Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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 have 2012 domain and about 50 of workstation and servers together in it at branch (A) and now I get another branch (B) with about another 75 workstations and servers (domain 2012). I need to consolidate them in one bigger network. I am willing to implement sites and services. But thing is that right now both branches has networks

I have never done this before on my own and I did read the instructions but it got me confused what be the right way to get things done.

I am thinking to switch one of branches adresses to network. I am not quite sure what to do the best about all it. How is the best practice designs would work on that kind of cases?

share|improve this question
Setting AD Sites and Services aside you'll need to renumber one of the networks if you intend to have arbitrary IP communication between hosts in both locations. I'd also do yourself a favor, from a VPN perspective, and not use in either location. That network is used by a lot of home NAT routers. I'd pick something else entirely. – Evan Anderson Jan 27 '14 at 20:55
up vote 1 down vote accepted

If you have the same subnet stretching both sites, you can't effectively use AD Sites & Services. It requires different subnets per site. As you've said - switching one site to (or any other unsused subnet for that matter) and defining both subnets and assigning one to each site is the basics of what you need to do.

If you ever grow to more than two sites, you'll need to consider site links, but that doesn't matter in a 2 site topology.

share|improve this answer

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.