Installing Windows 2012 R2 Domain Controller - Microsoft Consulting Services - CloudServus - United States

Well, I’ve been pretty lazy in my lab environment for the last couple of months.  I’ve finally decided it is time to migrate to a Windows 2012 R2 domain.  Currently, I am running a Windows 2008 R2 domain with Exchange 2010 and Lync 2010.  This article is the first in a couple of articles that are loosely related.  This article will focus on:

• Creating a new VM in Windows 2008 R2 Hyper-V (I know, I know, I need to update that too)
• Installing a new Windows 2012 R2 server
• Preparing the server to be a Domain Controller
• Installing the Active Directory Domain Services role
• Promoting the server to a Domain Controller.

Creating a new VM in Windows 2008 R2 Hyper-V

1. In Windows Server Manager Hyper-V console, select New – Virtual Machine.
2. Click Next.
3. Select a name for your virtual machine and a location to store the VHD.
4. Allocate some RAM.
5. Select your network
6. Select a location for your VHD and the size.
7. Install and Operating System from a boot CD/DVD-ROM
8. Review and click Finish.
9. The Virtual Machine will be created.

Installing Windows 2012 R2 Server

It is always a good idea to review the requirements for installing a new server operating system, especially if you are installing into a lab or production environment.  The following article outlines those requirements. The minimum basic requirements are below:

• Processor: 1.4 GHz 64-bit processor
• RAM: Minimum 512 MB (800MB to install in a VM)
• Disk Space: 32 GB

1. In Server Manager, select the new VM and connect.
2. In the VM Console, select to start the VM.  It should boot from your Windows 2012 R2 ISO.
3. Windows will begin to load.
4. Select your Language, Time format and Keyboard. Click Next.
5. Click Install Now.
6. Enter your Product Key and click Next.
7. Select Windows (Server with a GUI).
8. Check the box to accept the license terms and click Next.
9. Select Custom: Install Windows only (Advanced).
10. Select your hard drive and click Next.
11. Installing Windows.
12. Once complete it will ask to Restart.  Restart Now.
13. Windows will restart.
14. Once setup resumes, it will ask you for an Administrator password for the computer.  Click Finish.
15. Windows will then Finalize your Settings.

Windows is now installed.

Preparing the server to be promoted to a Domain Controller

There are a couple of things that need to be configured once the server is installed and before you can promote it to be a Domain Controller.

• Change name and add to the domain
• Setup network settings
• Enable Remote Desktop Connections
• Run Windows Update

Change Name and add to the domain:

1. Click the Ctrl+Alt+Del button
2. The server will recognize that it is connected to a network and ask to scan for other devices.  Click Yes.
3. Click Configure this local server.
4. Click the Computer Name.
5. The old, familiar System Properties window appears.  Click Change…
6. Change the Computer name and select Member of Domain and enter your domain name.
7. Enter the credentials for a Domain Admin
8. Welcome to the domain.
9. You must restart your computer to apply these changes.
10. Restart.

Configure Network Settings

1. On Server Manager summary click on IPv4 settings
2. The Network Settings window will appear.  Right-click on the network adapter and select Properties.
3. Select Properties of Internet Protocol Version 4 (TCP/IPv4).
4. Enter the IP, Subnet Mask, Default Gateway and DNS servers.
5. Complete

Enable Remote Desktop Connection

1. Click Disabled next to Remote Desktop
2. Click Allow remote connections to this computer.  A pop-up will appear. Click OK.
3. Click OK.

Check for Updates

33 Updates installed

The server will need to reboot once this is complete.

Install the Active Directory Domain Services

1. In Server Manager, click Add roles and features
2. On the Add Roles and Features Wizard, click Next.
3. Select Role-base
4. Select the server and click Next.
5. Check the box for Active Directory Domain Services.
6. Review the Features to be added and click Add Features
7. Click Next.
8. Click Next.
9. Click Next.
10. We’re now ready to install the features.  Click Install.
11. It will take a few minutes to install the features and then the server will need to be rebooted.

Promote the Server to a Domain Controller

Now you are ready to promote this Windows 2012 R2 server to a Domain Controller.  Kick off the Active Directory Domain Service Configuration Wizard.

1. When you open Server Manager after installing the Active Directory Domain Services role, there will be a warning message in the Notifications area at the top right.  Then click Promote this server to a domain controller.
2. The Active Directory Domain Services Configuration Wizard will appear.  Make the appropriate deployment operation selection, select the domain where you are installing the new Domain Controller and click Next.
3. Select the appropriate capabilities and site information, select the AD site, enter your Directory Services Restore Mode (DSRM) password and click Next.
4. On the DNS Options page, you might see a warning message “A delegation for this DNS server cannot be created because the authoritative parent zone cannot be found…”
5. This was a know issue with Windows 2008 R2 Domain Controllers and you can read about it here, but I haven’t found a similar article for Windows 2012 R2 yet.  In any case, I believe the advice from 2008 is still application and we can move forward.
6. On the Additional Options page, you’re given the option to Install from Media (IFM).  We don’t need this, since this Domain Controller is on the network and can talk to other DCs.  Select from Any Domain Controller and click Next.
7. Select the appropriate locations based on your companies design decisions and click Next.
8. Click Next.
9. On the Review Options page, verify that the settings are correct and click Next.
10. On the Prerequisite Checks page, verify that there are no errors and review the warnings, then click Install.
11. Once the DCpromo is complete, the server will reboot automatically.

You now have a Windows 2012 R2 server in your Windows 2008 R2 environment.