How to Configure Server Manager on Windows Server 2012 R2

How to Configure Server Manager on Windows Server 2012 R2

Server Manager is the primary management console introduced in Windows Server 2008 and significantly enhanced in Windows Server 2012 R2 to support multi-server management from a single pane of glass. On Windows Server 2012 R2, Server Manager provides a unified dashboard for installing and managing roles and features, monitoring server health across multiple servers simultaneously, configuring server groups, and launching role-specific management tools — all without requiring separate MMC consoles for each task.

For administrators managing multiple Windows Server 2012 R2 instances, Server Manager’s multi-server capabilities reduce the need to remote desktop into each server individually. The Manageability column in the Servers view quickly surfaces errors and warnings across all monitored servers, while the role-specific pages aggregate status information from all servers running that role. This guide covers initial configuration, adding servers to manage, creating server groups, customizing the dashboard, and using Server Manager for role installation and ongoing monitoring.

Prerequisites

– Windows Server 2012 R2 management workstation or server (Server Manager can run on Windows 8.1 with RSAT installed)
– Administrative credentials on all servers to be managed
– WinRM configured and running on managed servers (enable with Enable-PSRemoting -Force)
– Network connectivity between the management computer and all target servers
– DNS resolution working for all server names
– Servers joined to the same Active Directory domain or trusted domains

Step 1: Open and Familiarize with the Dashboard

Server Manager opens automatically when you log in to Windows Server 2012 R2. Launch it manually from the taskbar pin or:

servermanager.exe

The Dashboard provides:

– Welcome tile: Quick-start links for adding roles/features, adding servers, creating server groups
– Roles and Server Groups tiles: Colored status tiles for each installed role and server group showing alert counts (red = errors, yellow = warnings)
– Events tile: Summary of critical and error events across all managed servers
– Services tile: Services in stopped state that have automatic start configured
– Best Practices Analyzer tile: Warnings from the BPA scanner
– Performance tile: CPU and memory alerts

Step 2: Add Remote Servers to Server Manager

Add servers to Server Manager to enable multi-server management:

In the GUI: Click Manage > Add Servers. In the Add Servers dialog, search Active Directory for server names, import a list from a text file, or enter IP addresses manually.

Verify WinRM is enabled on servers before adding them:

# On each target server (run as administrator)
Enable-PSRemoting -Force
Set-Service WinRM -StartupType Automatic

# Verify WinRM is accessible from the management server
Test-WSMan -ComputerName "Server01"
Test-WSMan -ComputerName "Server02"

For non-domain servers, configure TrustedHosts on the management computer:

Set-Item WSMan:localhostClientTrustedHosts -Value "192.168.1.100,192.168.1.101" -Force

Step 3: Create Server Groups

Server Groups in Server Manager allow you to organize servers by function, location, or team. Creating groups helps focus monitoring attention and performs batch operations on related servers.

Create a server group via the GUI: Click Manage > Create Server Group. Name the group (e.g., “Web Servers,” “Database Servers,” “Branch Office”), then add servers to the group by name or IP address.

After creating groups, dedicated tiles appear on the Dashboard for each group. The tiles show the aggregate health status — if any server in the group has errors, the tile turns red. Click the tile to navigate to the group view showing all servers in that group with their individual status.

# Verify Server Manager settings file location (contains server lists and groups)
# Server Manager stores configuration at:
$configPath = "$env:APPDATAMicrosoftWindowsServerManagerServerList.xml"
if (Test-Path $configPath) {
    Get-Content $configPath | Select-Object -First 30
}

Step 4: Install Roles and Features from Server Manager

Server Manager’s Add Roles and Features Wizard provides a GUI for installing Windows roles and features. The wizard also supports remote installation — you can install a role on a remote server without opening Remote Desktop to that server.

Equally important is installing roles via PowerShell using the ServerManager module for automation:

# List all available roles and features
Get-WindowsFeature | Where-Object InstallState -eq "Available" | Select-Object Name, DisplayName | Sort-Object Name

# Install a role locally
Install-WindowsFeature -Name "Web-Server" -IncludeManagementTools

# Install a role on a remote server
Install-WindowsFeature -Name "Web-Server" -ComputerName "WebServer01" -IncludeManagementTools

# Install multiple features with a single command
Install-WindowsFeature -Name "RSAT-AD-Tools","RSAT-DNS-Server","RSAT-DHCP" -IncludeAllSubFeature

# Check current feature status across multiple servers
$servers = @("Server01","Server02","Server03")
foreach ($server in $servers) {
    $features = Get-WindowsFeature -ComputerName $server | Where-Object InstallState -eq "Installed"
    Write-Host "$server installed features: $($features.Count)"
    $features | Select-Object Name | Sort-Object Name | ForEach-Object { Write-Host "  $($_.Name)" }
}

Step 5: Configure Server Manager Startup and Auto-Refresh

Configure Server Manager behavior through the Manage menu:

Click Manage > Server Manager Properties to access:

