| 3TGKB-0065 | |
|
Last Edited : |
17-10-06 |
|
Revision : |
1.0 |
Boot Manager error when using Symantec Ghost to Deploy Windows Vista images!
I have been playing with the new Microsoft OS Vista.
During my play time I discovered that Ghost 8 would throw Boot Manager errors when deploying images which had Vista as the Operating System.
Solution One:
This one works for me...
Using the following switch during a Ghost Image Restore. -FPSP
I use the following command line to start a Multcast session called "auto3" to restore a ghost image using the switch.
GHOST.EXE -clone,mode=restore,src=@mcauto3,dst=1 -sure -rb -fdsp
Find below a Symantec Reference Document abd the switch description....
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1998082612540625?OpenDocument
| -FDSP | Clone | Force Disk Signature Preserve. Use to resolve bootup failures after cloning a disk on a Windows 2000/XP computer, especially when the disk and controller are the same in the source and destination computers, but the partition sizes or layout are different. This switch preserves the signature bytes on the destination disk when performing a disk-to-disk or image-to-disk cloning operation. This switch prevents Ghost from automatically forcing a disk initialization, which Ghost does by default when imaging a Windows 2000/XP disk. |
Solution Two:
This one works for me...
Upon starting the imaged Vista PC you will receive the Boot Manager error. Simply start the PC up using the Windows Vista CD and choose "Repair Machine"
Solution Three:
I haven't tried this one...
Found this on the following forum http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=181082&SiteID=1
Before Cloning Windows Vista run these three commands on the source PC before creating the Ghost image.
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
Please see below for an extended explanation of these commands
I hope one of these help you.
Regards
Matt Rowston
KB Keywords: Windows Vista, Ghost 8, Boot Manager, Error
Solution Three Forum Quote :
| An update on where things currently stand. Indeed this appears to be a condition specific to the new BCD-based boot manager. i.e. It's the boot manager failing to find and execute the Windows boot files under circumstances where Windows itself can otherwise successfully boot, and not a change to the boot configuration/dependencies of Windows itself. (Windows of course also keeps partition and disk information of its own, even prior to Vista. But in my experience this never resulted in a boot issue for the situation described, and Windows automatically updated and corrected if a different partition / disk signature was used.) The cause of the Vista load failure previously described, to the degree I understand it, is that by default all of the BCD entries use "PARTITION"-type device references where applicable. In the BCD data stored for these "PARTITION"-type device references (visible in the BCD section of the registry, and in a BCDEDIT /EXPORT), both the drive signature and the partition number appear to be part of the information stored. And based on the results, both must match the current environment else the boot manager will declare the OS loading application cannot be found. (Even if I force the drive signature to be the correct signature, if I'm restoring to a different partition than the image was previously using, the restored partition will still fail to boot because the partition number stored in the BCD still doesn't match the current environment.) The solution that appears to be most suitable (at least for the situation I previously described and was intending to solve) is to change the BCD entries to use "BOOT" device references rather than explicit "PARTITION"-based references. Presumably thereby implying "whatever device/partition I booted from, that is the device/partition I want to use". Preparing a Vista installation prior to creating the Ghost image then becomes a task of setting the DEVICE and OSDEVICE entries of the BCD entries you intend to use: Logon as Administrator and from a command prompt invoke the following changes: BCDEDIT /set {bootmgr} device boot BCDEDIT /set {default} device boot BCDEDIT /set {default} osdevice boot Note you can "fix" a previously restored (and currently failing to boot) installation using a PE boot disc and executing these same actions against the restored partition's BCD entries. There may be more entires that you need to fix if you intend to use them ({memtest}, {legacy}, etc.). The above is just the minimum for my own scenario where there is just a clean Vista-only OS installation on the partition. Once the BCD entries are no longer referring to specific disk signatures and partition numbers, there is no need to use -FDSP with Ghost anymore, either. The disk signature can be reset as it is by default with a Ghost disk restore, and "nothing special" is required during image creation or restore (from a Ghost perspective). Presumably this could have also been corrected by resetting/updating the "PARTITION"-type device entries with current information (current partition number and disk signature) post-Ghost restore, if for any reason the use of "PARTITION"-type references is needed. For the purposes of making an image that can be restored via Ghost to any partition on my test box, the "BOOT" device reference appears most desirable by not being fixed to any one partition or disk signature. Happy booting. |