Multiple AD servers in a Windows 2008 Server R2 environment
Posted on 2011-04-19
Here is the scenario:
I recently moved my company to a new Windows 2008 R2 network environment.
I have 3 IP DNS domains called: MYCOMPANY.LAN, SOUTHEAST.MYCOMPANY.LAN & CAPITAL.MYCOMPANY.LAN
I wanted to provide some measure of redundancy and DR for my network environment, so I have two Active Directory (AD) servers. The "Primary" AD server is MGMT04 and has the FSMO roles on it, as well as the global catalog and is he Primary DNS server for MYCOMPANY.LAN, SOUTHEAST.MYCOMPANY.LAN and CAPITAL.MYCOMPANY.LAN
When I installed the 2nd AD server called MGMT02, it installed DNS and it is the secondary DNS for all of those IP DNS domains.
Ok, this is all no big deal.
However, Win 2008 R2 did something a little different than what 2003 server did when installing a secondary AD controller, and I want to make sure I fully understand how this works.
When i installed the secondary AD server, the wizard prompted me to also install the Global Catalog on this guy because of the multiple DNS domains. I did so.
The question I have is this.
If the Primary AD server MGMT04 ever goes down, (hopefully NEVER), what is the procedure then for promoting the Secondary AD server of MGMT02 to be the primary AD server? Do the FSMO roles just automatically switch without any intervention on my part? I know I would have to manually change the DNS IP both Forward and Reverse domains to be the Primary, but what about the AD?
Thank you in advance for any direction on this,