Dagent connectivity issue (Delays or failures in connecting to the DS/GSS console)

Products

• Deployment Solution
• Ghost Solution Suite

Issue/Introduction

When the Dagent is up and running on a client machine it does not connect to Deployment Server/Ghost Solution Suite console, it takes a while until the Dagent connects to the DS/GSS console (this time fluctuates, some times it takes 15 minutes and other times it takes up to 2 hours). 

In the Dagent logs you will find the following error message:

[08/02/2010 20:27:50.553 2144 1] WaitForSysPrep.cpp:44 - Image state is IMAGE_STATE_UNDEPLOYABLE

If the above error message does not appear in the Dagent logs and the Dagent still experiences delays to connect to the DS/GSS console, then check this registry key:

{HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\State}

and if the value is IMAGE_STATE_UNDEPLOYABLE then most likely that would be why the Dagent is experiencing delays to connect to the DS/GSS console.

Environment

DS 8.x

GSS 3.x

Cause

This issue is generally caused by deploying an image with a 0 or 1 rearm count.  Rearm counts are decremented each time sysprep runs.  To view the current rearm count please run the following command on the client machine:

slmgr /dlv

It will take a minute or two for the window to pop up and the rearm count will be displayed at the bottom of the pop-up window.

Resolution

Please follow the steps below to solve this issue:

1. Edit Windows registry (regedit.exe)
2. Browse to {HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\State}
3. Change the value IMAGE_STATE_UNDEPLOYABLE to IMAGE_STATE_COMPLETE After this change is done the client machine will connect to DS console within a couple of seconds.

Note: Changing this registry key will help the Dagent connect but won't resolve whatever issue caused this registry key not to be changed by Sysprep. Because of this, the machine may not be a viable machine for capturing an image from.