We have an existing Win2K3 domain with a primary DC in our main office and a secondary DC in a co-location facility 700 miles away. We have a secondary (local) office connected to our main via WAN link. There is a member server which we would like to convert to a DC using dcpromo (for a variety of reasons...). What specific "gotcha's" should we prepare for? I have reviewed the dcpromo procedure from several sources (including TechNet) and really don't see much to worry about here, as this is an existing functioning AD structure.
Because of the latency between the satellite office (where the new DC is to be located) and the main office, and because the main office is subject to power issues, our thoughts are to also add a DNS replica to the new DC.
Any specific tips, comments or warnings are appreciated.
Software/Hardware used:
ASKED:
August 26, 2008 2:08 PM
UPDATED:
September 3, 2008 11:54 AM
You should not have any problems. The performance of AD replication depends on DNS, also the connectivity between physical locations. To reduce the amount of time for initial AD replication to occur, you may consider using the dcpromo /adv option to perform an offline installation of AD. This will prevent the initial replication from occuring over the WAN. For more information on this option review the following article How to use the Install from Media feature to promote Windows Server 2003-based domain controllers.
Prior to your installation do the following things:
Point your new server’s DNS settings at the root DNS servers
Create DNS delegation.
Open the DNS Management console
Right click: The Root zone, click New Delegation Next
Enter: The domain name for the child domain Next
Add: The child DNS server to host the new zone Next Finish
Now the DCpromo should run fine