Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently setting up a remote office that will be connected to our HQ via a P2P connection. We leverage a Windows AD Domain, and I wanted to know what would motivate someone to migrate from a single site multiple subnet topology to multiple sites/subnets. What factors should be considered?

share|improve this question
thank you for the suggestion... I'd left some things open as I thought more answers may have come in, but that wasn't fair to the current answers. – JPrescottSanders May 26 '11 at 3:14

If you have a DC at the branch site, you want to use Sites and Subnets to associate the branch DC with the site that contains the branch subnet(s) - so that all users at that site will preferentially authenticate the local DC, not your central DCs.

If you only have DCs at your central site, there's little or no gain to using sites and subnets.

share|improve this answer
I support this answer, and would also point out that you should probably make this new server a global catalog server! – SpacemanSpiff May 26 '11 at 4:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.