Dcpromo under Windows Server 2012
Today I want to promote an Windows 2012 Server to domain controller. I am building an new demo environment for a PowerShell 3.0 demonstration.
When I try to execute the well known command dcpromo I receive the following message:
But I still want to promote this server to the domain controller role. In this blog I will describe how you promote a server to DC Windows 2012 style. So I go to the the Server Manager console.
Click on ‘Add roles and features’.
Click Next
Click Next
Select the bullet ‘Select a server from the server pool’, make sure that if you have multiple Windows 2012 servers that the correct on is selected. Click Next.
Select the server roles you want to install on the selected server, in this case I selected ‘Active Directory Domain Services’ and ‘DNS Server’. Click Next.
Select the features you want to install on the selected server. ‘Group Policy Management’ is automatically selected because of the selected role in the previous step. Click Next and click Next in the next to two information screens.
Confirm the information on this screen and click Install.
After the installation is done return to this screen and click on the link “Promote this server to a domain controller”.
Since I am building a new domain I selected ‘Add a new forest’, and I entered the Root domain name. Click Next.
Because I am adding an Windows 2008 R2 domain controller later I selected ‘Windows Server 2008 R2’ for forest and domain functional level. I also entered the DSRM password.
In the next screen an warning appears about the delegation for the DNS server. If you click the warning a separate window appears, stating that if you are not integrating in an existing DNS domain no action i
s required. Click Next.
Check if automatically the correct NetBIOS name is entered and click Next
Check, and if needed alter, the NTDS and Sysvol folder location. Click Next.
Review the selected options. Click Next.
Click Install. After the installation is done you need to reboot the new domain controller.
After the reboot your new domain controller is done.
Was once an enthusiastic PepperByte employee but is now working at Ivanti. His blogs are still valuable to us and we hope to you too.