Installing the DHCP Role on Windows 2012 R2 Server

Unable to install DHCP server role on Windows 2012 Server Essential.

When you try to install the DHCP Role on a windows 2012 R2 server, then the role installation might just stop with the error "0x800f0922".

Searching for this error message shows a astonishing amount of questions about this, so you are in good company.

Some solutions tell you to disable automatic web proxy detection, or disconnect the network cable from the server during the installation of the DHCP role.

When you wish to know what happens, then look in the %SYSTEMROOT%\System32\DHCP for some logfiles.

In our case the newly installing dhcp server detects a already running dhcp server in the network and so refuses to install a local DHCP server.

So it's clear why disconnecting the network cable solves the installation problem, the other dhcp server is then no longer visible.

But why, why is preventing the installation of the dhcp server role?
And why, why is there such a cryptic nonsense error message instead of a real error message?

Adding a Windows 2012 R2 Essential Server to a existing domain

Adding a new Windows 2012 R2 Essentials server to a existing domain is a supported scenario by microsoft.

The new server will then be the primary server for all the ADS roles.

Unfortunally this does not mean it will just work out of the box.

The basic steps for this are:

- Make the basic installtion of the windows server

- Don't follow the wizard after installation, just cancel it
- Important: Set the server name you wish to use now, you won't be able to change it later on
- Install the Active Directory Services on the new server
- Add the new server as a additional ADS server in the existing domain
- Let the wizard finish the essentials configuration

The details can be found on the microsoft product site.

Unfortunally the wizard won't finish, but rather say: Error occured and nothing is logged.

The post-config wizard won't let you configure the Essentials Experience role because it's unable to start the 'Windows Server Essentials Management Service' system service. This service is configured to run under the <domain>\ServerAdmin$ account. This account must have 'Log on as a service' rights.

• Go to Group Policy Management
• Edit your policy, such as the 'Default Domain Controllers Policy'
• Go to Computer Configuration \ Windows Settings \ Security Settings \ Local Policies \ User Rights Assignment
• Edit 'Log on as a service' and add 2 accounts: <domain>\ServerAdmin$ and <domain>\MediaAdmin$

The ServerAdmin$ is enough to let the wizard finish the configuration. The MediaAdmin$ is needed for the 'Windows Server Essentials Media Streaming Service'.