I would like to upgrade my Exchange Computer running Server 2003 64bit to a new computer with more memory and CPU. At the same time I would like to upgrade it to 2008 Server. My plan was to disk image my current server then restore it to the new hardware so that I don't have to take the running system off line. The problem is when I restore the image to the new computer Windows fails to boot because it says the hard drive is faulty but it is not because a fresh install works. If I restore the image to like hardware it works fine. I have run into this in the past with workstations but I just did a new install to get around it. In this case I would really like to get the image to work on new hardware. Is there a way to force Windows to boot even though it is different hardware? I did not install Recovery Console on the server so it is not part of the image. I wish I did now because I have a felling that this is the solution. My next step is to use the Windows Builtin Backup and Recovery system on a fresh install if I can't get the image to work.

Do a repair install of server on the imaged box. This will update the hardware keys since you will need to provide that systems drivers when asked.

Since you've changed the hardware the o/s doesn't have drivers for the chipset, and that's why it fails. Making a repair install, like wanderer said, (after choosing to install windows, let the guide search for previous installations of windows then press R to repair) will remove the windows dir only and reinstall it with correct drivers. Most of your applications will also need to be reinstalled since the registry is one of the files being rewritten.

I would love to but the Windows Installation disk will Bluescreen at the part where it starts to load Windows and I never get the opportunity to run a repair install. Is there a way to bypass this like hold a set up keys down when running the install disk?

I could put the imaged drive into the like hardware and run a repair there but I think it will only see that systems hardware. My next try is to uninstall all drivers on the imaged system and then make a new image of that system and try to move it to the new computer.

You are just repeating things that have been tried and failed. You should be concerned that your methodology will lead to an unstable system. If the windows install is bluescreening out of the gate you have larger issues. Are you using a OEM version of server?

No I am using a VLK and there is where maybe the problem is. I have never seen this problem with OEM versions. "If the windows install is bluescreening out of the gate you have larger issues." True but it will not Bluescreen when I use the image on like hardware. In addition, the alternative is to install a Fresh 2008 Server then Exchange then configure it to match the other server then; prepare computer then; move the FSMO roles then; use one of the non MS approved scripts for moving AD from one DC to another and Finally cross my fingers and hope it comes up right. I guess I should do this to learn how to do it but I would rather do it when I am not busy. Not only that, I want to make sure I can restore the image on different hardware because if the server goes down, I might not have the ability to order the exact same hardware in the future.