Introduction to System Center Operations Manager

System Center Operations Manager (SCOM) is Microsoft’s enterprise monitoring platform designed for large-scale Windows environments. It uses management packs — extensible plug-ins — to provide out-of-the-box monitoring intelligence for Windows Server operating systems, SQL Server, IIS, Active Directory, Hyper-V, and hundreds of third-party applications. SCOM uses agents deployed to monitored servers to collect performance data, events, and health state information, which is aggregated at the Management Server and stored in SQL Server databases. The Operations Console provides dashboards, alert views, performance graphs, and topology diagrams. This guide covers the infrastructure requirements, deploying the SCOM Management Server on Windows Server 2019, installing agents, and importing management packs.

SCOM Infrastructure Components

A typical SCOM deployment consists of: Management Server (the core SCOM engine, handles agent communications and alert processing), Operational Database (SQL Server database storing current monitoring state and active alerts), Data Warehouse Database (SQL Server database for historical reporting data), Reporting Server (SQL Server Reporting Services for SCOM reports), Web Console (IIS-based web interface for browser access), and Gateway Server (optional, for monitoring servers in untrusted domains or DMZs via certificate-based authentication).

For production environments monitoring up to 500 agents, a single Management Server suffices. For larger environments, deploy multiple Management Servers in a Management Group with a Resource Pool for high availability. All SCOM components require Windows Server 2019 Standard or Datacenter, and the SQL Server databases require SQL Server 2019 or SQL Server 2022.

Prerequisites for SCOM Management Server on Windows Server 2019

Before installing SCOM, prepare the server with the following prerequisites. Install required Windows features:

Install-WindowsFeature -Name Web-Server, Web-ASP-Net45, Web-Net-Ext45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Static-Content, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Http-Redirect, Web-Http-Logging, Web-Request-Monitor, Web-Windows-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, NET-WCF-TCP-Activation45 -IncludeManagementTools

Install the Microsoft Report Viewer 2015 Runtime and SQL Server Native Client 2012. Create a dedicated domain service account (e.g., DOMAINscom-action) for the SCOM action account and a SCOM data access account (DOMAINscom-das). Grant the action account local administrator rights on the Management Server. The SQL Server service account and the SCOM action account need appropriate SQL Server permissions configured during the SCOM setup wizard.

Installing SCOM Management Server

Mount the System Center Operations Manager ISO and run Setup.exe. Click Install under Operations Manager. On the Getting Started page, select Management Server (and optionally Web Console). Enter the Management Group name — this is a permanent identifier for your SCOM environment, choose carefully as it cannot be changed without reinstalling.

On the Configure Operational Database page, enter the SQL Server instance name (e.g., SQLSERVER01SCOM) and the database name (OperationsManager). Specify the database size — 1000 MB minimum, 4000 MB recommended for production. On the Configure Data Warehouse page, enter the data warehouse SQL instance and database name (OperationsManagerDW).

Configure the SCOM service accounts — the Management Server Action Account should be the DOMAINscom-action account. Complete the wizard. SCOM installation takes 15–30 minutes. After completion, open the Operations Manager Console from the Start menu.

Installing SCOM Agents on Windows Server 2019

SCOM agents can be deployed using Discovery and push-installation from the Management Server, or manually via the MOMAgent.msi installer. To push-install agents from the Operations Console, navigate to Administration > Device Management > Agent Managed. Click Discovery Wizard in the Actions pane. Select Windows Computers, choose Advanced Discovery, and enter the computer name or IP range to scan. Provide credentials with local administrator rights on the target servers. Review the discovered computers and click Agent Install to begin deployment.

For manual agent installation on Windows Server 2019 (useful for servers in DMZs or restricted networks), run the MOMAgent.msi from the SCOM installation media:

msiexec /i MOMAgent.msi /quiet MANAGEMENT_GROUP="SCOM-PROD" MANAGEMENT_SERVER_DNS="scom-mgmt01.domain.com" MANAGEMENT_SERVER_PORT=5723 ACTIONSUSER="DOMAINscom-action" ACTIONSPWD="ActionAccountPassword" AcceptEndUserLicenseAgreement=1

After installation, the agent appears in Administration > Pending Management. Select it and click Approve to bring it under management.

Importing Windows Server 2019 Management Packs

Management Packs (MPs) define the monitoring rules, alerts, performance collection, and dashboards for specific technologies. Import the Windows Server 2019 management packs to start monitoring OS-level metrics. In the Operations Console, navigate to Administration > Management Packs > Import Management Packs.

Select Add from Catalog (requires internet access) or Add from disk for offline import. Search for Windows Server Operating System and import the following management packs: Microsoft Windows Server 2019 Operating System, Microsoft Windows Server 2016 and 2019 Monitoring, Windows Server 2019 Core Monitoring, and Windows Server IIS 10 (if IIS is running).

Download management packs from the Microsoft Download Center or the SCOM catalog at systemcentermarketplace.com when importing from disk. After import, the Operations Console will begin populating health states, alerts, and performance data for monitored Windows Server 2019 systems.

Configuring Alert Notification Subscriptions

SCOM routes alerts to the operations team using Notification Subscriptions. First, configure the SMTP notification channel. In Administration > Notifications > Channels, create a new Email channel. Specify the SMTP server address, port, sender address, and encoding. Test the channel by clicking the test button — a test email should arrive in the configured inbox.

Create Subscribers (the recipients) under Administration > Notifications > Subscribers. Create one subscriber per team member or distribution group. Then create a Subscription under Administration > Notifications > Subscriptions. Configure the subscription to notify the subscriber for all Critical and Warning alerts from the Windows Server 2019 management pack. Set a notification delay to avoid alert storms during maintenance windows.

Using Performance Views and Dashboards

Navigate to Monitoring in the Operations Console. Expand the Microsoft Windows Server node to see health state views, alert views, and performance views for all monitored Windows Server 2019 systems. The Windows Server Dashboard provides a summary of server health states across the environment.

Click on a specific server in any view to open the Health Explorer, which shows the hierarchical health model for that server — from individual monitors (CPU, memory, disk) up to the overall server health rollup. Red indicates Critical, Yellow indicates Warning, and Green indicates Healthy. Right-click on a monitor and select Overrides to adjust thresholds — for example, change the disk space critical threshold from the default 5% free to 10% free to alert earlier.

Maintenance Mode for Planned Downtime

Put a server into Maintenance Mode before performing planned maintenance to suppress alerts during the window. In the Monitoring view, right-click the server and select Maintenance Mode > Start Maintenance Mode. Specify the duration and reason. SCOM will suppress all alerts for this server until the maintenance window expires or is manually ended. Automate maintenance mode scheduling via PowerShell:

Import-Module OperationsManager
New-SCOMMaintenanceSchedule -Name "WS2019 Monthly Patching" -MonitoringObjects (Get-SCOMClass -Name "Microsoft.Windows.Server.2019.Computer" | Get-SCOMClassInstance | Where-Object {$_.DisplayName -like "WEB*"}) -StartTime (Get-Date "2026-06-01 02:00") -DurationInMinutes 180 -ReasonCode PlannedOther -Comment "Monthly patch cycle"