You have created a Ghost Solution Suite preboot environment, such as PXE, and you are attempting to get a computer to boot to Automation. The automation environment starts, but once the agent comes it, it reboots right away. If your target machine never tries to go into automation that is addressed in other articles.
Connection Closed. Session Terminated
Known PC's do not stay in Automation unless they have a job in the console that compels them to do so.
You have already installed the agent on the target machine, or you have already booted this computer to automation at least once.
When the Agent starts on the target machine it looks to the Ghost Solution Suite server for a job or task to be assigned to it. If it does not find a job or task to do, it will reboot the client trying to get it back into production. This is working as designed. To get a machine to stay in automation it needs to have a job, or it needs to be "new" to the console.
Note that Ghost identifies a PC by the "MAC address", a value which is attached to the Network Adapter. Unless you change the options in Ghost, the identity of a particular computer follows a network adapter, not the name of the PC or its hard drive.
To get a particular machine to boot to automation to do a job the easiest thing to do is just assign a job to the target PC. It will reboot to Automation, perform the job, then reboot back to Production. Any imaging job that specifies an automation environment will also cause the computer to reboot to automation and stay there long enough for it to do the job.
If you want a machine to boot to automation and wait there you have 2 options.
Option 1) Delete the PC from the Ghost Solution Suite console. Note: This will cause the loss of job history associated with this PC.
Option 2) Assign a "Wait" job to the target PC.
A small yellow triangle icon in the Ghost Console indicates the machine is "waiting" in automation for the next command. You can send an imaging job to the machine that is waiting in Automation. If you are running a non-sysprep create disk image task be sure to check "Do not boot to Production if client is already in Automation pre-boot". If you do not check that box the client will boot the PC to Production Windows, then back into Automation. It does this to ensure that it is booted to the automation environment specified in the job. Check that box to allow it to accept whatever automation environment it is currently using no matter what is set in the job. If your Create Disk Image task is selected to use Sysprep the "Do not boot to Production.." checkbox will be unavailable. For Sysprep jobs it must boot to Production first, because Sysprep runs in Production Windows, not in Automation. After Sysprep is executed it will reboot back to Automation and begin creating the image.