Hi everyone, I ran Sysprep on my Steadier State setup, with the intention to roll this out to a classroom of computers.
I then created a Ghost image of the reference PC and I am able to deploy the Ghost image to the other classroom computers. The rollback feature works like a champ.
When I make changes to the image, this is what I'm doing: 1. Load Ghost image 2. Boot into Windows (the VHD) 3. Make the necessary changes 4. Run Sysprep again and shut down 5. Boot into "rollback Windows" and run the merge command
If, at this point, I boot the system up, I have no problems. Sysprep has worked its magic and the changes made earlier have stuck.
However, if I create a Ghost image just after the merge command but before booting the reference PC, and then deploy that image to another machine, that other machine gives the error below and will only boot to the "roll back windows" partition.
This problem seems to be related to the merge command, but I'm not sure.
How can I fix this?
quote: Error: The Windows Boot Configuration Data (BCD) store file contains some invalid information. Object GUID: {e0314960-a43d-11e1-a217-b84580a896a3} Description: Windows 7 Status: 0xc0000017 Info: The configuration for an element within the object is invalid in the boot configuration data store. The associated Windows Boot Loader entry may not be available for selection until the problem is rectified by an administrator.
No idea, I haven't added Ghost to the mix. Ghosting without Sysprepping (which you're doing) can cause problems, as you know. Also, the GUIDs will of course be diffent for every system... that's probably the basis of the problem.