How to prevent DC at remote site from being used in rotation company wide.

We have two 2008 domain controllers at our main data center. We have a 2003 domain controller at one of our branch locations. The DHCP server at the branch location is set up to assign their local DC as the primary domain controller. However, we are noticing that this domain controller is being referenced by Outlook throughout the company. When users open Outlook they are forced to wait as the branch office DC is contacted.

I believe this may be due to the controller being in rotation for AD lookups. However, we can not have this take place as it is very inefficient to do AD lookups to remote locations. So my questions is, how do I set the DC's so that they are only utilized at their proper locations. i.e. the branch DC is only used at the branch location.
EuclidInsuranceAsked:
Who is Participating?
 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:

Hey,

That's exactly what AD Sites and Services is there for.

In order, you would:

1. Configure Site Names for each of your sites
2. Configure Subnets for each of your sites (it's a folder in AD Sites and Services) and bind those to sites
3. Move Domain Controllers into the sites as applicable

Clients will preferentially log onto a DC within their site.

You should also ensure that each site has a Global Catalog (I recommend making all DCs into Global Catalogs) or you will find logons still end up on remote domain controllers.

HTH

Chris
0
 
robrandonConnect With a Mentor Commented:
You should create a new Site and Subnet in the Sites and Services snap-in.  Make sure your remote DC is in the remote site and subnet.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.