Tuesday, April 17, 2012 11:07 PM
I would like to build a DC for a remote site and tie it with our main office.
The two site will be connected via a site-to-site VPN via cable modem
The idea for this DC to have AD DNS, DHCP. It will be a file, print, license server with several other minor roles.
Would I build this DC at the main office? join it to the domain, install all roles, configure, then bring down and power up at the other site?
Or do the above at the remote site?
Thursday, April 19, 2012 1:38 AMHi Altramarine,There are two methods to add domain controllers in remote sites, just as you mentioned. But each method has some associated issues need to pay attention to.As the first method you mentioned above, please notice that you cannot bring down the new DC for a long time which may exceed the tombstone lifetime.
As the second method, it's better to use IFM(install from Media) to reduce the replication time for the new DC.Please refer to this TechNet article: http://technet.microsoft.com/en-us/library/cc794962(WS.10).aspx for more details about Best Practises for Adding DCs in Remote Sites.And I'd like to share the other two articles with you as well, which may be useful to you:Known Issues for Adding Domain Controllers in Remote Sites
http://technet.microsoft.com/en-us/library/cc816685(v=ws.10).aspxInstalling AD DS from Media
- Marked As Answer by Arthur_LiMicrosoft Contingent Staff, Moderator Tuesday, April 24, 2012 7:08 AM
Thursday, April 19, 2012 3:27 AM
I've just covered the first article which helped me a lot already. Reading the other two now.
Also, regarding the first method:
The transition of the DC in question from main to remote site will be at most 5 hours. Providing the tombstone life is at default (60 days) on my 2003 server, I should be OK?
Also, I am a bit puzzled (lots of reading will aid that) about how to build this new DC at the main site, since at the remote site it needs to be on a separate subnet.
Should I initially join it, promote it using the main site subnet and then at the very end, change that? and add DNS role when the DC is already at the remote location?
My main site subnet (192.168.0.x)
Remote site I'd like to be (172.16.10.x)
Once again, really appreciate your time!
Thursday, April 19, 2012 7:55 AM
You're welcome Altra, it's my pleasure to help.
Since the disconnection time cannot exceed the tombstone lifetime, 5 hours would be no problem.
I think you can join the new DC to the main site and add DNS role for it, move it to the appropriate site, and then ship it to the physical site, thereby you can save some replication time.
Besides, make sure that the DNS configuration for this new DC is correct. If needed, please refer to this article for more information about how to configure DNS settings for Domain controllers: http://support.microsoft.com/kb/825036.
Feel free to let me know if there is any further questions.