How to Manage Windows Server 2012 R2 with Windows Admin Center

How to Manage Windows Server 2012 R2 with Windows Admin Center

Windows Admin Center (WAC) is Microsoft’s modern, browser-based server management platform that provides a unified interface for managing Windows Server, failover clusters, and hyperconverged infrastructure. While Windows Admin Center itself is a modern tool developed after Windows Server 2012 R2’s initial release, it fully supports managing Windows Server 2012 R2 as a managed node — allowing administrators to use WAC’s web interface to manage older servers without requiring GUI upgrades or Remote Desktop sessions.

Windows Admin Center is installed on a gateway server or Windows 10/11 management workstation and connects to managed servers via WinRM. For Windows Server 2012 R2 environments that may be mid-lifecycle, WAC provides a significant management upgrade — modern browser-based tools for performance monitoring, event viewing, PowerShell sessions, certificate management, and role configuration — without touching the managed server’s software. This guide covers installing WAC, connecting to WS2012 R2 servers, and using its major management modules.

Prerequisites

– A gateway server running Windows Server 2016/2019/2022 or a Windows 10/11 management workstation to host WAC
– Windows Server 2012 R2 as the managed node
– WinRM enabled on Windows Server 2012 R2 (Enable-PSRemoting -Force)
– Windows Management Framework 5.1 installed on WS2012 R2 (updates PowerShell from 4.0 to 5.1 for better WAC compatibility)
– .NET Framework 4.6 or later on the managed node
– A modern browser (Chrome, Edge Chromium, Firefox) on the administrator’s workstation
– HTTPS certificate for the WAC gateway

Step 1: Install Windows Management Framework 5.1 on WS2012 R2

Windows Server 2012 R2 ships with PowerShell 4.0. Install WMF 5.1 to improve Windows Admin Center compatibility and gain access to additional PowerShell features:

# Download WMF 5.1 for Windows Server 2012 R2:
# https://www.microsoft.com/en-us/download/details.aspx?id=54616
# File: Win8.1AndW2K12R2-KB3191564-x64.msu

# Install from command line (after downloading the MSU file)
wusa.exe "Win8.1AndW2K12R2-KB3191564-x64.msu" /quiet /norestart

# Or install via PowerShell after placing the MSU in C:Temp
$msu = "C:TempWin8.1AndW2K12R2-KB3191564-x64.msu"
Start-Process wusa.exe -ArgumentList "$msu /quiet /norestart" -Wait

# Verify PowerShell version after restart
$PSVersionTable.PSVersion

Also install .NET Framework 4.6 if not present:

# Check .NET Framework version
(Get-ItemProperty "HKLM:SOFTWAREMicrosoftNET Framework SetupNDPv4Full").Release
# Release value 393295 or higher = .NET 4.6 or later

# Install .NET 4.6 via Windows Update or DISM if needed
# Microsoft .NET Framework 4.6 is available as KB3045560

Step 2: Install Windows Admin Center on the Gateway Server

Download Windows Admin Center from Microsoft and install on the gateway server:

# Download WAC installer from https://aka.ms/windowsadmincenter
# Current version: WindowsAdminCenter[version].msi

# Install WAC as a service on Windows Server (recommended for shared team access)
# Run the MSI and accept defaults, or install silently:
msiexec /i WindowsAdminCenter2306.msi /qn /L*v C:LogsWAC_install.log SME_PORT=443 SSL_CERTIFICATE_OPTION=generate

# The installer will:
# - Install WAC as a Windows Service named "ServerManagementGateway"
# - Configure HTTPS on the specified port (443 by default)
# - Generate a self-signed certificate (replace with CA cert for production)

# Verify the service is running
Get-Service ServerManagementGateway | Select-Object Name, Status, StartType

Step 3: Access Windows Admin Center

Open a browser on the management workstation and navigate to the WAC URL:

# If WAC is on the same machine (desktop mode)
https://localhost

# If WAC is on a gateway server
https://WACGateway.domain.com

# For a non-standard port
https://WACGateway.domain.com:6516

Log in with domain administrator credentials or local administrator credentials. The home screen shows the connection list, initially containing only the local machine.

Step 4: Add Windows Server 2012 R2 as a Managed Connection

Add your WS2012 R2 servers to Windows Admin Center:

1. On the WAC home screen, click Add
2. Select Windows Server
3. Enter the server name or IP address
4. Optionally provide alternate credentials
5. Click Add

WAC will test connectivity and display the server in the connection list. If connectivity fails, troubleshoot using PowerShell:

# Test WinRM connectivity from the WAC gateway to the managed server
Test-WSMan -ComputerName "WS2012R2-Server01" -Verbose

# Ensure WinRM is running on the target
Invoke-Command -ComputerName "WS2012R2-Server01" -ScriptBlock { Get-Service WinRM }

Step 5: Use the Overview Dashboard

