Deployment Solution

I created a dual boot system of WIN7 and RHEL 5

The win7 boot partition is 0,0 (partition 1)

The win 7 partition is is 0,1 (partition 2)

The RHEL partition is 0,2 (partition 3)

I am using grub as the main boot manager.  The original system works fine.  The RHEL5 side works fine after imaging.  The Win7 side fails to load after imaging.

We get this message:

Windows Boot Manager-

Windows failed to start.  A recent hardware change .....

I think this is probably a Windows BCD problem, where the sysprep during the imaging changed something in the BCD.  Anyone else experience this and know the BCDEdit commands to fix it?

Thanks.

I know that in DS7 we had some issues around dual or mixed partitioning, but I thought we were handling that fine in DS6.

We are using 6.9 sp4

Booting off the Win7 install dvd and running the repair worked to repair Windows Boot Manager (I assume by fixing the BCD store) without breaking Grub.  However it would be nice to find out why it broke it the first place, since I would like to use our Deployment server for dual boot images, without having to spend the extra time in fixing the computers when the image is done.

I ran into a similar problem deploying a boot partition alongside multiple Windows 7 os partitions. Ghost was incapable of maintaining the integrity of the BCD store. I solved the problem by capturing the boot partition as a .wim file and using Imagex to apply it to a newly created boot partition.

For those of us using multi-boot solutions, maybe Symantec could provide a free down grade to earlier (working) editions of Ghost Server.