How to Use Server Manager for Role Administration on Windows Server 2025

Server Manager is the built-in management console that ships with every edition of Windows Server 2025 and provides a single pane of glass for monitoring server health, installing roles and features, reviewing events, and running Best Practices Analyzer scans — all without leaving a central dashboard. Whether you are managing a single server or a pool of remote machines across your organisation, Server Manager dramatically reduces the time spent switching between individual MMC snap-ins. While Windows Admin Center is Microsoft’s strategic successor for browser-based management, Server Manager remains the fastest way to perform day-to-day role administration directly on the server or from a management workstation running Remote Server Administration Tools (RSAT). This guide covers every major aspect of Server Manager on Windows Server 2025, from basic navigation through to PowerShell automation of role installation.

Prerequisites

Windows Server 2025 (Standard or Datacenter) with a Desktop Experience installation (Server Core does not include Server Manager GUI).
Local Administrator or Domain Administrator privileges.
Network connectivity to any remote servers you intend to manage.
WinRM enabled on remote servers (enabled by default in domain environments; run Enable-PSRemoting -Force on workgroup servers).
RSAT installed if running Server Manager from a Windows 10/11 management workstation.

Step 1: Launch Server Manager and Understand the Dashboard

Server Manager opens automatically when you log on to a server with Desktop Experience. To open it manually, click Start, type Server Manager, and press Enter, or run servermanager.exe from a Run dialog.

The Dashboard is the default landing page and contains five coloured tiles for the most common issue categories:

Manageability — highlights servers where Server Manager cannot connect or retrieve status.
Events — shows critical and error events collected from all managed servers in the last 24 hours.
Services — lists services across managed servers that are stopped but configured to start automatically.
Performance — flags CPU or memory alerts from any managed server.
BPA Results — surfaces Best Practices Analyzer warnings from the most recent scans.

The left navigation pane contains four top-level nodes: Dashboard, Local Server, All Servers, and individual role nodes (DNS, File Services, Hyper-V, etc.) that appear automatically when the corresponding role is installed.

Step 2: Configure Local Server Properties

Click Local Server in the left pane. This page aggregates the most important server configuration items in one place, including:

Computer name and domain or workgroup membership — click the link to open System Properties.
Windows Firewall status — click to open Windows Defender Firewall.
Remote Desktop state — click to enable or disable RDP.
Windows Update settings — click to open Windows Update.
IE Enhanced Security Configuration (if applicable) — click to toggle on or off.
NIC Teaming status, time zone, product ID, and installed RAM.

Each property is a clickable hyperlink that opens the relevant configuration dialog, making Local Server a one-stop configuration panel for initial server setup.

Step 3: Add Remote Servers to Server Manager

Server Manager can manage multiple remote servers simultaneously through a single console session. To add remote servers, click Manage in the top-right menu bar, then select Add Servers. The Add Servers dialog offers three search methods:

Active Directory — search for computer accounts by name, operating system, or OU.
DNS — search by DNS name or IP address.
Import — import a text file containing one server name per line.

After adding servers, they appear in the All Servers node. Server Manager periodically polls each remote server for health status, events, and running services, aggregating the data into the Dashboard tiles.

Ensure WinRM is running on remote servers before adding them. Use PowerShell to verify and enable remotely if needed:

# Enable WinRM on a remote server (requires admin credentials)
Invoke-Command -ComputerName "SRV-APP01" -ScriptBlock {
    Enable-PSRemoting -Force
    Set-Service -Name WinRM -StartupType Automatic
}

Step 4: Create Server Groups for Organised Management

When managing many servers, organising them into logical Server Groups simplifies monitoring. Click Manage > Create Server Group. Provide a group name (e.g., Web Servers, Database Servers), then use the same Active Directory, DNS, or Import method to add servers to the group.

Once created, each server group appears as a new node in the left pane with its own Dashboard view scoped to just those servers. This lets you monitor all web servers as a unit without scrolling through unrelated machines in the All Servers view.

Step 5: Add Roles and Features Using the Wizard

The Add Roles and Features Wizard is the most visible capability of Server Manager. Click Manage > Add Roles and Features. The wizard walks through seven pages:

Before You Begin — informational; check the prerequisites reminder and click Next.
Installation Type — choose Role-based or feature-based installation for the standard path, or Remote Desktop Services installation for VDI deployments.
Server Selection — select the target server from the server pool (local or any remote server added in Step 3).
Server Roles — browse and select the roles to install. Expanding a role reveals sub-roles and role services. Required dependencies are highlighted automatically.
Features — select optional Windows features that are not bound to a specific role (e.g., .NET Framework, Telnet Client, Failover Clustering).
Confirmation — review the list of roles, role services, and features to be installed. Check Restart the destination server automatically if required for unattended installation.
Results — installation progress is shown in real time. A log file path is displayed upon completion.

