Switch out hardware on a Windows Server 2003 Domain controller

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.  

Thanks fellas.
LVL 1
jeremycushingAsked:
Who is Participating?
 
jeremycushingConnect With a Mentor Author Commented:
Decided to go with Symantec System Restore 2010 to complete this.  The manual way had too many issues.

0
 
sumeshbnrCommented:
take an image of the OLD HDD and boot in safe mode with the new server .Then boot in safe mode with netwroking and give the IP address configuration intact .Then plug LAN canble .then reboot to normal mode .Dont install chipset driver first .try without chispset driver. Is ther any drive letter chnages in the new HDD booting? if s change it
0
 
jeremycushingAuthor Commented:
So I should boot into safe mode and do the network driver first? give it a static IP then reboot into normal mode for the chipset?

No change to the drive letters - i just imaged the 500 gig to another 500 gig for testing purposes.  C: drive & D: drive.

Has anyone tried using Backup Exec system recovery 9.0.1?  I was looking around and it seems this might be an alternative?

Sumeshhbnr i am waiting for your update.


0
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

 
sumeshbnrCommented:
after taking the fresh image of old hdd to the new one boot the new server with the cloned hdd in safe mode and unistall anoy drive if it installed.then install only nIC driver .Then boot to safe mode with NW and configure the excat IP details of the old one and reboot to normal mode
0
 
jeremycushingAuthor Commented:
ok I will try that first thing in the morning.

thank you sumeshbnr
0
 
JohnLoCommented:
A thought have you considered running VMware esxi 4 FREE on the new server and converting the old server to a virtual machine. During the conversion you can increase HD space and vmware tools will install all the drivers you need. the only thing you will have to do is boot the virtual machine and install vmware tools, then follow this kb article (http://support.microsoft.com/kb/315539) to remove the old NIC, set the ip info on the new NIc reboot and your up and runnig,
0
 
jeremycushingAuthor Commented:
What is the best way to covert to a VM? Can you point me to a good tutorial with step by step information?

Thanks
0
 
jeremycushingAuthor Commented:
OK I went ahead and tried to install the NIC in safe mode but it says restrictions wouldnt let me.

I went for it and installed after booting in regular mode.  I added the same IP info as on the original server.  Rebooted and it came up.  It has a rouge Parallel drive that i need to remove.

The issue now is that I get error 2511 in the Event Log.

The server service was unable to recreate the share Resources because the directory c:\exchsrvr\RES no longer exisits.
Please run "net share Resources /delete" to delete the share, or recreate the directory c:\exchsrvr\RES

-

2511

The server was unable to recreate the share VPALERT$ because the driectory c:\progra~1\nav\alert no longer exists.  
Please run "net share VPALERT$ /delete" to delete the share or recreate the directory c:\progra~1\nav alert

-

I have approximately 7 of those.

These folders are on the D Drive and have been on the D drive.   I checked the D drive and there is a folder d:\exchsrvr\res which is shared out.

-

What is my next step?  Again I am doing a dry run to test this process out before the real deal.

So far so good.

Thank you

0
 
jeremycushingAuthor Commented:
Figured this looked like the correct path to follow for the errors I was getting. Hopefully Exchange will work.  Trying to open Outlook on the server.

You can ignore this behavior. Or, if you prefer, you can work around the behavior. To do this, perform the following steps.

   1. Run Registry Editor (Regedt32.exe).
   2. From the View menu, click Tree and Data.
   3. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares.
   4. Click FaxStore.
   5. From the Edit menu, click Delete.
   6. Quit Registry Editor.
   7. Shutdown and restart the server.

Except I am just using this as a guide.  :)

We will see...
0
 
jeremycushingAuthor Commented:
Exchange server still unavailable.

Still getting a few of those errors for:

D:\exchsrvr\connect
                  \add-ins
                  \tracking.log

those folders do not exist anywhere on the server

when i open outlook it says exchange is unavailable but in ESM i do not see anything out of the ordinary.

help guys?

weird for all of this little issues since it is an image of the functioning server.

0
 
JohnLoCommented:
For vmware conversions as asked.... The gudes are for 3.0 but 4.0.1 is very similar. the other links get you to 4.0.1

Server Migrations with Vmware Converter -
http://www.vmware-tsx.com/download.php?asset_id=48

Converter tutorial  http://www.petri.co.il/virtual_convert_physical_machines_to_virtual_machines_with_vmware_converter.htm

Converter FAQ - http://www.vmware.com/products/converter/faqs.html

Converter Manual - http://www.vmware.com/pdf/VMware_Converter_manual.pdf

Converter download - http://www.vmware.com/download/converter/
0
 
jeremycushingAuthor Commented:
still working on this. i will update.
0
 
JohnLoCommented:
Should not be zero points because he did not like the answers
0
 
jeremycushingAuthor Commented:
I agree. Points should be rewarded.  How do I correct?

Also the project was completed without a hitch using SSR 2010.  From old to new within 4 hours.  

Thank you everyone.

0
All Courses

From novice to tech pro — start learning today.