Pointing the DAgent to Another Deployment Server
Updated: 06 Aug 2008 | 1 comment
If you have created a Vista image using a Scripted OS Install task, then you most likely left the command line to install the DAgent: C:\DAgent\DAgent.msi /quiet server_tcp_addr=%DSSERVER% server_tcp_port=402 scripted_install=1 LAUNCHUI=FALSE
However, you have now created an image that will connect the DAgent to whatever Deployment Server the image was created on. If you are using multiple Deployment Servers and are trying to use the same image, obviously this will be an issue. To work around this, I created a task to run immediately after a Distribute Image Task in WinPE pre-boot automation, which switches the DAgent to the correct Deployment Server, by modifying the registry:
REM Point DAgent to correct DS reg load HKLM\TEMP c:\windows\system32\config\software reg add "HKLM\TEMP\Altiris\Client Service" /v DSIp /t REG_SZ /d "%DSSERVER%" /f reg add "HKLM\TEMP\Altiris\Client Service" /v TcpAddr /t REG_SZ /d "%DSSERVER%" /f reg unload HKLM\TEMP
blog entry Filed Under:

The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments
Will this work on windows xp as well?
Will this work on windows xp as well?
Would you like to reply?
Login or Register to post your comment.