Discussion Locked

Sites or Domains

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a client with one location but may open up a branch office. If we put a Domain Controller in the Branch Office should we create a Site for the office or create an OU there?

5 replies

by cportman

BOTH!

It would be good to have all resources (computers, users, printers) in a separate OU.

You would also want to set up an additional site in AD Sites and Services so that you can regulate the replication of AD over your WAN.

good luck
cp

by joseph moore

Remote offices are just what Sites were made for. They are not physically close to your headquarters, and the connections to them are slow and tenuous at best. So, make all of your branch offices in their own Sites. This makes for a good logical grouping first off. Plus, you can apply Group Policy Objects to the remote users easier this way, no custom tweaking neeed. Just apply them to the Site and that is it.
Now, as for Organizational Units, you can have the same ones at all Sites for more logical groupings. If you have a Sales OU at your headquarters, set another Sales OU at the remote office Site for the remote Sales guys. You could put all sales people in the same OU, but that makes no sense. Users in different Sites should be in their own OUs. That is just the way they work. Less bandwidth required to get info on them if everyone is grouped together.
Also, you can set up a GP for the Sales OU at headquarters, and apply it to the remote office OU also, then all sales people arebeing effected by it.

So, set up the DC in the remote office, keep it as a part of your same domain (same namespace), set up a Site there, make its own OUs (but the OU name scheme can copy your headquarters naming to make organization easier), add the users who will be stationed there in those Sites and OUs, and away you go!

This discussion is closed to new replies.