I have a job setup that looks like this:
Reboot to Automation
Remote All Partitions and Data
Deploy Image to Computer
Reboot to Production
The computer successfully reboots into WinPE, loads drivers and network correctly, successfully registers with the NS, starts and completes the removal of the partitions and data, then starts ghost 11.5.1 without any command line options so it just opens up and sits there waiting.
Go into the ClientImageDeploy.log and eventually find that there is an Error getting=@CommandLine which I assume is the problem.
I can then, from the log, get the path to execute ghost.exe, enter the command line options by hand in the command prompt and get an execution of ghost running that does the imaging correctly. That execution finishes as it should after completing the deployment of the image.
The command used (for x86 WinPE environment) is like:
X:\> "\\<server>\Deployment\task handler\ghost\ghost32.exe" -sure -clone,MODE=restore,DST=1,SRC="\\<path to image>\<image name>.gho"
Then, to "trick" the job into thinking it completed without any failures, I go back into the ghost execution that's waiting and do a normal quit which sends back a finished without error to the NS. It will then continue to reboot to production correctly and mark the job as completed successfully.
Not sure if this is a bug or a problem with my setup, rdeploy seems to run with the command line options, but I'm having problems getting rdeploy to set the boot device correctly...