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.
August 26, 2008 2:08 PM
September 3, 2008 11:54 AM