Ghost Solution Suite

Tested this on multiple PC's such as Lenovo, Dell and HP. I have not changed any console options. GSS 3.0 build 1333 installed on Windows Server 2012 R2.

The issue is that when I boot from either PXE or USB everything works fine. PC connects to the console just fine.

However, if I reboot the PC for any reason and try to connect again, it boots into PE and the DAgent starts, the status says "Connection closed, Session terminated". then the PC reboots. (Please see attached)

If I delete the PC from the Ghost Console I can then connect to the console again.

I think that what is happening is that the client is checking in with the console, seeing it has no job and then booting back to production. If you have a job assigned does it do the same?

Hi Cobra7 -this is the correct behavior.

To explain, consider the scenario where you get lots of new PCs and need to set them up in a lab. As you rush around to each PC, booting them into automation for the first time, they will each wait in a "connected to server" state. This is called Initial Deployment and it allows you get each PC booted into automation so you can then go back to the console and drop the imaging jobs on them.

Once the computers have imaged and they reboot, they should return to the production environment by default. If however they are pushed into automation without a job scheduled for execution there, you don't actually want them to wait indefinitely once they are connected. You want them to boot into the production environment so that they are ready for use right?

In short, only new computer objects can be configured by default to wait in automation for their initial deployment. If you want to force a wait state on existing computer objects, then you'll need to create a job in GSS3 with a wait task. If you deploy that then to the machine it will boot again into automation and wait.