Promoting Windows 2000 domain to Windows 2003

How do you promote Windows 2000 domain to Windows 2003 domain on different machine
Who is Participating?
Lee W, MVPConnect With a Mentor Technology and Business Process AdvisorCommented:
Very dangerous to do it like cycle303 suggests.... to quote one of my links on the subject:  "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..."

Here are some links that should get you going for upgrading a 2000 domain to 2003:

Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain;en-us;555040

[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 | Windows | How To Upgrade Windows 2000 Domain to Windows 2003 Server
Quote from the top is from this article:

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
IF you are install another server with 2003 os, then you need to run adpred and domainprep from the 2003 disk on the 2000 server first.  Then install AD on the 2003 server and go.
Just to add to the above answer, here is a EE thread which i consider to be the most comprehensive upgrade guide

What are weekends for, eh?
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Before I defend why my answer is no more dangerous than yours, I would like to say that you answer is also correct.  If a windows domain is not taken care of properly, (IE upgrades, patched, hotfixes, the usual) most often they suffer the wrath when they try to upgrade.  Major issues will surface when running adprep and domainprep.  Little issues inside of active directory (unlinked containers and what not) will not be so apparant.  NTDSUtils and ADSIedit can be used to correct those issues.  I have also upgraded several hetrogenous domains with 10+ windows/unix servers in credit unions, law firms, banks, and local government agencies.  It is true that the environment needs to be pristine, however those are the steps required if a domain is maintained correctly.  
One line question with one answers leave alot of scope for interpretation - but don't make the answer any less right, just less comprehensive.

For example - I could also have been pedantic and said that cycle303's answer was not complete in that all you have managed is to introduce a 2003 server into a 2000 domain at 2000 DFL and FFL... whereas the poster asks "promote Windows 2000 domain to Windows 2003 domain " - again it depends on how you interpret this, but a literal interpretation could be decommisioning the orginal DC to then raise the FFL, or in place upgrade the OS of the old DC provided backups have been taken!

My link has pretty much all leew's concerns, but specified as an addition to the orginal answer rather than an alternative.

I'm sure if the poster has some concerns they can reply here...
Lee W, MVPTechnology and Business Process AdvisorCommented:
I didn't say he was wrong... just that it was very dangerous -- because so few people have a perfectly managed Windows Server infrastructure.
I would wholeheartedly agree that precautions are taken place with any major change in AD, and this is one of the biggest you can make.

Backup the whole lot up 3 times! :D
Everything posted looks right.  Great job to all?
LTGAuthor Commented:
Thanks for the info, it was very useful!!
All Courses

From novice to tech pro — start learning today.