The question to be asked is, Why do we need to add additional Domain Controller?
This answer is very simple: “for services redundancy” or “for domain authentication improvement in remote Site”.
In case of single Domain Controller failure, we still have another one which can provide authentication services in our network, which avoids business discontinuity.
So we assume that you already have an existing Windows 2008/ R2 or Earlier domain controller in place and also you have a Fresh New Windows 2012 R2 Box ready to get promoted as a ADC. As its going to be a DC, its fairly important that it should have a static IP address of same subnet or a routable subnet to an existing DC. Also don’t forget to point this new W2k12 server to existing domain controller (in our case 2k8 server) IP address.
In this Example the Domain Controller is using 192.168.0.253 IP.
And On the system we are promoting Additional Domain Controller the IP is- 192.168.0.252, so we are going to point this new server to existing domain controller for DNS, as in screenshot below.
Since DCPROMO is no more there.. I mean… the option is replaced in Windows Server 2012 R2
So the way to promote a server to a domain controller has been changed. Refer below
As the first step lets pull up the Server Manager.
Microsoft has designed Windows Server 2012 keeping in mind Cloud Computing… And this is one fine example after Storage Pool is this page…
So let`s assume that you have to deploy a domain controller on another location. What all options do you have?
- To go on to that site and install active directory.
- To get that server here and then install active directory
In the world of Cloud Computing, We are moving towards Server Virtualization. So what if I make a Virtual Machine here on my own machine, Install Active Directory on it and then send that Virtual Machine to the Remote Location
Select the Active Directory Domain Services Role
As we can see, it adds all the required features by itself automatically.
Another good point to note here… If I would have been installing AD DS Role on a Remote Computer, then I don’t have to be there to reboot the server, this screen gave me an option to reboot the server automatically after the role has been installed
On the same page, you also have an option to select an “Alternative Path” for the source files
And Just one more click, and here we go for the Installation Progress-
Once the Installation is done, and you close the wizard, don’t expect anything to happen automatically… Neither try to search for dcpromo again….
On the Server Manager Page, notice the Yellow Exclamation Mark up top right corner
Click the Notification Icon with the Exclamation Mark
you should see an option- “Promote the Server to a Domain Controller“. Found it???
First, click on the Task Details
So there is an option as “Post Deployment Configuration”
And the Action required is “Promote the Server as a Domain Controller”
Select the Link either from here “Task Details” or directly from the Notification” Window which we clicked earlier
Now click on the link- “promote this server to a domain controller”
And here comes the Configuration Window
- Add a domain controller to an existing domain
-Add a new domain to an existing Forest
- Add a new Forest.
Here we will choose, Add a domain controller to an existing domain.
Then specify the domain information for this step:
We will add the name of our Domain, in this case Domain name is “arsh.com”
Next Step looks something like the Screenshot below- Here you can choose if you would like to make your domain controller a GC and DNS Server, by default the options are checked and that’s recommended, Unless, You have a specific reason to uncheck them. Also notice that here you can also specify your DSRM password
Also notice the RODC (read only DC) option, if your domain supports the same you can choose to promote this DC as RODC by selecting this option.
After specifying the DSRM password and selecting relevant option, click next.
During the installation of DNS in Server W2k8 during DCPROMO process, a pop-up was seen regarding Failed to get DNS delegation. The reason was that by default when we install AD and DNS, the server tries to create a delegation for the zone above your domain name.
The same thing happens here as well but is displayed in a slightly different way. Now, Instead of the pop-up, you have this line and a small link “show more”
See the option “Create DNS Delegation” cannot be ticked.
Next is Path for NTDS and SYSVOL, change them if you want to . Like some people like to move them to a separate directory, here is your chance
So next we are in for a pleasant surprise, No more manual forest prep and Domain prep. By default the wizard has the built in option to prepare your domain for the new Windows 2012 R2 Schema, refer the screenshot below
Another very cool feature… “Prerequisite Check”
Prerequisite Checker is there in Exchange 2007 and now has been incorporated in Windows Server 2012. This small but very efficient tool helps us to determine if there is feature/component which is missing before it actually starts installing Active Directory.
All Systems are go-
Final Configuration Page….
And now time to Reboot System-
The New Login Screen
The Server Manager showing the Domain Information
And the New Start Page…..check out the new AD snap ins here 🙂
So your 2k12R2 DC is all up and running, check out the new features and Enjoy Using it.
Latest posts by Arshdeep Singh (see all)
- Asus Zenfone 2 Laser- NTFS issue - December 7, 2016
- Change Password for Soonr account in just 3 steps - November 3, 2015
- Windows Update error Codes, Description & Solutions - August 20, 2015