|
Question : Replacing Win2k DC with Windows 2003 DC
|
|
Simple question 150 point for the best possible answer:
I have two Window 2000 Domain Controllers and they are replicating with one another. They each have their propose but what I am task to do is eliminate one Domain Controller and replace it with a Windows 2003 Domain Controller and replicate with the existing infrastructure. What I was thinking was creating a windows 2003 domain controller and attaching it to replicate with both Win2k DC. The moving all the files and services to the new DC, my question is: what is the best possible manner that I should approach this task and make it a successful one. Do I just install a win2003 DC and attached it to the existing environment or do I install a Win2k DC and upgrade to a Win2003 DC? What are your suggestions and Ideas?
Thank you sincerely
bebeslb
|
Answer : Replacing Win2k DC with Windows 2003 DC
|
|
Depends on many things, especially how old the DC is now.
The ideal way would be to introduce a new 2k3 Server onto the network, and then gracefully remove the old one. But there is alot to know and do during this process...
First, what mode are you in? Mixed or Native? Do you know where the FSMO roles are? Is the computer running any Sever System Software like Exchange?
Im not giving a checklist, but rather just a bunch of things to consider.
first thing you'll need to do is extend the active directory schema. This is done by using the adprep utility which comes with Windows 2003. You'll have to run the following: adprep /forestprep adprep /domainprep This is essential to a 2k3/2k network. Then after you install Windows 2003 and Active Directory, you should have 3 Domain Controllers. If the old one was running DNS or DHCP, you'll need to set that up on the new computer at this point. With just 2 DCs, I would make them both DNS servers. If you are using AD-Integrated DNS, you should just be able to turn it on, and it will replicate along with the other DC info.
You'll need to identify which of the two computers are Global Catalog servers, and which ones hold which FSMO roles. You will need to move all of them off of the server you are decommissioning. Also make sure that the other DCs are global catalog server.(I assume you don't have that many users/computer accounts, so this is recommended). Once you have a server that has no roles and isn't a GC, then you should be able to uninstall Active Directory by running DCPromo. This is assuming there is nothing else about this computer that needs to be transfered. Once you have uninstalled active directory, the server is now a member server and not a domain controller. You should then be able to remove it from the network.
You could also upgrade one of your existing servers to 2k3, but if you have the resources, and the computer is more than 3-4 years old, I would purchase a new one.
|
|
|
|