Ghost Solution Suite

During the days of the aclient, we could schedule migration jobs, to a new DS server, using an internal file copy function (destination = aclient.inp). Is this possible with the Altiris Deployment Agent?

I know you can right click on the computer to set a new destination IP or manually change the reg key TCPADDR, but having the resiliency and scheduling features of a job would be better.

I'm pretty sure you still can. The aclient.inp file has to contain all settings though I believe, the changed ones alone isn't enough. I used to use a "Destination path" of setting:aclient.inp

But rather than try and keep an aclient.inp file up to date I prefer to have a DS job with the reg key change and run that.

set NewDS=172.27.24.104

reg add "HKLM\SOFTWARE\Altiris\Client Service" /v DSIp /t REG_SZ /d %NewDS% /f
reg add "HKLM\SOFTWARE\Altiris\Client Service" /v TcpAddr /t REG_SZ /d %NewDS% /f

Using settings or self in a copy task to reconfigure or update the DAgent is pretty much a no go. I have been playing with it for a bit.

We use an asynchronous batch file to migrate DAgents. Just not as elegant as in the old Aclient days.

Andy - why do you set DSIp?

I set DSIp because I saw that the IP address of the DS Server was set there too.