I will admit with Windows Server 2012 R2 I usually installed the full gui version and then once I had the server the way I wanted it, I would uninstall the gui. With this no longer being possible with Windows Server 2016 I had to dust off my notes on how to leverage sconfig and powershell to configure new domain controllers running Windows Server 2016 Core. Here is my notes on what I did.
Setting up a DC to host a new domain.
Go through the installation and put in the new password.
In the core console run “powershell.exe”.
Hold off on rebooting until after you set the Static IP and DNS.
Update the DNS Server.
Restart the server.
Log back into the server, install and configure the first Domain Controller in a new forest/domain named “sixteen.contoso.ad”. (I have to many contoso labs built)
Provide the safemodeadministratorpassword
Then confirm you want the server to be configured and rebooted.
The usual warnings should prompt and eventually be prompted for sign out.
Log back in and do some initial validation.
Validate the new DC
Make sure AD/DNS services are running
Check for sysvol and netlogon shares
With this being the first DC shouldn’t be to much to check
Making a Windows 2016 Server a Domain Controller in an existing domain
Here we go, at the PowerShell prompt on the new server run the following.
At the Windows PowerShell credential prompt use credentials for the domain you plan on this Domain Controller hosting.
Set the SafeModeAdministratorPassword, then validate that the server is to be configured and restarted.
Once the new Domain Controller restarts and comes back up, leverage the Validation Section to make sure it looks good. Also leverage some of the replication cmdlets to validate replication is working.
That is all I’m going to cover in this blog I hope you find it useful.