In the Windows Server 2019 Essentials edition, the Administrative Dashboard is no longer available. You have to perform all configuration manually—or via PowerShell.
Latest posts by Leos Marek (see all)

Windows Server 2019 Essentials, formerly known as Small Business Server, is a reasonable choice for very small companies. As Microsoft is pushing everything into cloud computing, version 2019 is probably the last version that will have the Essentials edition available.

Benefits and limitations

Clearly the main benefit of Essentials is its price, which is roughly half that of the Standard edition. Also, you do not need to purchase any client access licenses (CALs). This makes the overall price even cheaper.

Windows Server 2019 Essentials comes with following limitations:

  • 16 CPU cores; 64 GB RAM
  • Maximum of 25 users/50 devices
  • No virtualization rights; one physical or virtual installation

Over the past few years, as even small companies have used more and more applications, the computing demands have increased. You can have only a single installation of Essentials. Assuming it will be the only server in the environment, I would not recommend Essentials to a customer with more than 10 users or computers.

Administrative Dashboard removed

Administrative Dashboard formerly served to complete the server setup and simplify other management tasks. It was part of the Windows Server Essentials Experience role, which Microsoft removed from Windows Server 2019 along with the dashboard.

Administrative Dashboard

Administrative Dashboard

Instead of the Administrative Dashboard, only the Server Manager is now available. The configuration is very similar to any other Windows Server edition.

Configuring the server

Typically, Windows Server 2019 Essentials will be the first (and most likely the only) server in your environment. This means you will need to deploy and configure at least these roles and features:

  • Active Directory Domain Services (AD DS)
  • DNS Server
  • DHCP Server
  • Print and Document services (optional)

First, you should rename the server from the generated WIN-XXXX name to something more suitable. You can do this with the following command:

Rename-Computer -NewName "DC" -Force -Restart:$true

Before you can start with the Active Directory deployment, you need to configure a static IP address. First, use Get-NetAdapter command to find out the InterfaceIndex number of the network interface controller (NIC) you want to assign the IP to.

Use Get NetAdapter to get the InterfaceIndex value

Use Get NetAdapter to get the InterfaceIndex value

In my case, I am configuring the server with IP, mask, and gateway

New-NetIPAddress -InterfaceIndex 5 -IPAddress "" -AddressFamily IPv4 ‑PrefixLength 24 -DefaultGateway ""

Note that at this point, we did not configure a DNS server. The setup will add this later automatically. Now you can install all needed roles using a single command. You can omit the ‑Verbose parameter; I just use it for presentation.

Add-WindowsFeature ‑Name AD-Domain-Services,DHCP,DNS,Print-Services ‑IncludeManagementTools ‑Verbose
Install the needed roles and features

Install the needed roles and features

Now it's time to promote the server to a domain controller using the following command:

Install-ADDSForest -CreateDnsDelegation:$false -DatabasePath "C:\Windows\NTDS"  DomainMode "Default" -DomainName "LAB.local" -DomainNetbiosName "LAB" -ForestMode "Default" -InstallDns:$true -LogPath "C:\Windows\NTDS" -NoRebootOnCompletion:$false  SysvolPath "C:\Windows\SYSVOL" -Force:$true

Make sure to change the ‑DomainName and ‑DomainNetbiosName parameters to fit your naming convention. Also, note the ‑DomainMode and ‑ForestMode parameters. These serve to set the forest and domain functional levels. However, for some strange reason, the setup does not offer the Win2016 value. Use the Default value to set the Windows Server 2016 forest and domain levels.

Windows Sever 2016 value missing in Install ADDSForest cmdlet

Windows Sever 2016 value missing in Install ADDSForest cmdlet

After you execute the command, the setup will prompt you to enter the Directory Services Restore Mode password. Next, it will show several warnings (the same ones as in the graphical interface) and will promote the server to a domain controller.

Promote the server to a domain controller

Promote the server to a domain controller

It will reboot the server automatically to complete the promotion. The functional level is indeed set to Windows Server 2016. Also, it set our network adapter DNS server IP address to

Domain functional level

Domain functional level

At this point, we have a working Active Directory domain and DNS system, leaving us with DHCP and Print and Document services. As the Print and Document services role does not require any special configuration, the only configuration left for us to do is for the DHCP server.

For the initial DHCP configuration, you need to perform several steps. First, you need to create the DHCP management security groups DHCP Administrators and DHCP Users. You can do this using the old netsh command:

netsh dhcp add securitygroups

You need to restart the DHCP server service after this:

Restart-Service DHCPServer

Next, you have to authorize the DHCP server against Active Directory using the following command:

Add-DhcpServerInDC -DnsName "DC.LAB.local" -IPAddress ""

As the last step for DHCP initial configuration, you need to notify Server Manager you've done the configuration; otherwise, you will still see the notification.

Set-ItemProperty ‑Path registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ServerManager\Roles\12 ‑Name ConfigurationState ‑Value 2

At this point, you can finally create and activate the DHCP scope for client computers. In my case, I am creating the DHCP scope named LAB with the IP address range from to, the default gateway, and the DNS server Excluded IPs are in the range from to

#Create scope named LAB with range to
Add-DhcpServerv4Scope -name "LAB" -StartRange "" -EndRange "" -SubnetMask "" -State Active
#Exclude IPs from range to
Add-DhcpServerv4ExclusionRange -ScopeID "" -StartRange ""  EndRange ""
#Configure default gateway (router option) to
Set-DhcpServerv4OptionValue -OptionID 3 -Value "" -ScopeID ""  ComputerName "DC.LAB.local"
#Configure DNS server option to
Set-DhcpServerv4OptionValue -DnsDomain "LAB.local" -DnsServer ""
DHCP scope created and activated

DHCP scope created and activated

That's it for the initial configuration of Windows Server 2019 Essentials.

Subscribe to 4sysops newsletter!


With the removal of the Administrative Dashboard and the initial configuration wizard from Windows Server 2019 Essentials, the configuration is not as easy as it was in previous versions. After reading this post, you should be able to speed up the configuration using several PowerShell commands.


Leave a reply

Please enclose code in pre tags

Your email address will not be published.


© 4sysops 2006 - 2023


Please ask IT administration questions in the forums. Any other messages are welcome.


Log in with your credentials


Forgot your details?

Create Account