How to Set Up Windows Server 2016 Server Manager

Server Manager is the central management console in Windows Server 2016 that consolidates the most common server administration tasks into a single dashboard. It provides a unified view of server status, role and feature management, event logs, performance data, and service health across both local and remote servers. For administrators managing small to medium-sized Windows server environments, Server Manager eliminates the need to individually open multiple management tools on each server.

This guide covers configuring Server Manager for first use, adding local and remote servers to the management pool, installing roles and features, interpreting dashboard alerts, and customizing the console for your environment.

Opening Server Manager

Server Manager opens automatically at logon on Windows Server 2016 with Desktop Experience. If it does not launch automatically, open it from the Start menu or run it from a command prompt:

ServerManager.exe

The Dashboard is the default landing page. It shows alerts aggregated from all managed servers, broken down by role, and provides quick links to add roles, add servers, and create server groups.

Step 1: Configure Server Manager to Start Automatically

If Server Manager does not launch at logon, enable it in the Properties dialog. From the Manage menu, select Server Manager Properties and ensure the Do not start Server Manager automatically at logon checkbox is cleared. Alternatively, configure this with a registry key:

Set-ItemProperty -Path "HKCU:SoftwareMicrosoftServerManager" -Name "DoNotOpenServerManagerAtLogon" -Value 0

Step 2: Add Remote Servers

Server Manager can manage multiple remote servers from a single console. From the Manage menu, select Add Servers. You can search Active Directory for computers by name, import from a text file, or enter names manually.

Prerequisites for managing a remote server include the Windows Remote Management (WinRM) service running on the remote server, the remote server’s firewall allowing Server Manager traffic, and the current user having administrative rights on the remote server. Enable WinRM on a remote server via PowerShell:

Enable-PSRemoting -Force

Once added, remote servers appear in All Servers and can be targeted for role installation, event viewing, and service management from the local Server Manager console.

Step 3: Install Roles and Features

From the Manage menu, select Add Roles and Features to launch the wizard. Work through the wizard steps: select role-based or feature-based installation, choose the target server from the server pool, select the roles to add (such as DNS Server, DHCP Server, or Web Server IIS), and review dependencies. The wizard offers to restart the server automatically after installation if required.

Install roles and features with PowerShell for unattended automation:

Install-WindowsFeature -Name Web-Server -IncludeManagementTools -ComputerName Server02

Remove roles and features with:

Remove-WindowsFeature -Name Web-Server -ComputerName Server02

Step 4: Create Server Groups

Server groups let you organize servers by function or location for easier management. From the Manage menu, select Create Server Group. Give the group a name such as Web Servers or Domain Controllers, and add the relevant servers from the managed server pool.

Each group gets its own tile on the Dashboard showing aggregated event counts, service state, and performance alerts for the servers in that group. Clicking the tile opens a filtered view showing only the servers in that group.

Step 5: Interpret Dashboard Alerts

The Dashboard displays a tile for each installed role and each server group. Red numbers in the tiles indicate alert conditions: services that have stopped, events at Warning or Critical level in the last 24 hours, or performance threshold violations. Click a red number to see the details and navigate directly to the relevant server or event log.

The Manageability column in All Servers indicates the communication status with each managed server. A status of Online means Server Manager can communicate with the server. Target computer not accessible means WinRM is not responding — investigate the WinRM service, firewall rules, and network connectivity on the target.

Step 6: Manage Services from Server Manager

Right-click any server in All Servers or a server group to access a context menu with shortcuts to Computer Management, Remote Desktop, PowerShell, and Windows PowerShell. You can also right-click a server and select Services to see and control all services on that server without leaving Server Manager.

Step 7: Configure Server Manager Notifications

Server Manager can send email notifications when managed servers report critical events. Configure this from Tools then Task Scheduler by creating a scheduled task that uses the Server Manager COM infrastructure. Alternatively, integrate Server Manager alerts with System Center Operations Manager or a SIEM tool by reading the event data Server Manager surfaces in the Windows event log under the ServerManager source.

Managing Server Manager from PowerShell

The ServerManager module in PowerShell exposes cmdlets for the most common tasks. List all installed features:

Get-WindowsFeature | Where-Object Installed -eq $true | Select-Object Name, DisplayName, InstallState

Check what features are available but not installed:

Get-WindowsFeature | Where-Object InstallState -eq 'Available' | Select-Object Name, DisplayName

Server Manager on Windows Server 2016 is the starting point for all server administration in GUI environments. Keeping its server pool accurate, server groups organized, and dashboard alerts reviewed regularly ensures that issues across your entire server estate surface quickly and can be addressed before they affect users or services.