Solved Installing Windows 2008 DC on 2003 Domain

Microsoft Windows server 2003 enterprise
June 23, 2010 at 13:41:53
Specs: Windows 2008

Our domain's functional level is Windows 2000 native. We are planning to replace the last DC running Windows 2000 with Windows 2008.

I read that we need to do adprep before promoting a W2K8 to a DC . I'm curious if anything did this procedure before and what steps did it take.


See More: Installing Windows 2008 DC on 2003 Domain

Report •

June 24, 2010 at 16:22:05
To Do this:
1. Verify the new server's TCP/IP configuration has been pointed to the current DNS server.

2. Join the new 2008 server to the current Windows Server 2000 domain.

3. Upgrade the Windows Server 2000 forest schema to Windows Server 2008 schema with the "adprep /forestprep" command on old server.

Run the "adprep.exe /forestprep" command from the Windows Server 2008 installation CD on the server that holds the schema master role.

Locate adprep.exe file on the 2008 install disc and run that file from run on start menu with with /forestprep
Ex: d:\w2k8\file\file\adprep.exe /forestprep

How to Determine the Schema FSMO Holder in a Forest
1. Click Start, click Run, type mmc, and then click OK.
2. On the Console menu, click Add/Remove Snap-in, click Add, double-click Active Directory Schema, click Close, and then click OK.
3. Right-click Active Directory Schema in the top left pane, and then click Operations Masters to view the server holding the schema master role.

4. Upgrade the Windows 2000 domain schema with the "adprep /domainprep" command on old server.

Same as above but use /domainprep

8. Run "dcpromo" on new server to promote it as an additional domain controller in existing Windows 2000 domain.

9. Enable Global Catalog on new server and manually Check Replication Topology and afterwards manually trigger replication (Replicate Now) to synchronize Active Directory database between 2 replicas.

It will some time to replicate GC between DC be patient

10. Remove Global catalog from the 2000 Domain controller
To remove the global catalog from the original domain controller:
1. On the domain controller from which you want to remove the 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.
2. In the console tree, double-click Sites, and then double-click sitename.
3. Double-click Servers, click your domain controller, right-click NTDS Settings, and then click Properties.
4. On the General tab, click to clear the Global catalog check box to remove the role of global catalog from this server.
5. Restart the domain controller.

11. Verify that the old DNS Server Zone type is Active Directory-Integrated. If not, please refer to:

How To: Convert DNS Primary Server to Active Directory Integrated

Active Directory Integrated-Zone is available only if DNS server is a domain controller.

12. Install DNS component on new server and configure it as a new DNS Server (Active Directory Integrated-Zone is preferred). All the DNS configuration should be replicated to the new DNS server with Active Directory Replication.

13. Change client TCP/IP configuration to point to new 2008 DNS server.

Mike Treloar
Sago Networks

Report •

June 24, 2010 at 19:14:18
✔ Best Answer
Suggested order:

dns server on 2008
global catalog
transfer fsmo roles to the 2008 server

Report •

Related Solutions

Ask Question