A client has a single Windows 2003 standard server (DC) on some old crusty hardware. In fact their RAID died and now it was reloaded on a single drive until their new gear could be ordered and build.
The new hardware has come in. It is a dual core Tyan mobo, RAID 5, etc. It is time to get their OS on this new hardware.
The usual way to go would be to shut them down on a friday afternoon, ghost the drive onto another 500 gig drive. Plug the 500 gig into the new mobo and configure the drivers (including NIC), and get it to play nicely with the RAID controller. After it gets up and going I would then ghost onto the RAID. The old mobo is a TYAN also if it matters.
Now as an initial test I have an image of their current 500 gig drive that they are running on. It boots up and of course needs the updated drivers. However I wasnt really paying attention and I may have done something wrong? but after I loaded all the drivers and reboot it gets stuck on applying computer settings - i let it sit for 40 minutes. I then killed it.
So my question to all of you pros is why do you think the DC got stuck on applying computer settings? My thought is that it has something to do with the NIC card. Is there something I need to do instead? Maybe before the restart?
I know this method is so brute force. The bigger question is shouldn't there be an easy way to do this? Isn't there some software I can use to make an image and then load on this new hardware? Price isn't a issue w/ the software.
I have access to both the old (current) server (tyan, 1 500 gig drive, single server in their domain, has their exchange, etc.) and to the new hardware. I can have access to both machines all weekend long.
What would be the best route and please provide as many steps / details as possible. I would really appreciate any direction.
I have ghosted server OS onto new hardware w/o too many problems and it never got stuck on the applying computer settings. Strange.