Upgrade hardware on Domain Controller 1

[jfc1003]

We have a rather old machine running as the W2K Domain controller on a small network. The machine itself is at the end of it's life cycle. The motherboard desperately needs replacing as do the hard drives. Unfortunately, there is a third party software running on the machine that would require a technical visit for a reinstall at the cost of $3000. My boss's challenge...find a way to elminate that additional cost.

If this was a workstation, I would just image the old drive to the new workstation, reinstall Windows over itself to reestablish the HAL and be done. But I have never done that with a domain controller. Any suggestions on what effects it would have on a Domain Controller if it were shut down, imaged to a new server, and woke up finding all new hardware? Can you reinstall Windows over itself on a Domain controller?

 

[helliphikneau]

imagin doing what you suggest and then doing a boot to oem cd and an in place repair as it will retest for hardware.

hope this helps

 

[Hondy]

If you only have one DC on a w2k domain you are asking for trouble, if you lose this machine or break it trying to move it you will screw all your permissions on all your files and mail through out your domain.

You should consider cloning your server using Ghost or something, you should add another machine into the forest to hold all of the permissions while you tinker with the other one. This way if if blows up you will still have your crucial domain info intact. Transfer the roles to your new DC (global catalog, infrastructure etc).

Then I would look at cloning the image from your current domain controller onto your new server, being windows 2000 it should find all the new hardware, you may need some drivers but the AD should stay intact.

People will still be able to log on assuming the services like dns and dhcp are running on your new DC or elswhere.

I hope this helps

 

[jfc1003]

That is what back ups are for. Few small companies, including mine, have the luxury of multiple servers, but thank you for the lecture. You missed the point altogether.

I am simply wondering if reinstalling windows over itself to redetect hardware on a domain controller will have any negative effects. Or if anyone has tried it. There are many circumstances and issues that I am not detailing.

 

[Hondy]

That's not what backups are for, backups are for recovering from an UNAVOIDABLE problem. I was only trying to help, re-install windows over your domain controller and see where it gets you, you are telling me you don't have 1 spare pc in your business... good luck. It will detect all your hardware, like I said, but if active directory still works I'd be surprised. If thats your reaction to someone offering advice then you obviously don't want to listen.

 

[ricpinto]

I have cut and paste this from tek-tips before, now I don't know the thread number, here it goes:
-----------------------------------------------------------


Please let me know what you think?

Procedures for moving Win2000
Installation to new hardware!

I was recently faced with the problem of moving any existing Win2000 domain controller to a new hardware platform. The only reason for the move was that the current hardware was failing. After a search Microsoft’s Knowledge base and posting on the chat boards it did not appear that anyone had a straight forward process for making such a move.

The following is a step by step explanation on how I accomplished the move, with little or no down time for the users. Total time needed to complete the process was about 4 hours.

Hardware;

• Dell PowerEdge 2300 (Old system)
• Dell PowerEdge 2600 (New System)

Software;

• Win2000
• Active Directory installed
• System running as Primary Domain Controller
• Veritas BackupEx

Requirements;

• Both servers must have the same type of tape drives used for backups
• New and Old server must have the same name
• New server should not be connect to the network until process in completed

Steps;

1. Configure your hard drives, Example: my old server contained six 9gig HD’s split into two volumes. The first being the (C:\drive) and labeled system disk made up of three 9gig drives configured raid 5. The second being (D:\drive) and labeled Benson made of three 9gig drives also raid 5.

The new servers drives consisted of six 36gig HD’s split into two volumes. The first being the (C:\drive) and labeled system disk made up of three 36gig drives configured raid 5. The second being (D:\drive) and labeled Benson made of three 36gig drives also raid 5.

2. Prep your two volumes then install Win2000 server, make sure that you name the server the same as the old one. Do not install active directory just a basic install of windows 2000 will do.

3. Next install your backup software in my case I use Veritas,

4. On the old server run a backup make sure you backup the whole server including system state.

5. Re-boot the new server when Win2000 starts to load press F8, from the menu choose Director restore mode and the server with start up in safe mode.

6. Using the backup tape that you just make in step 4, inventory and catalog the tape on the new server. Once the catalog process in completed you can begin the restore process.

7. In Varitas choose restore, you should then choose to restore all drives including the system state. I also selected the following options listed below to take place during the installation. Then start the restore process.

• Restore over existing Files
• Merge the existing hardware configuration and registry services with the data to be restored
• Restore junction points, files and directories from backup Media

8. The restore process could take several hours depending on the amount of data being restored. During this time you should make sure you have the device drivers for the new server handy either on CD or Floppy as you might need then during the reboot.

9. When the restore is complete you should be asked to reboot if not shut down the server and restart it, letting it boot up normally. As the new server boots up windows should start to find new hardware and begin to install drivers for that hardware. You might be asked for the drivers CD or floppy during this process. This process may be slow in my case it took about ten minutes to complete the boot process.

10. When windows is done booting from step 9 shutdown and restart again this time during the boot process you may see error messages that one or more services did not start. In my case it was the Veritas services, during the restore process the registry changes prevent Veritas from starting you can ignore this for the time being.

11. Also during the boot process you will notice that Win2000 seems to get stuck at Preparing Network Connections. This is normal as the servers active director is attempting to connect to the other servers but can’t. You should not be plugged into the network yet. After what seems to be forever but is more like 15 minutes Windows with boot to the login screen.

12. Login as administrator and verify the following;

• Any programs that were installed on the old server are working on the new one. In my case two of my programs stopped working both were dependent on services that start during the boot process. I un-installed both programs via add and remove programs then re-installed them both then worked fine.
• Verify that the syvol information on the new server matches the syvol from the old if not make the needed corrections.
• Next verify that your NIC card is configured properly
• When configuring the new NIC card after you may receive the following error: “The IP Address you have entered for this network adapter is already assigned to another adapter. Adapter is hidden from the network and Dial-up connections folder because it is not physically in the computer.” To resolve this issue use article Q269155 from Microsoft Knowledge Base.

13. Shut down the new server completely and power it off.
14. Run one final backup on the old server, I recommend a Friday night to ensure all work for the week is backed up.

15. After the backup is completed on the old server disconnect the server from the network by removing the network cable. DO NOT shutdown the old server you might need to go back if the process fails or you may want to confirm configurations once the new server is running.

16. Connect the new server to the network and then power on the server. It should boot faster this time and logon as the administrator. Clear the admin logs and permit the server to run for some time checking the logs from time to time for errors. In my case I was dealing with a domain controller I also had a secondary controller on the network. So during this time I checked to see that both were processing logon request and the replication was taking place.

17. After an hour and in my case I had received no errors both servers had replicated and were processing logon request. It should be noted that I performed this process while two users were login to the network neither user reported any problems nor did they even realize that a change had taken place.

18. Clear any messages from the admin logs and reboot the new server one more time and you should be in business.


NOTE: I used Thursdays tape to build the server and restore active directory, as in my case I had to restore some data files from work that was done on Friday prior to changing the servers. You may need to restore some data files from the last backup on the old server; however you should not restore any operating systems or active director from this point on.


WARNING: ALTHOUGH THIS PROCESS WORKED FOR ME I CAN NOT PROMISS THAT IT WILL WORK FOR YOU OR ON ALL HARDWARE PLATFORMS. I BELIEVE THE THEORY BEHIND THE PROCESS IS SOUND HOWERVER FURTHER TESTING NEEDS TO BE DONE TO CONFIRM AND REFINE THE PROCESS