How to Set Up System Center Operations Manager (SCOM) on Windows Server 2016

System Center Operations Manager (SCOM) is Microsoft’s enterprise-grade monitoring platform that provides comprehensive health monitoring, alerting, and performance tracking for Windows Server 2016, Linux servers, network devices, and cloud workloads. SCOM uses Management Packs (MPs) to define what to monitor and how to respond, making it highly extensible. This guide walks through installing SCOM, deploying the SCOM agent to Windows Server 2016 targets, and configuring a Management Pack for Windows Server monitoring.

Prerequisites

SCOM 2016 or SCOM 2019 management server installed and licensed. SQL Server (2014 SP2 or later) with an operational database and data warehouse database already configured. Active Directory domain with the SCOM management server and monitored Windows Server 2016 machines joined to the domain. The SCOM management server and SQL Server are typically separate roles from the monitored targets.

Step 1: Install the SCOM Operations Console

The Operations Console is the primary interface for SCOM administration. Run the SCOM setup media and choose Operations Console. Complete the installation wizard and connect to the management server when prompted. For SCOM 2016 command-line reference, use the Operations Manager Shell PowerShell module:

Import-Module OperationsManager
New-SCOMManagementGroupConnection -ManagementServer "SCOM-MGT01"

Step 2: Deploy the SCOM Agent via the Discovery Wizard

In the Operations Console, navigate to Administration > Device Management > Discovery Wizard. Click Discover. Choose Windows computers, Advanced discovery. Select the domain and click Discover. SCOM scans the domain for Windows computers. Select the Windows Server 2016 machines to monitor and click Next. Choose Automatic agent installation. Enter an account with administrative access to the target servers. Click Finish.

SCOM pushes the MOMAgent.msi installer to each target server, installs and configures the agent, and begins collecting data within minutes.

Step 3: Install the SCOM Agent Manually

For environments where push installation is blocked by firewall rules, install the agent manually on each Windows Server 2016 machine. Copy MOMAgent.msi from the SCOM management server’s AgentManagementamd64 folder to the target and run:

msiexec /i MOMAgent.msi /quiet MANAGEMENT_GROUP=SCOM_MG01 MANAGEMENT_SERVER_DNS=SCOM-MGT01.domain.local ACTIONS_USE_COMPUTER_ACCOUNT=1

After installation, verify the Microsoft Monitoring Agent service is running:

Get-Service HealthService

Step 4: Approve Pending Agents

If SCOM is configured to require manual approval for new agents, navigate to Administration > Device Management > Pending Management. Right-click pending agents and select Approve. Agents will begin reporting health data to the management group within a few minutes of approval.

Step 5: Import the Windows Server Management Pack

Management Packs define monitoring workflows. The Microsoft Windows Server 2016 Operating System MP is available from the Microsoft Download Center or the SCOM MP catalog. In the Operations Console, navigate to Administration > Management Packs > Import Management Packs. Click Add > Add from disk. Browse to the downloaded MP .msi or .mpb file. Resolve dependencies if prompted and click Install.

To import via PowerShell:

Import-SCOMManagementPack -FullName "C:MPsMicrosoft.Windows.Server.2016.mp"

Step 6: Configure Alert Notifications

SCOM can send email notifications when alerts are raised. In the Operations Console, navigate to Administration > Notifications > Channels. Click New > E-Mail (SMTP). Configure the SMTP server address, reply-to address, and a display name. Click Finish.

Create a subscription to define who receives which alerts: Administration > Notifications > Subscriptions > New. Set conditions (such as alert severity = Critical), select the notification channel, and specify recipient addresses. SCOM sends email when matching alerts are generated.

Step 7: Create a Custom Monitor

SCOM monitors can check Windows services, performance thresholds, and event log entries. To create a service monitor via the Operations Console, navigate to Authoring > Monitors. Right-click Unit Monitor, select Create a monitor. Choose Windows Services under Service-specific monitors. Select the target class (Windows Server 2016 Operating System) and the service to monitor (for example, wuauserv). Set the unhealthy state to raise a Critical alert. Complete the wizard and enable the monitor.

To create a simple threshold monitor via PowerShell:

Get-SCOMManagementPack -DisplayName "Windows Server 2016 Operating System" | Get-SCOMMonitor | Where-Object {$_.DisplayName -like "*CPU*"} | Format-Table DisplayName, Enabled

Step 8: Review Health Dashboard

In the Monitoring workspace, navigate to Microsoft Windows Server > Windows Server 2016 Computers. The Health Explorer view shows a hierarchical health model: from overall computer health down to individual monitors for CPU, memory, disk, services, and more. Red and yellow states indicate problems requiring attention. Double-click any object to open Health Explorer for drill-down diagnosis.

Best Practices

Keep Management Packs updated as Microsoft releases new versions with improved monitors and fixes. Tune alert thresholds to reduce noise—SCOM’s default thresholds are often too sensitive for production environments. Use SCOM’s Maintenance Mode feature to suppress alerts during planned maintenance windows. Size the data warehouse SQL database for at least 400 days of retention to enable meaningful trend analysis. Combine SCOM with Azure Monitor for a hybrid monitoring strategy spanning on-premises and cloud workloads.