Windows Server 2012 -- domain controller FAILOVER ?

My two 50-user locations are connected via
20MB fiber and each has ONE domain controller.

How can I setup so if an ON-SITE domain controller
is down it uses the REMOTE domain controller instead
or do I need two domain controllers at each location ?
finance_teacherAsked:
Who is Participating?
 
Walter PadrónCommented:
In Active Directory Sites and Services create two Sites and put one DC in each, create two Subnets one for each site and assign them to the proper Sites created before. After that authentication must succeed no matter the site where you logon.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
Are you experiencing issues now?  It should just work.  Sites allow for "favored" authentication to a server but do not preclude authentication from other sites.
0
 
Cliff GaliherCommented:
As long as you've defined your sites in sites and services and clients have DNS settings pointing to DNS servers that are up, this will happen automatically. You don't need to make special changes.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
finance_teacherAuthor Commented:
Currently each domain controller (one at each site)
also does DNS for the 50 users at each site.

Site #1 Example, 192.168.1.1
    ** Primary DNS Server = Site #1, 192.168.1.1
    ** Secondary DNS Server = Site #2, 192.168.2.1
----------------------------------------------------------------------------------------------------------------
What do you recommend since it seems like the below happens ?

  ** login to a computer @ site #1 using a NEW, non-cached account
  ** see that above Primary DNS Server & Secondary DNS Server are correct
  ** turn off Primary DNS Server
  ** login to a NEW computer @ site #1 using a NEW, non-cached account
  ** login as the CACHED user instead
  ** do PING
            ** 192.168.1.1 is down
            ** 192.168.2.1 is up

I was assuming login to a NEW computer @ site #1 using a NEW,
non-cached account would work since the backup, 192.168.2.1, is up
0
 
Walter PadrónCommented:
You must setup DNS properly.

In Site_A the primary DNS must be server DC_A and secondary DNS must be server DC_B
In Site_B the primary DNS must be server DC_B and secondary DNS must be server DC_A

DC = Domain Controller and i suppose DNS is installed there
0
 
Cliff GaliherCommented:
Logging I with both cached and new non-cached would work. The primary DNS server would be down either way so the secondary would be used to find DCs, and DCs would be contacted using site metrics until one responds. Cached credentials would only be used if all DCs or DNS servers failed to respond. As said previously, when set up properly, this "just works."
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.