Server Manager: To install the Active Directory Domain Services role, select Add Roles and Features from Server Manager.
Select Destination Server: Select the server you want to install the AD DS binaries on and select Next. In this case, we're on the Windows Server 2012 R2 server's (WITP-MEMBER) console.
Select Features: Next, you have the option to install other features. Note that Group Policy Management is automatically selected.
Confirm Installation Selections: Your choices are displayed, and you also have the option to automatically restart the server if required. Click Install to install the binaries.
Note that in this newest type of wizard, you can easily skip back to a previous step by simply selecting it from the left-side menu.
Installation Progress: Once the AD DS binaries are installed, you need to promote this server to a domain controller. Note that DCPROMO is gone; to continue with the process, select Promote the server to a domain controller. This launches the Active Directory Domain Services Configuration Wizard.
Deployment Configuration: Chose the deployment operation that applies to your situation. In this case, we're adding a Windows Server 2012 R2 DC to the ntservices.net existing forest.
Domain Controller Options: By default, DNS Server and Global Catalog will be selected. I suggest you leave these checked, as these are best practices. This is where you can specify the new DC is to be a read only domain controller. You also have the option to deploy a DC directly in an AD site; in this example I'm adding the new DC to the BranchOffice2 site.
DNS Options: If you are installing a DC with DNS into an environment that doesn't have an existing DNS infrastructure (such as a test environment), expect to see this message.
Additional Options: If you are adding a DC to a very large Active Directory environment, Install From Media (IFM) allows you to install the Active Directory database from backups rather than importing all data from the network—a real time saver.
If you do choose to replicate over the network, you have the option to choose which DC you want to replicate from (presumably the network closest DC).
Paths: The location where the AD DS database, log files, and SYSVOL will be stored. For a production DC there are recommended best practices for putting these files on a partition other than the system partition.
Preparation Options: The Configuration Wizard will inform you if ADPREP /FORESTPREP and /DOMAINPREP will be run. In this case, since we're adding a Windows Server 2012 R2 DC to a domain with a Windows Server 2008 R2 DC running at Windows Server 2008 R2 forest and domain functional level, these options will be run automatically.
The Configuration Wizard runs an extensive set of prerequisite checks to ensure these steps aren't executed on a forest crippled with problems (such as failed replication in the schema partition).
If you want to run ADPREP manually, this TechNet article describes how to do it. The More about preparation options link provides you with general guidance on the DC installation process.
Review Options: The selections you chose are selected. You can also view the PowerShell script that this wizard generates by selecting View script.
Prerequisites Check: The results from the prerequisites check. In this example, the server being promoted to DC doesn't have a static IP address because it's running in Azure. Note that the server will automatically reboot—there's no choice here—once the promotion operation is complete.
Installation: The wizard running ADPREP /FORESTPREP. Not a whole lot to see.
Installation 3: The schema partition being replicated into the new DC, one of many operations that takes place during promotion.
Automatic Reboot: The promotion is complete, and the server is automatically rebooted.