Dagent shows connection closed, session terminated

[Migration User]

I am trying to image a thinkpad R61 laptop with windows 7 enterprise os. I have set the bios for the nic to boot first and the job in the DS console using sysprep. When the laptop first boots up it loads the dagent and the agent shows the record updated, it only shows connection closed session terminated when the job is dragged to it. The DS version we have is 6.0 build (430) SP3. Thanks

[Migration User]

Are you sure it's DS 6.0 build (430) ?  That's pretty old...
The latest version that was compliant with Windows 7 is DS 6.9 SP3.  I can confirm that it works with our test windows 7 machines. 

[Migration User]

Sorry I meant 6.9

[Migration User]

Has any one got a solution for the above problem?

[Migration User]

I too have a similar problem on a Windows 7 Enterprise machine running Dagent version 6.9.453 and a server running Deployment Solution Version 6.9 (build 453) Service Pack 4.

First off dagent's connection to the server is spotty at best, and takes about 16 minutes to even show up or connect to the deployment server as in this unresolved issue. But it does eventually hit the server. However like the original poster, any time I issue a job to the client computer from the server, it fails to execute and then the client disconnects from the server and lists the status as "Connection closed; session terminated." At this point, no further communication between client and server takes place until the client is restarted (and then it takes 16 minutes to connect.)

This is after I tried to create an image from this computer using sysprep. Despite the fact that it didn't successfully run, I now find this message repeated in the Dagent logfile. Which to me implies that Dagent is still waiting for the sysprep from a job that was long ago cancelled and deleted to run.

[08/02/2010 20:27:50.553 2144 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_UNDEPLOYABLE
[08/02/2010 20:27:50.553 2144 2] DsAgent.cpp:625 CDSAgent::AgentCommand - QueryShutdownState
[08/02/2010 20:28:20.616 2144 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_UNDEPLOYABLE
[08/02/2010 20:28:20.616 2144 2] DsAgent.cpp:625 CDSAgent::AgentCommand - QueryShutdownState
[08/02/2010 20:28:50.671 2144 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_UNDEPLOYABLE
[08/02/2010 20:28:50.671 2144 2] DsAgent.cpp:625 CDSAgent::AgentCommand - QueryShutdownState
[08/02/2010 20:29:20.740 2144 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_UNDEPLOYABLE
[08/02/2010 20:29:20.740 2144 2] DsAgent.cpp:625 CDSAgent::AgentCommand - QueryShutdownState
[08/02/2010 20:29:50.808 2144 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_UNDEPLOYABLE
[08/02/2010 20:29:50.808 2144 2] DsAgent.cpp:625 CDSAgent::AgentCommand - QueryShutdownState
[08/02/2010 20:30:20.876 2144 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_UNDEPLOYABLE
[08/02/2010 20:30:20.876 2144 2] DsAgent.cpp:625 CDSAgent::AgentCommand - QueryShutdownState
[08/02/2010 20:30:50.945 2144 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_UNDEPLOYABLE
[08/02/2010 20:30:50.945 2144 2] DsAgent.cpp:625 CDSAgent::AgentCommand - QueryShutdownState

Again, any help would be appreciated. It's a pity there are so many issues on here that just get left to die without resolution, and it'd be nice if this didn't have to be one of them.

[Migration User]

Your log file indicates image_state_undeployable.
As long as the computer is in this state Dagent will not communicate or show in task bar.
It must say image_state_complete

From my experience what could cause this is
1. A previous attempt to create a image failed on the reference computer causing the image state to be bad therefore image created is bad.
 Also I've been told when you set up the job to create a image in the DS console and you choose Rdeploy (which I was told is inconsistant) then try useing ghost instead.

2. Also during distributing a image if something happens during sysprep you will  get a computer that seems ok afterward but its state is image_state_undeployable and Dagent will not function right.

In the registry check HKLM-software-microsoft-windows-current version-setup-state There is also a file in windows directory but I don't remember its location that indicates the image state.

To fix the problem you will have to remake the image if that was bad or if imaging a computer, find out what went wrong. It could be something in the answer file. 

When you set up a job to Create an Image in Deployment solution it runs Sysprep on the reference, if something goes wrong it is left in a image_undeployable state even if the computer boots into the desktop and functions ok. Same thing when distributing a image.

[Migration User]

I actually just hosed another system of ours, and can confirm if you change the registry key to IMAGE_STATE_COMPLETE, dagent will start working normally again**, almost instantly.

Just for closure.

**edit: almost normally. It connects as if it's normal, but It's still kind of wonky when accepting jobs. It's still better to avoid this if you can.