For several years I have successfully used Ghost 2003 to run pcdos boot disketts and create ghost images of our computers. I have successfully used these Ghost images to uprgade hardware (eg. larger hard drives) and recover from various disasters. Ghost has never let me down yet. We have successfully resored images of Small Business Server 2000, Windows Professional 2000, Windows XP, and others.
I recently upgraded to Windows SBS 2003, with Terminal Server running on a separate Windows Server 2003 server. For the SBs machine, I used some old 9gb scsi drives in a RAID 5 configuration for setup and configuration, and had planned to install larger drives and use Ghost to migrate to the larger drives and increase the partition sizes, as I have previously done successfully with a RAID5 configuration in SBS 2000.
Ghost created the image successfully and resored the image successfully (according to its own messages), but the server only boots to the Windows Server 2003 screen with the progress bar, and then reboots itself.
I have made several attempts, including re-initializing the RAID configuration, but the results are identical every time.
Can this have something to do with the SID? (I really don't know what that is, i've just seen it referred to in several other places!) ;-) Does it have something to do with Microsoft's anti-piracy measures I've heard about that prevents an image from being resored to a different machine? (in this case, do you think the different hard drive array is causing the anti-piracy protection to kick in?) I'm just shooting in the dark here.
Am I likely to have the same problem resoring the Ghost image I made of our Windows Server 2003 - particulrly if I am NOT trying to increase the drive capacity on it?
Any help/suggestions/solutions would be greatly appeciated!
I really like Ghost for the purpose for which we use it, but right now I'm scared to death because I don't have a restorable version of our OS!
Thanks in advance!
- Paul Johnson
Good Times PowerSports