Upgrading w2k Domain controller hardware

[Guest]

Hello All-

I am sure that there are some KB or white paper resources that deal with this issue, but I have not been able to find them. I want to upgrade my File & Print server hardware to a brand new server. This server is currently one of my Domain Controllers and I want to make sure that all the computers that point to it will continue to function properly within the W2K network after the upgrade. I also plan to upgrade the Hardware on our Exchange 2000 server which is also a Domain Controller. Any info or links you can provide would be very helpful. Thanks in advance for your help. Let me know if you need any additional info from me.

-Nathan

 

[Gerry Voras]

The best way to go about doing this would be to (1) build a new DC and add
it to your domain, (2) migrate software and services, and (3) shut down the
old DC pending rebuild. While it can be done, just moving the hard drives
from one computer to another is just asking for trouble.

BTW, I would not have the Exchange server also be a DC. Exchange will keep
the hardware busy enough as it is.

Hello All-

I am sure that there are some KB or white paper resources that deal with

this issue, but I have not been able to find them. I want to upgrade my
File & Print server hardware to a brand new server. This server is
currently one of my Domain Controllers and I want to make sure that all the
computers that point to it will continue to function properly within the W2K
network after the upgrade. I also plan to upgrade the Hardware on our
Exchange 2000 server which is also a Domain Controller. Any info or links
you can provide would be very helpful. Thanks in advance for your help.
Let me know if you need any additional info from me.

 

[Guest]

THx for the info, in what I have found so far this does seem to be the preferred method to bring in new hardware. Here are some links to related information that I found.

http://www.tek-tips.com/gfaqs.cfm/lev2/3/lev3/19/pid/96/fid/3016

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q255690

Cheers, nathan