When a client system boots into Windows PE 2.1, to Install the Automation Partition the DAgent starts and connects to the Deployment Server, but then appears to hang at "Client Record Updated".

Article:TECH40785  |  Created: 2008-10-30  |  Updated: 2012-07-21  |  Article URL http://www.symantec.com/docs/TECH40785
Article Type
Technical Solution


Issue



When a client system boots into Windows PE 2.1, to install the Automation Partition, the DAgent starts and connects to the Deployment Server, but then appears to hang at "Client Record Updated".  To reproduce:

1) Install Deployment Server 6.9 SP1 build 355
2) Install WinPE 2.1 automation files to the Boot Disk Creator
3) Create a WinPE 2.1 automation boot disk (with all basic default settings)
4) Create a job in the Deployment Server console that has two tasks
    A) File copy task that copies the partition installer to the client machine
    B) Run script task that simply runs the partition installer
5) Run the job created in step 4 on a client machine

The job will successfully copy the file, and start the installation process without errors. It will then boot the computer into WinPE automation (which it should be design), then when DAgent checks into the Deployment Server it will show "Client Record Updated", and then hang at this point indefinately.

If the client machine is rebooted manually (physically from the client machine) the computer will check back into the Deployment Server and then the job will show that it ran successfully (and the partition at that point is installed properly). The problem is that the process requires a manually physical reboot to the client computer, and during that time the client is unmanageble from the Deployment Server.

This issue did not occur with Deployment Server 6.8 SP2, but appears to have been introduced with DS 6.9 and 6.9 SP1. The customer reporting this is using scripts to install automation partitions because they are copying the files using NS package servers, and they have scripts that find the closest package server.

Environment



Server Upgraded to DS 6.9 Sp1


Cause



In this particular case, the agents need to be updated as well.  Since the existing agents were still the 6.8 Sp2 agents, they were not using the correct security.   As well, in the script, instead of just running the installer, use the "start" command to run and detach the installer.  The script will then complete immediately, telling the engine that it has finished so that the engine can continue to the next task when the agent connects again.


Solution



 Upgraded the agents.   An alternate idea is, in the script, instead of just running the installer, use the "start" command to run and detach the installer.  The script will then complete immediately, telling the engine that it has finished so that the engine can continue to the next task when the agent connects again.

Legacy ID



44213


Article URL http://www.symantec.com/docs/TECH40785


Terms of use for this information are found in Legal Notices