– Do not start Server Manager automatically at logon: Disables automatic startup (useful on servers that should not have GUIs running)
– Refresh interval: How often Server Manager polls servers for updated status (default 10 minutes)

Configure from PowerShell by modifying the registry:

# Disable Server Manager auto-start at logon
New-ItemProperty -Path "HKCU:SOFTWAREMicrosoftServerManager" `
    -Name "DoNotOpenServerManagerAtLogon" `
    -Value 1 -PropertyType DWORD -Force

# For all users (requires admin): Set via Group Policy or registry run
Set-ItemProperty -Path "HKLM:SOFTWAREMicrosoftServerManager" `
    -Name "DoNotPopWACConsoleAtSMTabLaunch" -Value 1

Step 6: Use the Best Practices Analyzer

The Best Practices Analyzer (BPA) scans installed roles against Microsoft’s best practice guidelines and reports deviations. Run BPA from Server Manager’s role pages or via PowerShell:

# List available BPA models
Get-BpaModel | Select-Object Id, Name, LastScanTime

# Run BPA for IIS
Invoke-BpaModel -ModelId "Microsoft/Windows/IIS"

# Run BPA for Active Directory
Invoke-BpaModel -ModelId "Microsoft/Windows/DirectoryServices"

# Get BPA results and filter for warnings and errors
Get-BpaResult -ModelId "Microsoft/Windows/IIS" | 
    Where-Object { $_.Severity -in "Warning","Error" } |
    Select-Object Severity, Title, Problem, Impact, Resolution | 
    Format-List

Step 7: Monitor Events and Services Across Servers

Server Manager aggregates events from all managed servers in its Events view. Navigate to All Servers > Events to see events from all servers in one view. You can filter by server, severity, event ID, and time range.

The Services view under All Servers shows services that have stopped unexpectedly (services configured for automatic start but currently stopped). This is particularly useful for catching services that have crashed:

# PowerShell equivalent - find stopped automatic-start services across multiple servers
$servers = @("Server01","Server02","Server03")

$stoppedServices = Invoke-Command -ComputerName $servers -ScriptBlock {
    Get-Service | Where-Object { $_.StartType -eq "Automatic" -and $_.Status -ne "Running" } |
        Select-Object Name, DisplayName, Status
} -ErrorAction SilentlyContinue

$stoppedServices | Select-Object PSComputerName, Name, DisplayName, Status | 
    Sort-Object PSComputerName, Name | Format-Table -AutoSize

Step 8: Configure Role-Specific Pages

When roles are installed, Server Manager adds dedicated pages for each role. These pages aggregate role-specific information across all servers running that role. For example, the DNS page shows all DNS servers being managed, their event logs, services status, and provides quick links to the DNS Manager console for each.

Configure which servers appear in role pages by managing role-specific server lists. For example, to add a server to the IIS role view in Server Manager, the server must have the Web-Server feature installed AND be added to the Server Manager server list with appropriate credentials.

# Verify which roles are installed on each managed server
$servers = @("WebServer01","WebServer02","DBServer01")

foreach ($server in $servers) {
    $roles = Get-WindowsFeature -ComputerName $server | 
        Where-Object { $_.InstallState -eq "Installed" -and $_.FeatureType -eq "Role" } |
        Select-Object Name, DisplayName
    
    Write-Host "`n=== $server installed roles ===" -ForegroundColor Cyan
    $roles | ForEach-Object { Write-Host "  $($_.DisplayName)" }
}

Step 9: Configure Remote Management Credentials

When managing servers in different domains or workgroups, configure explicit credentials for Server Manager to use:

# Right-click a server in the All Servers list > Manage As...
# Enter alternate credentials for that specific server

# Test connectivity with specific credentials from PowerShell
$cred = Get-Credential "DOMAIN2AdminUser"
Invoke-Command -ComputerName "Server01.domain2.local" -Credential $cred -ScriptBlock { hostname }

Step 10: Export and Save Server Manager Data

Export server and role information for documentation and auditing:

# Export installed features report for all managed servers
$servers = @("Server01","Server02","Server03")
$report  = @()

foreach ($server in $servers) {
    $features = Get-WindowsFeature -ComputerName $server | Where-Object InstallState -eq "Installed"
    foreach ($f in $features) {
        $report += [PSCustomObject]@{
            Server      = $server
            FeatureName = $f.Name
            DisplayName = $f.DisplayName
            FeatureType = $f.FeatureType
        }
    }
}

$report | Export-Csv "C:ReportsServerRolesInventory.csv" -NoTypeInformation
Write-Host "Report saved with $($report.Count) entries"

Summary

Server Manager on Windows Server 2012 R2 delivers a powerful multi-server management experience that significantly reduces the time required for daily administrative tasks. By properly adding all managed servers to the console, organizing them into logical groups, enabling WinRM for remote management, and leveraging the PowerShell ServerManager module for scriptable role installations and audits, administrators can manage dozens of servers efficiently from a single workstation. The role-specific pages, Best Practices Analyzer integration, and real-time event and service monitoring make Server Manager the operational hub for Windows Server 2012 R2 environments of any scale.