Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

PXE Redirect in DS 6.9 SP3

Updated: 02 Jun 2010 | 4 comments
jimc84's picture
0 0 Votes
Login to vote

Hi all,

Has anyone had any success using the 'Redirect' option in the PXE Configuration Utility in DS6.9 SP3?  

We need to be able to allow our remote client machines to PXE Boot by selecting the default WinPE Mnanaged environment, which should redirect the PXE Boot to use the local configured PXE Boot, as our Image Jobs only run using the default WinPE Managed environment.  However, the problem we have is that instead of mapping the drives configured in the local PXE Boot configuration, it keeps pxe booting using the global WinPE Managed environment!  This looks to me like it may be a bug in the 'redirect' function in the PXE Configuration Utility but perhaps someone out there has had success with this??

Thanks,
Jim 

Comments

JSHawks's picture
24
Nov
2009
0 Votes 0
Login to vote

Hi Jim, We had the same

Hi Jim,

We had the same issue.   PXE Redirect in 6.9 SP2 did the same thing.  Altiris Support gave us a work around that work flawlessly and even reduces work.  I'm not at the office right now, but i'll post the notes i have tomorrow when i get back in. 

Scott

jimc84's picture
25
Nov
2009
0 Votes 0
Login to vote

Thanks Scott, that would be

Thanks Scott, that would be great!

jimc84's picture
01
Dec
2009
0 Votes 0
Login to vote

Hey Scott, have you any

Hey Scott, have you any update on this for me?  

Thanks,
Jim

JSHawks's picture
01
Dec
2009
3 Votes +3
Login to vote

Hi Jim, Sorry for the delay

Hi Jim,

Sorry for the delay in getting this to you.  OK Here is the setup an Altiris Engeineer on the DS team told me to use.

A quick note about our environment before we start.  we use our PXE servers in our location as a file server for that location as well.

setup your main PXE options on the master PXE server like you want under the shared profile.

In the remote locations, simply setup the PXE servers with no local boot options,and therefore, no redirect.  Have the remote locations IP Helper point to the local PXE as you normally would.  This will be pulling the winPE over the wire.  If you have a descent connection to the remote location, it's not really a big deal.

on the PE builds on the master and create a mapdrvs.bat under the startup folder.  below are the contents of that file.

if /i %ALTIRIS_PXE_SERVER%==%ALTIRIS_DS_SERVER% (goto one) else (goto two)

:one
net use L: \\EDMSITEMAIN\Library password /user:domain\user
net use O: \\EDMSITEMAIN\Images password /user:domain\user
goto end

:two
net use L: \\%ALTIRIS_PXE_SERVER%\Library password /user:domain\user
net use O: \\%ALTIRIS_PXE_SERVER%\Images password /user:domain\user
goto end

:end

Basically, what this does is use some env. variables from winpe and sets up our mapped drivers for us to pull our images, install packages, etc from a local share.  you may not need this.

We have all of our remote locations setup this way and i haven't had any issues.  We do have one location that has a very small pipe back to us, and we simply create ISO's and send to them.  That is a small office as well, so it's no big deal.

I may not have explained this well, so if you want more detail or clarification, fell free to email me and we can talk offline more about this.