We help IT Professionals succeed at work.

Adding a DC 2003 Enterprise Server to 2000 network

Have a 2000 DC presently and would like to add a 2nd DC (a 2003 Enterprise Server).  Also added to the mix is the remnants of a long since gone 2000 DC.  My understanding is the 2nd DC failed long ago but still in AD. Obviously I need to have a 2nd DC asap.  Would like to eventually demote the 2000 DC and be strictly 2003 and add a 2nd 2003 DC. I also have concerns that the running 2000 DC is quite old.

What would be the best scenario to address all?  Add the 2003 DC then remove the lost 2000 DC then demote the present 2000 DC. Or do I have to address the failed 2000DC before attempting to add the 2003 DC? Also I believe there are patches for AD when having a 'mix' solution.

More detail the better.  Thanks for the help.
Watch Question

Toni UranjekConsultant/Trainer


First you should remove all traces of failed domain controller. The process is called metadata clean up.

"How to remove data in Active Directory after an unsuccessful domain controller demotion"

Then you should prepare your existing environment for W2K3 DC.

"How to upgrade Windows 2000 domain controllers to Windows Server 2003"


Lee W, MVPTechnology and Business Process Advisor
Most Valuable Expert 2013

I think toniur may have given you incorrect information.  Correct me if I'm wrong, but you are NOT upgrading an existing 2000 DC to 2003... you ARE wanting to ADD a new 2003 DC to an existing 2000 domain, correct?

If that's the case, then the second link toniur posted isn't the most appropriate.  Rather, I would suggest you read over the following series of links.  There are considerations here because while you are not upgrading a 2000 DC, you ARE upgrading the DOMAIN to 2003.  Exchange can have issues with this and you may have a need/desire to move other services as well.

I do completely agree, your first step will be to clean up the metadata... while toniur's link I'm sure covers it, I tend to like Daniel Petri's documentation better than microsoft.  Reference:

Now the links for upgrading the DOMAIN to 2003.

Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain

[If using R2 release of Windows 2003] Extending Your Active Directory Schema for New Features in Windows Server 2003 R2

Hotfixes to install before you run adprep /Forestprep on a Windows 2000 domain controller to prepare the Forest and domains for the addition of Windows Server 2003-based domain controllers

Commodore.ca | Windows | How To Upgrade Windows 2000 Domain to Windows 2003 Server
Quote from the top of this article: "Several glossy Microsoft presenters have stated that all you need to do to complete a Windows 2003 Domain upgrade is run ADPREP and then upgrade away.  This may work for very small / simple environments but it is definitely not good advice for most companies.  After upgrading five servers in two unrelated domains and installing many fresh copies of 2003 I can say that I personally would not skip a single step in the process I have developed below."

Windows Server 2003 Upgrade Assistance Center

Here are some links that should help you in replacing existing domain controllers and/or transferring services and Active Directory functions to another/new system:

How can I transfer some or all of the FSMO Roles from one DC to another?

How To Create or Move a Global Catalog in Windows 2000

How to move a DHCP database from a computer that is running Windows NT Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is running Windows Server 2003

How can I move a DHCP database from one server to another?

How can I move DNS from one Windows 2000 Server to another Windows 2000 Server?
(Two Related if going 2000 to 2003 - read both before moving)

Exchange Considerations:
[If you run Exchange 2000] Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers

leew is right, you will be adding second DC not upgrading so please disregard second KB article from my post.


Thanks for the quick responses.  And I appreciate all the detail. We do have Exchange 2000 in place as well which adds to the mix.  Would it make better sense to upgrade Exchange 1st?  The Exchange is presently on a box that would need to be replaced entirely as well if going to 2003 and I understand Ex 2007 requires a 64bit server.

Thanks again


Thanks again for such a quick detailed response.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.