Windows Boot Manager error on Syspreped client after booting a Ghost Client to automation.
Last Updated April 20, 2018
Using Ghost Solution Suite(GSS) 3.x to boot a Syspreped client to automation results in the client machine receiving a windows boot manager error when the client is booted back to production.
Ghost Solution Suite 3.x
Windows Client OS
Windows PE automation
Steps to reproduce:
Running Syspreped manually on a windows client.
Boot to GSS automation (Pxe or automation folders) no ghost job has to be ran.
Boot the client back to it's production OS.
Observe that the client does not boot fully to the production OS but to the error noted above.
Windows Boot Manager
Info: Windows failed to load because the system registry file is missing, or corrupt.
The automation agent was hard set to log to the c:\windows\temp folder. In automation some times windows PE will assign drive letters differently than in production. If the OS drive was assigned a letter other than C the automation agent would create a windows folder on a non OS drive. Upon trying to boot to production the incorrect windows folder might then be used and the error would be triggered.
This issue has been resolved and the fix is included in GSS RU6. For more information on obtaining RU6 see the Symantec Ghost Solution Suite 3.2 RU6 Release Notes at the following link: http://www.symantec.com/docs/DOC1095
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe