Good morning. I wanted to document an issue I have seen several times. The fix for this problem is pretty easy in PowerShell, but would take quite a bit of time using Server Manager. The reason for the wizard is failing at 16% is due to the inability to connect to a domain controller in the domain. This failure to connect is due to none of the roles being installed and therefore the server not being promoted to a domain controller. This can all be discovered from the Essentials deployment logs in the C:\ProgramData\Microsoft\WindowsServer\Logs folder.
As I stated above the fix is pretty easy. Run the three PowerShell commands below, changing domainname to the name you want for your domain and the P@ssW0rD! to a password of your choosing. Keep in mind this password must meet complexity requirements with a length of at least 8 characters and 3 of 4 character types; capital letter, lowercase letter, number, special character.
NOTE: If you do not want the default computer name of WIN-<random string>, then you should change the computer name via the sysdm.cpl application or use netdom.
Also, change domainname.local to a domain name of your choice that ends in .local. For instance tailspintoys.local or contoso.local. You will not be able to change the computer or domain name after completing the wizard.
$Password = ConvertTo-SecureString “P@ssW0rD!” -AsPlainText -Force
Install-ADDSForest -DomainName “domainname.local” -SafeModeAdministratorPassword $Password -Force
After the above commands complete the server will automatically restart and the deployment wizard should complete without further errors. If it is failed, then click Retry. I have seen a few instances where a retry is necessary.
I hope you found this post helpful. If you have anything to add, please do so in the comment section below.