Step 6: Install Roles with PowerShell (ServerManager Module)

Every action the Add Roles and Features Wizard performs can be scripted using the ServerManager module, which is included in Windows Server 2025 by default. The primary cmdlets are Get-WindowsFeature, Install-WindowsFeature, and Uninstall-WindowsFeature.

# List all available roles and features with their installation state
Get-WindowsFeature | Select-Object Name, DisplayName, Installed, InstallState

# Search for features matching a keyword
Get-WindowsFeature | Where-Object Name -like "*DNS*"

# Install the DNS Server role with management tools
Install-WindowsFeature -Name DNS -IncludeManagementTools

# Install IIS Web Server with common role services
Install-WindowsFeature -Name Web-Server `
    -IncludeManagementTools `
    -IncludeAllSubFeature

# Install a role on a remote server
Install-WindowsFeature -Name FileAndStorage-Services `
    -ComputerName "SRV-FILE01" `
    -IncludeManagementTools

# Uninstall a role
Uninstall-WindowsFeature -Name DNS -IncludeManagementTools

# Export a role/feature list for replication to another server
Get-WindowsFeature | Where-Object Installed | Export-Clixml -Path C:TempInstalledFeatures.xml

# Import and install on a target server
$Features = Import-Clixml -Path C:TempInstalledFeatures.xml
Install-WindowsFeature -Name $Features.Name -IncludeManagementTools

Step 7: Run Best Practices Analyzer Scans

The Best Practices Analyzer (BPA) compares role configurations against Microsoft’s documented best practices and produces a report of violations, warnings, and informational findings. In Server Manager, navigate to a role node (e.g., File and Storage Services), scroll to the Best Practices Analyzer tile, and click Start BPA Scan.

Results are colour-coded: red for errors (configuration violates a best practice that could cause reliability issues), yellow for warnings (deviations worth reviewing), and blue for informational items. Run BPA scans from PowerShell for automation:

# List available BPA models
Get-BpaModel

# Run a BPA scan for the DNS Server role
Invoke-BpaModel -ModelId Microsoft/Windows/DNSServer

# Retrieve BPA results and filter for errors
Get-BpaResult -ModelId Microsoft/Windows/DNSServer |
    Where-Object Severity -eq Error |
    Select-Object Title, Category, Problem, Resolution

# Run BPA on a remote server
Invoke-BpaModel -ModelId Microsoft/Windows/FileServices -ComputerName SRV-FILE01

Step 8: Configure Server Manager Startup Behaviour

By default, Server Manager launches automatically at logon. To suppress this, open Manage > Server Manager Properties and check Do not start Server Manager automatically at logon. You can also configure the refresh interval for data collection in this dialog (default is 10 minutes).

To suppress the startup via Group Policy across multiple servers:

Open Group Policy Management and create or edit a GPO linked to your servers OU.
Navigate to Computer Configuration > Preferences > Control Panel Settings > Scheduled Tasks.
Alternatively, use the registry preference: HKLMSOFTWAREMicrosoftServerManager, value DoNotOpenServerManagerAtLogon = DWORD 1.

# Disable Server Manager auto-start via registry (run on target servers)
Set-ItemProperty -Path "HKLM:SOFTWAREMicrosoftServerManager" `
    -Name DoNotOpenServerManagerAtLogon `
    -Value 1 `
    -Type DWord

Step 9: Understand Server Manager Limitations vs Windows Admin Center

Server Manager was designed for managing a handful of servers in a single-site environment. As your infrastructure grows, you will encounter its limitations:

Server Manager does not scale well beyond approximately 100 managed servers — polling overhead becomes significant.
It does not support Azure Arc-enabled servers or hybrid management scenarios.
Role-specific management remains fragmented across different MMC snap-ins (DNS Manager, DHCP Manager, Hyper-V Manager, etc.).
Server Manager cannot manage Windows Server Core or Nano Server without WinRM, and its GUI is absent entirely on those installations.
There is no mobile or browser-based access — it requires a full Windows desktop session.

Windows Admin Center addresses all these limitations through a browser-based architecture that works equally well for on-premises, Azure, and hybrid environments. However, Server Manager remains the faster choice for quick, local role management on a desktop-experience server.

Conclusion

Server Manager on Windows Server 2025 remains an indispensable tool for administrators who need to quickly install roles, review events, and enforce best practices across a managed server pool. By combining the graphical wizard for exploratory work with the ServerManager PowerShell module for automation, you can build repeatable deployment scripts that install and validate role configurations consistently across every server in your environment. For larger and hybrid deployments, treat Server Manager as a complement to Windows Admin Center rather than a replacement — use each tool where it excels, and layer PowerShell scripting over both for true infrastructure-as-code discipline.

Links

Newsletter

Contact