Click on a managed Windows Server 2012 R2 connection to open its management dashboard. The Overview page displays:

– CPU usage (real-time graph and average)
– Memory usage (used vs. available)
– Network I/O (bytes sent/received per second)
– Disk I/O (read/write per second)
– Computer name, OS version, domain, uptime
– Quick action buttons: Restart, Shutdown, Edit computer ID

This single page provides the core health status that previously required opening multiple MMC consoles and remote desktoping to the server.

Step 6: Use the PowerShell Integration

WAC includes a browser-based PowerShell terminal for direct interactive command-line access to managed servers. Navigate to Tools > PowerShell in the left navigation. This opens a PowerShell session running directly on the managed server, entirely within the browser window — no separate Remote Desktop or PuTTY session required.

# Example commands run in WAC's browser PowerShell against WS2012 R2:

# Check disk space
Get-PSDrive -PSProvider FileSystem | Select-Object Name, Used, Free

# View top memory consumers
Get-Process | Sort-Object WorkingSet64 -Descending | Select-Object -First 10 Name, Id, @{N="MB"; E={[math]::Round($_.WorkingSet64/1MB,1)}}

# Check Windows Update pending restarts
(New-Object -ComObject Microsoft.Update.SystemInfo).RebootRequired

# View installed Windows updates
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 20 HotFixID, InstalledOn, Description

Step 7: Manage Certificates with WAC

Navigate to Tools > Certificates in WAC to manage the certificate stores on the managed WS2012 R2 server. The Certificates tool allows you to:

– Browse personal, trusted root, and intermediate certificate stores
– View certificate details (thumbprint, expiry date, subject, issuer, SANs)
– Import PFX certificates
– Export certificates
– Delete expired or revoked certificates

# PowerShell equivalent for certificate management on WS2012 R2
# Run locally or via Invoke-Command for remote management

# List all certificates in the Personal store with expiry
Get-ChildItem cert:LocalMachineMy | 
    Select-Object Subject, Thumbprint, NotBefore, NotAfter,
    @{N="DaysUntilExpiry"; E={($_.NotAfter - (Get-Date)).Days}} |
    Sort-Object NotAfter

# Alert on certificates expiring within 30 days
Get-ChildItem cert:LocalMachineMy | 
    Where-Object { $_.NotAfter -lt (Get-Date).AddDays(30) } |
    Select-Object Subject, NotAfter

Step 8: Manage Services and Processes

WAC’s Services tool shows all services with their current state, startup type, and the ability to start, stop, or restart them with a single click. The Processes tool provides a sortable list of running processes with CPU and memory usage — similar to Task Manager but accessible through the browser.

# Stop and restart a service via WAC PowerShell terminal
Restart-Service -Name "W3SVC" -Force

# Kill a process
Stop-Process -Name "notepad" -Force

# Change a service startup type
Set-Service -Name "Spooler" -StartupType Manual

Step 9: Configure WAC Gateway Access Control

Control who can access the WAC gateway and manage servers through it:

# WAC Gateway access is configured in the Settings > Access section
# Users can be added as: Administrators (full access) or Users (viewer access)

# Configure allowed groups via registry
Set-ItemProperty -Path "HKLM:SOFTWAREMicrosoftServerManagementGateway" `
    -Name "AllowedGroupMembers" -Value "DOMAINServerAdmins,DOMAINHelpDesk"

# Review WAC service configuration
Get-ItemProperty "HKLM:SOFTWAREMicrosoftServerManagementGateway"

Step 10: Manage Multiple Servers with WAC Tags and Groups

Organize managed servers using tags to create logical groupings for easier navigation:

1. On the WAC home page, select multiple servers
2. Click Tag and create a tag (e.g., “Production-Web,” “Branch-Office,” “SQL-Servers”)
3. Use the tag filter on the home page to show only servers with a specific tag

# Import many servers into WAC via PowerShell using the WAC connection management API
# Alternatively, use the WAC settings to import from a CSV file:
# Settings > Connections > Import/Export connections

# Create a server list CSV for bulk import
$servers = @("Server01","Server02","Server03","Server04")
$csv = $servers | ForEach-Object { "winsrv,$_,,$_" }
$csv | Out-File "C:Tempwac_servers.csv" -Encoding UTF8

# WAC import CSV format: type,name,tags,grouping

Summary

Windows Admin Center provides a significantly improved management experience for Windows Server 2012 R2 environments, offering browser-based access to dashboards, PowerShell terminals, certificate management, event viewing, and service management without requiring GUI updates to the managed servers themselves. By installing WMF 5.1 on managed WS2012 R2 servers to ensure WinRM and PowerShell compatibility, and deploying WAC on a modern gateway server, organizations can manage aging server infrastructure with modern tooling that requires only a web browser. This is particularly valuable for teams migrating away from Remote Desktop as the primary management interface, or consolidating management onto a single operations workstation.