I’ve recently needed to move a Windows 2003 domain controller to a Windows 2003 R2 server. I’d been putting it off for a while because I knew it would be complex. These are the steps I followed. (For clarity Ive called the original Server A and the destination Server B.
Firstly upgrade the schema to conform to Windows 2003 R2. On the R2 second install CD is a directory called F:\CMPNENTS\R2\ADPREP . Copy this to the existing DC and run ADPREP /forestprep. You may also need to run ADPREP /domainprep and ADPREP /domainprep /gpprep. (More details here).
Now run DCPromo on ServerB and add it to an existing forest/domain. When it completes reboot the server.
Global Catalog promotion
Add ServerB to be a Global catalog and remove ServerA from being a GC. Allow time for ServerB to replicate all the changes required before removing the GC from ServerA. (Details here)
To create a new global catalog:
1. On the domain controller where you want the new global catalog, start the Active Directory Sites and Services snap-in. To start the snap-in, click Start, point to Programs, point to Administrative Tools, and then click Active Directory Sites and Services. double-click Sites, and then double-click sitename.
2.Double-click Servers, click your domain controller, right-click NTDS Settings, and then click Properties. On the General tab, click to select the Global catalog check box to assign the role of global catalog to this server. Restart the domain controller
Transferring operations master roles
Whilst AD supports multimaster replication there are some functions which are not supported in this way in the domain. Details of these can be found here
For procedures describing the transfer of operations master roles, see:
• Transfer the schema master role
• Transfer the domain naming master role
• Transfer the RID master role
• Transfer the PDC emulator role
• Transfer the infrastructure master role