System Requirements for System

Center 2012 Operations Manager

Microsoft Corporation
Published: November 1, 2013

Authors
Byron Ricks

Applies To
System Center 2012 Operations Manager
System Center 2012 Service Pack 1 (SP1) Operations Manager
System Center 2012 R2 Operations Manager

Feedback
Send suggestions and comments about this document to [email protected].
Copyright
This document is provided "as-is". Information and views expressed in this document, including
URL and other Internet website references, may change without notice.
Some examples depicted herein are provided for illustration only and are fictitious. No real
association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any
Microsoft product. You may copy and use this document for your internal, reference purposes.
You may modify this document for your internal, reference purposes.
2013 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Bing, Internet Explorer, JScript, SharePoint, Silverlight, SQL Server,
Visio, Visual Basic, Visual Studio, Win32, Windows, Windows Intune, Windows PowerShell, and
Windows Vista are trademarks of the Microsoft group of companies. Portions of this
documentation related to network monitoring are provided by EMC, and for those portions the
following copyright notice applies 2010 EMC Corporation. All rights reserved. All other
trademarks are property of their respective owners.

Revision History
Release Date Changes

October 17, 2013 Original release of this guide.

November 1, 2013 Minor updates for this guide.

Contents
System Requirements for System Center 2012 - Operations Manager .......................................... 4
System Requirements: System Center 2012 R2 Operations Manager ....................................... 4
System Requirements: System Center 2012 SP1 - Operations Manager ................................. 23
System Requirements: System Center 2012 - Operations Manager ......................................... 41
System Requirements for System Center
2012 - Operations Manager
System Center 2012 Operations Manager, System Center 2012 Service Pack 1 (SP1) -
Operations Manager, and System Center 2012 R2 Operations Manager have requirements for
supported operating systems, hardware configurations, software requirements, installation
combinations, and security configurations. Both versions of Operations Manager have their own
sections covering these supported configurations.

System Requirements
1. System Requirements: System Center 2012 - Operations Manager
2. System Requirements: System Center 2012 SP1 - Operations Manager
3. System Requirements: System Center 2012 R2 Operations Manager

System Requirements: System Center 2012 R2

Operations Manager
This document provides information about the operating systems, hardware configurations,
software requirements, installation combinations, and security configurations for System Center
2012 R2 Operations Manager. This document focuses on the system requirements, and it
mentions unsupported configurations only when necessary. If operating systems, hardware
configurations, software requirements, installation combinations, and security configurations are
not presented here, they have not been tested and are not supported.

Note
For system requirements across all components of System Center, see System
Requirements for System Center 2012 R2.
The Prerequisites checker is no longer a separate option in Setup. However, you can begin the
installation process to check the hardware and software prerequisites, and then cancel
installation after the required prerequisites have been determined.
We recommend that you also review the key concepts of Operations Manager. Documents to
review include the following:
Release Notes for Operations Manager in System Center 2012 R2 identifies any changes
that could affect planning for a new deployment of System Center 2012 R2 Operations
Manager.
Deploying System Center 2012 - Operations Manager provides detailed information about
the security-related features and settings in Operations Manager that can affect your
deployment.
This document contains the following sections:
4
 Operations Manager Virtualization Support
Running Operations Manager on Windows Azure Virtual Machines
Minimum Screen Resolution Requirements
Minimum Hardware Requirements
Minimum Software Requirements
Requirements by Feature
Management Server
Operations Console
Web Console
Operational Database
Microsoft Monitoring Agent Windows-Based Computers
Operations Manager Agent UNIX- or Linux Computers
Operations Manager Reporting
Operations Manager Data Warehouse
Operations Manager Gateway Server
Supported Firewall Scenarios
Minimum Network Connectivity Speeds
Supported Cluster Configurations
Monitored Item Capacity
Operations Manager Feature Firewall Exceptions
Support for Languages in Addition to English
Supported Network Monitoring Scenarios
Application Performance Monitoring Requirements

Operations Manager Virtualization Support

Microsoft supports running all Operations Manager server features in any physical or virtual
environment that meets the minimum requirements that are stated in this document. However, for
performance reasons, we recommend that you store the operational database and data
warehouse database on a directly attached physical hard drive, and not on a virtual disk.
Specifically, virtual computers that are running any Operations Manager server feature must not
use any functionality that does not immediately commit all activity on the virtual computer to the
virtual hard drive. This includes making use of point-in-time snapshots and writing changes to a
temporary virtual hard drive. This is true for every virtualization technology that is used with
Operations Manager.

5
Running Operations Manager on Windows Azure Virtual
Machines
System Center 2012 R2 Operations Manager runs on virtual machines in Windows Azure just as
it does on physical computer systems. We recommend using Operations Manager with Windows
Azure virtual machines in the following scenarios:
Scenario 1: You can run Operations Manager on a Windows Azure virtual machine and use
it to monitor other Windows Azure virtual machines.
Scenario 2: You can run Operations Manager on a Windows Azure virtual machine and use
it to monitor virtual machines that are not running on Windows Azure.
Scenario 3: You can run Operations Manager on-premises and use it to monitor Windows
Azure virtual machines.
Operations Manager was tested by Microsoft by installing and using it in a Windows Azure virtual
machine. The standard sizing and supported configuration for Operations Manager applies to
Windows Azure virtual machines.

Minimum Screen Resolution Requirements

Operations Manager is optimized for screen resolutions of 1280 x 1024 or larger. The minimum
supported screen resolution is 1024 x 768.

Minimum Hardware Requirements

Use the Operations Manager Sizing Helper to determine hardware requirements for each
Operations Manager server feature. If you want to install more than one feature on the same
computer, use the higher of the recommended hardware requirements for any of the combined
features.
Supported Processors, Memory, and Disk Space

Note
Operations Manager does not support installing the 32-bit agent on a 64-bit operating
system. Operations Manager provides native support for x86-based computers for agents
and consoles, and x64-based computers for all server features.

Minimum Software Requirements

Operations Manager server features require a supported operating system. For a list of the
supported operating systems for each server feature, see the Requirements by Feature section
in this document.
Installing System Center 2012 R2 Operations Manager on Windows Server 2012 Core requires
Windows 32-bit on Windows 64-bit (WoW64) support, .NET 4.5, Windows PowerShell 3.0. In
addition, you need AuthManager. To install AuthManager for Windows 2012, add Server-Gui-
Mgmt-Intra (the Minimal Server Interface.) To install for Windows 2012 R2, install AuthManager
with this command: dism /online /enable-feature /featurename:AuthManager. If you attempt to

6
install Operations Manager without WoW64 support installed, the bootstrapper will present an
error message indicating the side-by-side configuration is incorrect.
We recommend that you check for updates and hotfixes for Microsoft SQL Server. Note the
following database considerations for Operations Manager:
SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise
editions. Operations Manager will function with both editions.
Operations Manager does not support hosting its databases or SQL Server Reporting
Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not
supported. The same version should be used for all features.
SQL Server collation settings for all databases must be one of the following:
SQL_Latin1_General_CP1_CI_AS; Latin1_General_100_CI_AS, // EN, IT, DE, PT-BR, NE,
PT-PT; French_CI_AS; French_100_CI_AS; Cyrillic_General_CI_AS; Chinese_PRC_CI_AS;
Chinese_Simplified_Pinyin_100_CI_AS, // CN simplified;
Chinese_Traditional_Stroke_Count_100_CI_AS, // CN traditional, CN-HKJapanese;_CI_AS;
Japanese_XJIS_100_CI_AS; Traditional_Spanish_CI_AS; Modern_Spanish_100_CI_AS; or
Latin1_General_CI_AS; Cyrillic_General_100_CI_AS, // RU; Korean_100_CI_AS;
Czech_100_CI_AS; Hungarian_100_CI_AS; olish_100_CI_AS; and
Finnish_Swedish_100_CI_AS. No other collation settings are supported.
The SQL Server Agent service must be started, and the startup type must be set to
automatic.
The db_owner role for the operational database must be a domain account. If you set the
SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on
the operational database, the Data Access service will not be able to start. For information
about how to resolve the issue, see System Center Data Access Service Start Up Failure
Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 R2 Operations
Manager, you should move the tempdb database to a separate disk that has multiple
spindles. For more information, see tempdb Database.
If you want to install more than one Operations Manager feature on the same computer, you must
install the prerequisite software for all of the combined features.

Requirements by Feature

Management Server
Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012,
Windows Server 2012 Core Installation, or Windows Server 2012 R2.
Processor Architecture: must be x64.
Windows PowerShell version: Windows PowerShell version 2.0, Windows PowerShell
version 3.0, or Windows PowerShell version 4.0.

7
 Windows Remote Management: Windows Remote Management must be enabled for the
management server.
.NET Framework 4 or .NET Framework 4.5 is required. For more information, see .NET
Framework 4 redistributable package

Operations Console
Microsoft Report Viewer 2012 Redistributable Package

Important
Report Viewer also has a dependency on Microsoft System CLR Types for SQL
Server 2012. The SQL Server System CLR Types package contains the components
implementing the geometry, geography, and hierarchy ID types in SQL Server 2012.
This component can be installed separately from the server to allow client
applications to use these types outside of the server. Click the installation instructions
and you see the links that point to other requirements for this component: Windows
Installer 4.5, X86 Package (SQLSysClrTypes.msi),X64 Package
(SQLSysClrTypes.msi), and SQL Server System CLR Types Books on-line page.
Disk space: %SYSTEMDRIVE% requires at least 512 MB free hard disk space.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Server Operating System: must be Windows 7, Windows 8, Windows Server 2008 R2 SP1,
Windows Server 2012, or Windows Server 2012 R2.
Processor Architecture: must be x64 for servers and x64 or x86 for a client computer.
Windows Installer version: at least Windows Installer 3.1.
Windows PowerShell version: Windows PowerShell version 2.0. Windows PowerShell
version 3.0 is required to use Windows PowerShell cmdlets for administration of UNIX and
Linux computers.
.NET Framework 4 is required. For more information, see .NET Framework 4 redistributable
package

Web Console
Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server
2012 R2.
Processor Architecture: must be x64.
Web browsers: Internet Explorer 8, Internet Explorer 9, Internet Explorer 10, Internet Explorer
11, Silverlight 5.0
Internet Information Services (IIS) 7.5 and later versions, with the IIS Management Console
and the following role services installed:
Static Content
Default Document
Directory Browsing
HTTP Errors

8
 HTTP Logging
Request Monitor
Request Filtering
Static Content Compression
Web Server (IIS) Support
IIS 6 Metabase Compatibility
ASP.NET (both the 2.0 and 4.0 versions of ASP.NET are required.)
Windows Authentication
Selected website for web console: requires a configured http or https binding.

Important
Installing the web console on a computer that has Microsoft SharePoint installed is
not supported.
The System Center 2012 R2 Operations Manager SharePoint Dashboard Viewer Web Part
works on SharePoint 2010 and SharePoint 2013 and is supported. However, it does not work
on Office 365 SharePoint and is not supported.
.NET Framework 4 is required for Setup to run. For more information, see the following
documents:
.NET Framework 4 redistributable package

Note
Installation of the web console requires that ISAPI and CGI Restrictions in IIS are
enabled for ASP.NET 4. To enable this, select the web server in IIS Manager, and then
double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click
Allow.

Important
You must install IIS before installing .NET Framework 4. If you installed IIS after installing
.NET Framework 4, you must register ASP.NET 4.0 with IIS. Open a Command prompt
window by using the Run As Administrator option, and then run the following command:
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r

Operational Database
Disk space: The operational database must have at least 1024 MB free disk space. This is
enforced at the time of database creation, and it will likely grow significantly. For information
about SQL Server Planning, see Installing SQL Server 2008 R2 or Install SQL Server 2012.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012
Core Installation or Windows Server 2012 R2.
Processor Architecture: x64.
Windows Installer version: at least Windows Installer 3.1.

9
Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server
2012, SQL Server 2012 SP1.
SQL Server Full Text Search is required.
.NET Framework 4 is required. For more information, see .NET Framework 4 redistributable
package

Microsoft Monitoring Agent Windows-Based Computers

File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating Systems: Windows Server 2003 SP2, Windows Server 2008 SP2, Windows Server
2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2,
Windows XP Professional x64 Edition SP2, Windows XP Professional SP3, Windows Vista
SP2, Windows 7, POSReady, Windows XP Embedded Standard, Windows XP Embedded
Enterprise, Windows XP Embedded POSReady, Windows 7 Professional for Embedded
Systems, Windows 7 Ultimate for Embedded Systems, Windows 8 Pro or Windows 8
Enterprise.
Processor Architectures: x64 or x86.
Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required
for the Operations Manager agent for Windows Server 2003.
Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell
version 3.0.

Note
Windows PowerShell is required for agents that will be monitored by a management
pack that uses Windows PowerShell scripts.

Operations Manager Agent UNIX- or Linux Computers

Supported operating systems:
CentOS 5 and 6 (x86/x64)
Debian GNU/Linux 5, 6, and 7 (x86/x64)
HP-UX 11i v2 and v3 (PA-RISC and IA64)
IBM AIX 5.3, AIX 6.1 (POWER), and AIX 7.1 (POWER)
Novell SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86/x64), and 11 (x86/x64)
Oracle Solaris 9 (SPARC), Solaris 10 (SPARC and x86), and Solaris 11 (SPARC and x86)
Oracle Linux 5 and 6 (x86/x64)
Red Hat Enterprise Linux 4, 5, and 6 (x86/x64)
Ubuntu Linux Server 10.04 and 12.04 (x86/x64)

Operations Manager Reporting

Disk space: The %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.

10
 Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server
2012 Core Installation or Windows Server 2012 R2.
Processor Architecture: x64.
Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL
Server 2012, SQL Server 2012 SP1.
The Remote Registry service must be enabled and started.
Microsoft SQL Server Reporting Services: SQL Server SQL 2008 R2 SP1, SQL Server 2008
R2 SP2, SQL Server 2012, SQL Server 2012 SP1.
System Center 2012 Operations Manager supports SQL Server Reporting Services in
native mode only; do not use SharePoint integrated mode.
.NET Framework 4 is required. For more information, see the following document:
.NET Framework 4 redistributable package

Operations Manager Data Warehouse

Disk space: The data warehouse database must have at least 1024 MB free hard disk space.
This is enforced at the time of database creation, and the required disk space will likely grow
significantly. For information about requirements in SQL Server Planning, see Installing SQL
Server 2008 or Installing SQL Server 2008 R2.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server
2012 Core Installation or Windows Server 2012 R2.
Processor Architecture: x64.
Windows Installer version: at least Windows Installer 3.1.
Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL
Server 2012, SQL Server 2012 SP1.
SQL Server Full Text Search is required.
.NET Framework 4 is required for Setup to run. For more information, see the following
document:
.NET Framework 4 redistributable package

Operations Manager Gateway Server

Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012,
Windows Server 2012 Core Installation or Windows Server 2012 R2.
Processor Architecture: must be x64.
Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell
version 3.0.
Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required
for the management server.
.NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network
devices.
11
Supported Firewall Scenarios
The following table shows Operations Manager feature interaction across a firewall, including
information about the ports that are used for communication between the features, which
direction to open the inbound port, and whether the port number can be changed.
Firewall Scenarios for System Center 2012 R2 Operations Manager

Operations Port number Feature B Configurable Note

Manager Feature A and direction

Management server 1433 ---> Operational Yes (Setup)

database

Management server 1434 UDP < - Operational No If the operational

-- database database is
installed on a
named instance of
SQL Server SQL
2008 R2 SP1,
SQL Server 2008
R2 SP2, SQL
Server 2012, or
SQL Server 2012
SP1 such as in a
cluster, and the
Windows Firewall
is enabled on the
management
server, you have
to also open UDP
1434 inbound on
the management
server.

Management server 1433 ---> Operational Yes (Setup)

database

Management server 5723, 5724 -- Management No Port 5724 must be

-> server open to install this
feature and can be
closed after this
feature has been
installed.

Management server 1433 --> Reporting data No

warehouse

12
Operations Port number Feature B Configurable Note
Manager Feature A and direction

Management server 1433 ---> Reporting data No

warehouse

Reporting server 5723, 5724 -- Management No Port 5724 must be

-> server open to install this
feature and can be
closed after this
feature has been
installed.

Operations console 5724 ---> Management No

server

Connector 51905 ---> Management No

Framework source server

Web console server Selected web Management No

site port ---> server

Web console (for 1433, 1434 -- Operational Yes (Setup)

Application -> database
Diagnostics

Web console (for 1433, 1434 -- Data warehouse Yes (Setup)

Application Advisor) ->

Web console (for 80 ---> SQL Server No

Application Advisor) Reporting
Services

Web console browser 80, 443 ---> web console Yes (IIS Admin) Default for HTTP
server or SSL.
For either Network
Authentication or
Mixed
Authentication, an
account name and
password can be
sent as part of the
request. We
recommend you
use SSL.

13
Operations Port number Feature B Configurable Note
Manager Feature A and direction

Agent installed by 5723 ---> Management Yes (Setup)

using MOMAgent.msi server

Agent installed by 5723 ---> Management Yes (Setup)

using MOMAgent.msi server

Agent installed by 5723 ---> Gateway server Yes (Setup)

using MOMAgent.msi

Gateway server 5723 ---> Management Yes (Setup)

server

Agent (Audit 51909 ---> Management Yes (Registry)

Collection Services server Audit
(ACS) forwarder) Collection
Services (ACS)
Collector

Agentless Exception 51906 ---> Management Yes (Client

Monitoring data from server Agentless Monitoring
client Exception Wizard)
Monitoring (AEM)
file share

Customer Experience 51907 ---> Management Yes (Client

Improvement server (Customer Monitoring
Program data from Experience Wizard)
client Improvement
Program)
Endpoint

Operations console 80 ---> SQL Server No The Operations

(reports) Reporting console uses port
Services 80 to connect to
the SQL Server
Reporting Services
website.

Reporting server 1433 ---> Reporting data Yes

warehouse

Management server 1433 ---> Audit Collection Yes

(Audit Collection Services (ACS)
Services Collector) database

14
Operations Port number Feature B Configurable Note
Manager Feature A and direction

Management Server 161, 162 <--- Network device Yes All firewalls
> between the
management
servers in the
resource pool and
the network
devices need to
allow SNMP
(UDP) and ICMP
bi-directionally,
and ports 161 and
162 need to be
open bi-
directionally. This
includes Windows
Firewall on the
management
server itself.
If your network
devices are using
a port other than
161 and 162, you
need to open bi-
directional UDP
traffic on these
ports as well.

Management server 1270 --- > UNIX or Linux No

or gateway server computer

Management server 22 --- > UNIX or Linux Yes

or gateway server computer

In the preceding table, if SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server
2012, or SQL Server 2012 SP1 is installed by using a default instance, the port number is 1433. If
SQL Server is installed with a named instance, it is probably using a dynamic port. To identify the
port, do the following:
1. Run SQL Server Configuration Manager.
2. Open SQL Server Network Configuration.
3. Open Protocols for INSTANCE1 (or the instance that is running under it).
4. Open TCP/IP.
15
5. Click IP Addresses.
6. The port is under IPAll (usually the TCP Dynamic Ports).

Minimum Network Connectivity Speeds

Operations Manager requires the following minimum network connectivity speeds between the
specified features.

Feature A Feature B Minimum requirement

Management server Agent 64 Kbps

Management server Agentless 1024 Kbps

Management server Database 256 Kbps

Management server Console 768 Kbps

Management server Management server 64 Kbps

Management server Data warehouse database 768 Kbps

Management server Reporting server 256 Kbps

Management server Gateway server 64 Kbps

Local management group Connected management group 1024 Kbps

(tiered)

Web console server web console 128 Kbps

Reporting Data Warehouse Reporting server 1024 Kbps

Console Reporting server 768 Kbps

Audit collector Audit database 768 Kbps

Supported Cluster Configurations

Operations Manager supports the clustering configurations for Operations Manager features as
shown in the following table:

Important
Clustering of management servers is not supported in System Center 2012 R2
Operations Manager.
You can use SQL Server failover clustering or SQL Server 2012 AlwaysOn. For more
information about SQL Server 2012 AlwaysOn, see Using SQL Server 2012 Always On
Availability Groups with System Center 2012 SP1 - Operations Manager.

16
When using SQL Server failover clustering, only Cluster service quorum node clusters are
supported. Multisite clusters (geographically dispersed clusters) are supported for all Operations
Manager cluster roles. You can use replication technology to help provide high availability for
data in Operations Manager, but the latency of communications between components introduce
risks to data replication and might introduce failover issues. We recommend that you use
synchronous mirroring of data disks between sites. Synchronous mirroring means that the data is
fully synchronized across all sites and ensures the correct behavior of applications in the event of
failover across sites.

Important
Microsoft is not obligated to release a hotfix on any Operations Manager issue that
cannot be reproduced in a non-multisite cluster environment. If an analysis determines
that non-Microsoft components in the configuration are causing the issue, the customer
must work with the appropriate vendor for those components.

Server Feature Cluster Notes

Operations Manager Single Active-Passive cluster Other Operations Manager

Operational database features must not be installed
on the cluster or nodes of the
cluster.

Operations Manager Reporting Single Active-Passive cluster Other Operations Manager

data warehouse features must not be installed
on the cluster or nodes of the
cluster.

Audit Collection Services (ACS) Single Active-Passive cluster Other Operations Manager
database features must not be installed
on the cluster or nodes of the
cluster.

Supported, But Not Recommended Cluster Configurations

Operations Manager supports the following clustering configurations for Operations Manager
server roles, as shown in the following table; however, because of a potential performance effect
on your computer running SQL Server, these configurations are not recommended:

Server Feature Cluster Notes

Operations Manager Active-Active cluster where the There might be some

operational database and operational database is performance issues with SQL
Operations Manager installed on one node of the Server in this configuration.
Reporting data warehouse. cluster and the Reporting data
warehouse is installed on the

17
Server Feature Cluster Notes
other node of the cluster.

Operations Manager Single Active-Passive or There might be some

operational database, Active-Active cluster where all performance issues with SQL
Reporting data warehouse, three components are on a Server in this configuration.
and Audit Collection Services single cluster.
(ACS) database.

Operations Manager Single Active-Passive cluster There might be some

operational database and where both components are performance issues with SQL
Audit Collection Services on a single cluster. Server in this configuration.
database.

Operations Manager Single Active-Passive cluster There might be some

operational database and where both components are performance issues with SQL
Reporting data warehouse. on a single cluster. Server in this configuration.

Reporting data warehouse Single Active-Passive cluster There might be some

and Audit Collection Services where both components are performance issues with SQL
database. on a single cluster. Server in this configuration.

Monitored Item Capacity

Operations Manager supports the following number of monitored items.

Monitored item Recommended limit

Simultaneous Operations consoles 50

Agent-monitored computers reporting to a 3,000

management server

Agent-monitored computers reporting to a 2,000

gateway server

Agentless Exception Monitored (AEM)- 25,000

computers per dedicated management server

Agentless Exception Monitored (AEM)- 100,000

computers per management group

Collective client monitored computers per 2,500

management server

Management servers per agent for multihoming 4

Agentless-managed computers per 10

18
Monitored item Recommended limit
management server

Agentless-managed computers per 60

management group

Agent-managed and UNIX or Linux computers 6,000 (with 50 open consoles); 15,000 (with 25
per management group open consoles)

UNIX or Linux computers per dedicated 500

management server

UNIX or Linux computers monitored per 100

dedicated gateway server

Network devices managed by a resource pool 1,000

with three or more management servers

Network devices managed by two resource 2,000

pools

Agents for Application Performance Monitoring 700

(APM)

Applications for Application Performance 400

Monitoring (APM)

URLs monitored per dedicated management 3000

server

URLs monitored per dedicated management 12,000

group

URLs monitored per agent 50

Operations Manager Feature Firewall Exceptions

Feature Exception Port and protocol Configured by

Management server System Center 5723/TCP Setup

Management 5724/TCP Setup
service
51905/TCP Setup
System Center
Data Access 51907/TCP Setup
service 51906/TCP Setup
Operations
Manager

19
Feature Exception Port and protocol Configured by
Connector
Framework
Operations
Manager Customer
Experience
Improvement
Operations
Manager
Application Error
Monitoring

Web console Operations Manager Selected web site Setup

web console port/TCP

Web console, http World Wide Web 80/TCP Windows Firewall

Services, http

Web console, https Secure World Wide 443/TCP Windows Firewall

Web Service, https

Operational database SQL Server 1433/TCP Windows Firewall

database server 1434/UDP Windows Firewall
If using a named
instance, add.

Operations Manager SQL Server 1433/TCP Windows Firewall

data warehouse database server 1434/UDP Windows Firewall
database If using a named
instance, add.

Operations Manager SQL Server Reporting 80/TCP Windows Firewall

Reporting Services

Agent, manual System Center 5723/TCP Windows Firewall

installation of Management service
MOMAgent.msi

Agent, push installation System Center 5723/TCP Windows Firewall

Management 137/UDP, 138/UDP, Windows Firewall
service
139/TCP, 445/TCP Windows Firewall
File and Print
135/TCP, 445/TCP
Sharing
Remote
Administration

Agent, pending repair System Center 5723/TCP Windows Firewall

Management 137/UPD, 138/UPD,
20
Feature Exception Port and protocol Configured by
service 139/TCP, 445/TCP Windows Firewall
File and Print 135/TCP, 445/TCP Windows Firewall
Sharing
Remote
Administration

Agent, pending upgrade System Center 5723/TCP Windows Firewall

Management 137/UDP, 138/UDP, Windows Firewall
service
139/TCP, 445/TCP Windows Firewall
File and Print
135/TCP, 445/TCP
Sharing
Remote
Administration

Gateway System Center 5723/TCP Setup

Management service

Operations Manager SQL Server 1433/TCP Windows Firewall

Audit Collection If using a named 1434/UDP Windows Firewall
Services database instance, add.

Operations Manager ACS Collector Service 51909/TCP Windows Firewall

Audit Collection
Services Collector

Support for Languages in Addition to English

Operations Manager supports the following languages: English, German, French, Japanese,
Spanish, Simplified Chinese, Russian, Italian, and Portuguese (Brazil).
Support for different languages
If your systems run a language other than English, you can install Operations Manager for that
language. You also have the option of installing English Operations Manager for your
management group.
For example, if you use a German version of a Windows operating system on all your servers,
you can install German Operations Manager features for your entire management group. If you
have a German version of a Windows operating system on all your servers, you can optionally
install English Operations Manager features for your entire management group.
Agents for different languages
If you use an English management group, you can monitor any Windows Operating System
Locale type.

21
If you use another language, you can monitor Windows operating systems for English and that
language. For instance, if you use a German management group, you can monitor only English
and German Windows operating systems.
Console for different languages
Operations Manager consoles are language independent. For example, you can use an Italian
Operations Manager console to connect to a German management group.

Supported Network Monitoring Scenarios

Operations Manager supports monitoring of network devices that support Simple Network
Management Protocol (SNMP). Port monitoring is available for devices that have implemented
the interface MIB (RFC 2863) and MIB-II (RFC 1213) standards. In addition, peripheral
monitoring, including processor and memory monitoring, is supported on a subset of devices. For
more information, see System Center Operations Manager 2012: Network Devices with Extended
Monitoring Capability.
Operations Manager can identify connected devices in a recursive discovery that use an IPv6
address; however, the initial device that is discovered must use an IPv4 address.
For more information about supported network devices, see Network Devices Supported for
Discovery by Operations Manager 2012.

Application Performance Monitoring Requirements

To view Application Performance Monitoring event details, you must install the Operations
Manager web console. For more information, see How to Install the Operations Manager Web
Console.
Application Performance Monitoring requires the following software on the agent:
.NET Framework 3.5, .NET Framework 3.5 SP1, .NET Framework 4, or .NET Framework 4.5.

Note
Applicatoin monitoring build on .NET Framework 2.0 is supported, but the computer
must have .NET Framework 3.5 installed for some parts of the agent to work
correctly.
Internet Information Services (IIS) 7.0 or Internet Information Services (IIS) 8.0. Application
monitoring on a Microsoft Failover IIS configuration is not supported. However, application
monitoring using load balancing is supported instead.
ISAPI and CGI Restrictions in IIS be enabled for ASP.NET 4.0. To enable this, select the web
server in IIS Manager, and then double-click ISAPI and CGI Restrictions. Select ASP.NET
v4.0.30319, and then click Allow.
Additionally, you must start the SQL Server Agent service and set the startup type to automatic.
This only refers to the SQL instance where SQL Reporting Services is installed to run report
subscriptions.

22
System Requirements: System Center 2012 SP1 -
Operations Manager
This document provides information about the operating systems, hardware configurations,
software requirements, installation combinations, and security configurations for Operations
Manager in System Center 2012 Service Pack 1 (SP1). This document focuses on the system
requirements, and it mentions unsupported configurations only when necessary. If operating
systems, hardware configurations, software requirements, installation combinations, and security
configurations are not presented here, they have not been tested and are not supported.

Note
For system requirements across all components of System Center 2012 SP1, see
System Requirements for System Center 2012 SP1.
The Prerequisites checker is no longer a separate option in Setup. However, you can begin the
installation process to check the hardware and software prerequisites, and then cancel
installation after the required prerequisites have been determined.
We recommend that you also review the key concepts of Operations Manager. Documents to
review include the following:
Release Notes: System Center 2012 SP1 - Operations Manager identifies any changes
that could affect planning for a new deployment of Operations Manager in System Center
2012 SP1.
Deploying System Center 2012 - Operations Manager provides detailed information about
the security-related features and settings in Operations Manager that can affect your
deployment.
This document contains the following sections:
Operations Manager Virtualization Support
Minimum Screen Resolution Requirements
Minimum Hardware Requirements
Minimum Software Requirements
Requirements by Feature
Management Server
Operations Console
Web Console
Operational Database
Operations Manager Agent Windows-Based Computers
Operations Manager Agent UNIX- or Linux Computers
Operations Manager Reporting
Operations Manager Data Warehouse
Operations Manager Gateway Server
Supported Firewall Scenarios

23
 Minimum Network Connectivity Speeds
Supported Cluster Configurations
Monitored Item Capacity
Operations Manager Feature Firewall Exceptions
Support for Languages in Addition to English
Supported Network Monitoring Scenarios
Application Performance Monitoring Requirements

Operations Manager Virtualization Support

Microsoft supports running all Operations Manager server features in any physical or virtual
environment that meets the minimum requirements that are stated in this document. However, for
performance reasons, we recommend that you store the operational database and data
warehouse database on a directly attached physical hard drive, and not on a virtual disk.
Specifically, virtual computers that are running any Operations Manager server feature must not
use any functionality that does not immediately commit all activity on the virtual computer to the
virtual hard drive. This includes making use of point-in-time snapshots and writing changes to a
temporary virtual hard drive. This is true for every virtualization technology that is used with
Operations Manager.

Minimum Screen Resolution Requirements

Operations Manager is optimized for screen resolutions of 1280 x 1024 or larger. The minimum
supported screen resolution is 1024 x 768.

Minimum Hardware Requirements

Use the Operations Manager Sizing Helper to determine hardware requirements for each
Operations Manager server feature. If you want to install more than one feature on the same
computer, use the higher of the recommended hardware requirements for any of the combined
features.
Supported Processors, Memory, and Disk Space

Note
Operations Manager does not support installing the 32-bit agent on a 64-bit operating
system. Operations Manager provides native support for x86-based computers for agents
and consoles, and x64-based computers for all server features and support for agents on
computers with 64-bit Itanium processors.

Minimum Software Requirements

Operations Manager server features require a supported operating system. For a list of the
supported operating systems for each server feature, see the Requirements by Feature section
in this document.

24
Installing Operations Manager in System Center 2012 SP1 on Windows Server 2012 Core
requires Windows 32-bit on Windows 64-bit (WoW64) support, .NET 4.5,
Windows PowerShell 3.0, and Server-Gui-Mgmt-Infra (the Minimal Server Interface). If you
attempt to install Operations Manager without WoW64 support installed, the bootstrapper will
present an error message indicating the side-by-side configuration is incorrect.

Important
During the initial installation of the operational database, only use Windows
Authentication on the SQL server that hosts the Operations Manager operational
database. Do not use Mixed Mode (Windows Authentication and SQL Server
Authentication) because using SQL Server Authentication mode during the initial
installation of the operational database can cause issues. Although enabling Mixed Mode
security is possible on the SQL Server hosting the Operations Manager operational
database, it is not supported as all contact with the database is accomplished using
Windows accounts only.
We recommend that you check for updates and hotfixes for Microsoft SQL Server. Note the
following database considerations for Operations Manager:
SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise
editions. Operations Manager will function with both editions.
Operations Manager does not support hosting its databases or SQL Server Reporting
Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not
supported. The same version should be used for all features.
SQL Server collation settings for all databases must be one of the following:
SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS,
Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or
Latin1_General_CI_AS. No other collation settings are supported.

The Operations Manager data warehouse installer will always install the data warehouse with
SQL_Latin1_General_CP1_CI_AS regardless of the SQL Server collation. Until this issue is
resolved, always install the Operations Manager data warehouse on a SQL Server with the
SQL_Latin1_General_CP1_CI_AS collation. There are some compatibility issues when the
Temp database on the data warehouse SQL Server instance is anything other than
SQL_Latin1_General_CP1_CI_AS and the data warehouse database is
SQL_Latin1_General_CP1_CI_AS. For more information about SQL Server collation setting
impact and installation requirements in System Center 2012 Service Pack 1 (SP1) between
Operations Manager and Service Manager, see Clarification on SQL Server Collation
Requirements for System Center 2012.

The SQL Server Agent service must be started, and the startup type must be set to
automatic.

25
 Side-by-side installation of System Center Operations Manager 2007 R2 reporting and
Operations Manager in System Center 2012 SP1 reporting on the same server is not
supported.
The db_owner role for the operational database must be a domain account. If you set the
SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on
the operational database, the Data Access service will not be able to start. For information
about how to resolve the issue, see System Center Data Access Service Start Up Failure
Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 Operations
Manager, you should move the tempdb database to a separate disk that has multiple
spindles. For more information, see tempdb Database.
If you want to install more than one Operations Manager feature on the same computer, you must
install the prerequisite software for all of the combined features.

Requirements by Feature

Management Server
Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or
Windows Server 2012 Core Installation.
Processor Architecture: must be x64.
Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell
version 3.0.
Windows Remote Management: Windows Remote Management must be enabled for the
management server.
.NET Framework 4 is required. For more information, see the following document:
.NET Framework 4 redistributable package

Operations Console
Microsoft Report Viewer 2010 SP1 Redistributable Package
Disk space: %SYSTEMDRIVE% requires at least 512 MB free hard disk space.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Server Operating System: must be Windows 7, Windows 8, Windows Server 2008 R2 SP1,
or Windows Server 2012.
Processor Architecture: must be x64 for servers and x64 or x86 for a client computer.
Windows Installer version: at least Windows Installer 3.1.
Windows PowerShell version: Windows PowerShell version 2.0. Windows PowerShell
version 3.0 is required to use Windows PowerShell cmdlets for administration of UNIX and
Linux computers.
.NET Framework 4 is required. For more information, see the following document:
.NET Framework 4 redistributable package
26
Web Console
Operating System: Windows Server 2008 R2 SP1, or Windows Server 2012.
Processor Architecture: must be x64.
Web browsers: Internet Explorer 8, Internet Explorer 9, Internet Explorer 10, Silverlight 5.0
Internet Information Services (IIS) 7.5 and later versions, with the IIS Management Console
and the following role services installed:
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Logging
Request Monitor
Request Filtering
Static Content Compression
Web Server (IIS) Support
IIS 6 Metabase Compatibility
ASP.NET (both the 2.0 and 4.0 versions of ASP.NET are required.)
Windows Authentication
Selected website for web console: requires a configured http or https binding.

Important
Installing the web console on a computer that has Microsoft SharePoint installed is
not supported.
The System Center 2012 Service Pack 1 (SP1) SharePoint Dashboard Viewer Web Part
works on SharePoint 2010 and SharePoint 2013 and is supported. However, it does not work
on Office 365 SharePoint and is not supported.
.NET Framework 4 is required for Setup to run. For more information, see the following
documents:
.NET Framework 4 redistributable package

Note
Installation of the web console requires that ISAPI and CGI Restrictions in IIS are
enabled for ASP.NET 4. To enable this, select the web server in IIS Manager, and then
double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click
Allow.

Important
You must install IIS before installing .NET Framework 4. If you installed IIS after installing
.NET Framework 4, you must register ASP.NET 4.0 with IIS. Open a Command prompt
window by using the Run As Administrator option, and then run the following command:
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r

27
Operational Database
Disk space: The operational database must have at least 1024 MB free disk space. This is
enforced at the time of database creation, and it will likely grow significantly. For information
about SQL Server Planning, see Installing SQL Server 2008 or Installing SQL Server 2008
R2.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server
2012 Core Installation.
Processor Architecture: x64.
Windows Installer version: at least Windows Installer 3.1.
Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server
2012, SQL Server 2012 SP1.
SQL Server Full Text Search is required.
.NET Framework 4 is required. For more information, see the following document:
.NET Framework 4 redistributable package

Operations Manager Agent Windows-Based Computers

File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating Systems: Windows Server 2003 SP2, Windows Server 2008 SP2, Windows Server
2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows XP Professional
x64 Edition SP2, Windows XP Professional SP3, Windows Vista SP2, Windows 7,
POSReady, Windows XP Embedded Standard, Windows XP Embedded Enterprise,
Windows XP Embedded POSReady, Windows 7 Professional for Embedded Systems,
Windows 7 Ultimate for Embedded Systems, Windows 8 Pro or Windows 8 Enterprise.
Processor Architectures: x64, x86, or IA64.
Windows Installer version: at least Windows Installer 3.1.
Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required
for the Operations Manager agent.
Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell
version 3.0.

Note
Windows PowerShell is required for agents that will be monitored by a management
pack that uses Windows PowerShell scripts.

Operations Manager Agent UNIX- or Linux Computers

Supported operating systems:
CentOS 5 and 6 (x86/x64)
Debian GNU/Linux 5, 6, and 7 (x86/x64)
HP-UX 11i v2 and v3 (PA-RISC and IA64)

28
 IBM AIX 5.3, AIX 6.1 (POWER), and AIX 7.1 (POWER)
Novell SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86/x64), and 11 (x86/x64)
Oracle Solaris 9 (SPARC), Solaris 10 (SPARC and x86), and Solaris 11 (SPARC and x86)
Oracle Linux 5 and 6 (x86/x64)
Red Hat Enterprise Linux 4, 5, and 6 (x86/x64)
Ubuntu Linux Server 10.04 and 12.04 (x86/x64)

Operations Manager Reporting

Disk space: The %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows
Server 2012 Core Installation.
Processor Architecture: x64.
Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL
Server 2012, SQL Server 2012 SP1.
The Remote Registry service must be enabled and started.
Microsoft SQL Server Reporting Services: SQL Server SQL 2008 R2 SP1, SQL Server 2008
R2 SP2, SQL Server 2012, SQL Server 2012 SP1.
System Center 2012 Operations Manager supports SQL Server Reporting Services in
native mode only; do not use SharePoint integrated mode.
.NET Framework 4 is required. For more information, see the following document:
.NET Framework 4 redistributable package

Operations Manager Data Warehouse

Disk space: The data warehouse database must have at least 1024 MB free hard disk space.
This is enforced at the time of database creation, and the required disk space will likely grow
significantly. For information about requirements in SQL Server Planning, see Installing SQL
Server 2008 or Installing SQL Server 2008 R2.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows
Server 2012 Core Installation.
Processor Architecture: x64.
Windows Installer version: at least Windows Installer 3.1.
Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL
Server 2012, SQL Server 2012 SP1.
SQL Server Full Text Search is required.
.NET Framework 4 is required for Setup to run. For more information, see the following
document:
.NET Framework 4 redistributable package

29
Operations Manager Gateway Server
Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or
Windows Server 2012 Core Installation.
Processor Architecture: must be x64.
Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell
version 3.0.
Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required
for the management server.
.NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network
devices.

Supported Firewall Scenarios

The following table shows Operations Manager feature interaction across a firewall, including
information about the ports that are used for communication between the features, which
direction to open the inbound port, and whether the port number can be changed.
Firewall Scenarios for Operations Manager in System Center 2012 SP1

Operations Port number Feature B Configurable Note

Manager Feature A and direction

Management server 1433 ---> Operational Yes (Setup)

database

Management server 1434 UDP < - Operational No If the operational

-- database database is
installed on a
named instance of
SQL Server SQL
2008 R2 SP1,
SQL Server 2008
R2 SP2, SQL
Server 2012, or
SQL Server 2012
SP1 such as in a
cluster, and the
Windows Firewall
is enabled on the
management
server, you have
to also open UDP
1434 inbound on
the management
30
Operations Port number Feature B Configurable Note
Manager Feature A and direction
server.

Management server 1433 ---> Operational Yes (Setup)

database

Management server 5723, 5724 -- Management No Port 5724 must be

-> server open to install this
feature and can be
closed after this
feature has been
installed.

Management server 1433 --> Reporting data No

warehouse

Management server 1433 ---> Reporting data No

warehouse

Reporting server 5723, 5724 -- Management No Port 5724 must be

-> server open to install this
feature and can be
closed after this
feature has been
installed.

Operations console 5724 ---> Management No

server

Connector 51905 ---> Management No

Framework source server

Web console server Selected web Management No

site port ---> server

Web console (for 1433, 1434 -- Operational Yes (Setup)

Application -> database
Diagnostics

Web console (for 1433, 1434 -- Data warehouse Yes (Setup)

Application Advisor) ->

Web console (for 80 ---> SQL Server No

Application Advisor) Reporting
Services

Web console browser 80, 443 ---> web console Yes (IIS Admin) Default for HTTP
server or SSL.

31
Operations Port number Feature B Configurable Note
Manager Feature A and direction
For either Network
Authentication or
Mixed
Authentication, an
account name and
password can be
sent as part of the
request. We
recommend you
use SSL.

Agent installed by 5723 ---> Management Yes (Setup)

using MOMAgent.msi server

Agent installed by 5723 ---> Management Yes (Setup)

using MOMAgent.msi server

Agent installed by 5723 ---> Gateway server Yes (Setup)

using MOMAgent.msi

Gateway server 5723 ---> Management Yes (Setup)

server

Agent (Audit 51909 ---> Management Yes (Registry)

Collection Services server Audit
(ACS) forwarder) Collection
Services (ACS)
Collector

Agentless Exception 51906 ---> Management Yes (Client

Monitoring data from server Agentless Monitoring
client Exception Wizard)
Monitoring (AEM)
file share

Customer Experience 51907 ---> Management Yes (Client

Improvement server (Customer Monitoring
Program data from Experience Wizard)
client Improvement
Program)
Endpoint

Operations console 80 ---> SQL Server No The Operations

Reporting console uses port
32
Operations Port number Feature B Configurable Note
Manager Feature A and direction
(reports) Services 80 to connect to
the SQL Server
Reporting Services
website.

Reporting server 1433 ---> Reporting data Yes

warehouse

Management server 1433 ---> Audit Collection Yes

(Audit Collection Services (ACS)
Services Collector) database

Management Server 161, 162 <--- Network device Yes All firewalls
> between the
management
servers in the
resource pool and
the network
devices need to
allow SNMP
(UDP) and ICMP
bi-directionally,
and ports 161 and
162 need to be
open bi-
directionally. This
includes Windows
Firewall on the
management
server itself.
If your network
devices are using
a port other than
161 and 162, you
need to open bi-
directional UDP
traffic on these
ports as well.

Management server 1270 --- > UNIX or Linux No

or gateway server computer

Management server 22 --- > UNIX or Linux Yes

33
Operations Port number Feature B Configurable Note
Manager Feature A and direction
or gateway server computer

In the preceding table, if SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server
2012, or SQL Server 2012 SP1 is installed by using a default instance, the port number is 1433. If
SQL Server is installed with a named instance, it is probably using a dynamic port. To identify the
port, do the following:
1. Run SQL Server Configuration Manager.
2. Open SQL Server Network Configuration.
3. Open Protocols for INSTANCE1 (or the instance that is running under it).
4. Open TCP/IP.
5. Click IP Addresses.
6. The port is under IPAll (usually the TCP Dynamic Ports).

Minimum Network Connectivity Speeds

Operations Manager requires the following minimum network connectivity speeds between the
specified features.

Feature A Feature B Minimum requirement

Management server Agent 64 Kbps

Management server Agentless 1024 Kbps

Management server Database 256 Kbps

Management server Console 768 Kbps

Management server Management server 64 Kbps

Management server Data warehouse database 768 Kbps

Management server Reporting server 256 Kbps

Management server Gateway server 64 Kbps

Local management group Connected management group 1024 Kbps

(tiered)

Web console server web console 128 Kbps

Reporting Data Warehouse Reporting server 1024 Kbps

Console Reporting server 768 Kbps

Audit collector Audit database 768 Kbps

34
Supported Cluster Configurations
Operations Manager supports the clustering configurations for Operations Manager features as
shown in the following table:

Important
Clustering of management servers is not supported in System Center 2012 Service Pack
1 (SP1), Operations Manager.
Only Cluster service quorum node clusters are supported. Multisite clusters (geographically
dispersed clusters) are supported for all Operations Manager cluster roles. You can use
replication technology to help provide high availability for data in Operations Manager, but the
latency of communications between components introduce risks to data replication and might
introduce failover issues. We recommend that you use synchronous mirroring of data disks
between sites. Synchronous mirroring means that the data is fully synchronized across all sites
and ensures the correct behavior of applications in the event of failover across sites.

Important
Microsoft is not obligated to release a hotfix on any Operations Manager issue that
cannot be reproduced in a non-multisite cluster environment. If an analysis determines
that non-Microsoft components in the configuration are causing the issue, the customer
must work with the appropriate vendor for those components.

Server Feature Cluster Notes

Operations Manager Single Active-Passive cluster Other Operations Manager

Operational database features must not be installed
on the cluster or nodes of the
cluster.

Operations Manager Reporting Single Active-Passive cluster Other Operations Manager

data warehouse features must not be installed
on the cluster or nodes of the
cluster.

Audit Collection Services (ACS) Single Active-Passive cluster Other Operations Manager
database features must not be installed
on the cluster or nodes of the
cluster.

Supported, But Not Recommended Cluster Configurations

Operations Manager supports the following clustering configurations for Operations Manager
server roles, as shown in the following table; however, because of a potential performance effect
on your computer running SQL Server, these configurations are not recommended:

35
Server Feature Cluster Notes

Operations Manager Active-Active cluster where the There might be some

operational database and operational database is performance issues with SQL
Operations Manager installed on one node of the Server in this configuration.
Reporting data warehouse. cluster and the Reporting data
warehouse is installed on the
other node of the cluster.

Operations Manager Single Active-Passive or There might be some

operational database, Active-Active cluster where all performance issues with SQL
Reporting data warehouse, three components are on a Server in this configuration.
and Audit Collection Services single cluster.
(ACS) database.

Operations Manager Single Active-Passive cluster There might be some

operational database and where both components are performance issues with SQL
Audit Collection Services on a single cluster. Server in this configuration.
database.

Operations Manager Single Active-Passive cluster There might be some

operational database and where both components are performance issues with SQL
Reporting data warehouse. on a single cluster. Server in this configuration.

Reporting data warehouse Single Active-Passive cluster There might be some

and Audit Collection Services where both components are performance issues with SQL
database. on a single cluster. Server in this configuration.

Monitored Item Capacity

Operations Manager supports the following number of monitored items.

Monitored item Recommended limit

Simultaneous Operations consoles 50

Agent-monitored computers reporting to a 3,000

management server

Agent-monitored computers reporting to a 2,000

gateway server

Agentless Exception Monitored (AEM)- 25,000

computers per dedicated management server

Agentless Exception Monitored (AEM)- 100,000

computers per management group

36
Monitored item Recommended limit

Collective client monitored computers per 2,500

management server

Management servers per agent for multihoming 4

Agentless-managed computers per 10

management server

Agentless-managed computers per 60

management group

Agent-managed and UNIX or Linux computers 6,000 (with 50 open consoles); 15,000 (with 25
per management group open consoles)

UNIX or Linux computers per dedicated 500

management server

UNIX or Linux computers monitored per 100

dedicated gateway server

Network devices managed by a resource pool 1,000

with three or more management servers

Network devices managed by two resource 2,000

pools

Agents for Application Performance Monitoring 700

(APM)

Applications for Application Performance 400

Monitoring (APM)

URLs monitored per dedicated management 3000

server

URLs monitored per dedicated management 12,000

group

URLs monitored per agent 50

Operations Manager Feature Firewall Exceptions

Feature Exception Port and protocol Configured by

Management server System Center 5723/TCP Setup

Management 5724/TCP Setup
service

37
Feature Exception Port and protocol Configured by
System Center 51905/TCP Setup
Data Access 51907/TCP Setup
service
51906/TCP Setup
Operations
Manager
Connector
Framework
Operations
Manager Customer
Experience
Improvement
Operations
Manager
Application Error
Monitoring

Web console Operations Manager Selected web site Setup

web console port/TCP

Web console, http World Wide Web 80/TCP Windows Firewall

Services, http

Web console, https Secure World Wide 443/TCP Windows Firewall

Web Service, https

Operational database SQL Server 1433/TCP Windows Firewall

database server 1434/UDP Windows Firewall
If using a named
instance, add.

Operations Manager SQL Server 1433/TCP Windows Firewall

data warehouse database server 1434/UDP Windows Firewall
database If using a named
instance, add.

Operations Manager SQL Server Reporting 80/TCP Windows Firewall

Reporting Services

Agent, manual System Center 5723/TCP Windows Firewall

installation of Management service
MOMAgent.msi

Agent, push installation System Center 5723/TCP Windows Firewall

Management 137/UDP, 138/UDP, Windows Firewall
service
139/TCP, 445/TCP Windows Firewall
File and Print
135/TCP, 445/TCP

38
Feature Exception Port and protocol Configured by
Sharing
Remote
Administration

Agent, pending repair System Center 5723/TCP Windows Firewall

Management 137/UPD, 138/UPD, Windows Firewall
service
139/TCP, 445/TCP Windows Firewall
File and Print
135/TCP, 445/TCP
Sharing
Remote
Administration

Agent, pending upgrade System Center 5723/TCP Windows Firewall

Management 137/UDP, 138/UDP, Windows Firewall
service
139/TCP, 445/TCP Windows Firewall
File and Print
135/TCP, 445/TCP
Sharing
Remote
Administration

Gateway System Center 5723/TCP Setup

Management service

Operations Manager SQL Server 1433/TCP Windows Firewall

Audit Collection If using a named 1434/UDP Windows Firewall
Services database instance, add.

Operations Manager ACS Collector Service 51909/TCP Windows Firewall

Audit Collection
Services Collector

Support for Languages in Addition to English

Operations Manager supports the following languages: English, Chinese-Hong Kong, Chinese-
Traditional, Czech, Dutch, German, French, Hungarian, Italian, Japanese, Korean, Polish,
Portuguese (Brazil), Portuguese (Portugal), Russian, Simplified Chinese, Spanish, Swedish, and
Turkish.
Support for different languages
If your systems run a language other than English, you can install Operations Manager for that
language. You also have the option of installing English Operations Manager for your
management group.
For example, if you use a German version of a Windows operating system on all your servers,
you can install German Operations Manager features for your entire management group. If you

39
have a German version of a Windows operating system on all your servers, you can optionally
install English Operations Manager features for your entire management group.
Agents for different languages
If you use an English management group, you can monitor any Windows Operating System
Locale type.
If you use another language, you can monitor Windows operating systems for English and that
language. For instance, if you use a German management group, you can monitor only English
and German Windows operating systems.
Console for different languages
Operations Manager consoles are language independent. For example, you can use an Italian
Operations Manager console to connect to a German management group.

Supported Network Monitoring Scenarios

Operations Manager supports monitoring of network devices that support Simple Network
Management Protocol (SNMP). Port monitoring is available for devices that have implemented
the interface MIB (RFC 2863) and MIB-II (RFC 1213) standards. In addition, peripheral
monitoring, including processor and memory monitoring, is supported on a subset of devices. For
more information, see System Center Operations Manager 2012: Network Devices with Extended
Monitoring Capability.
Operations Manager can identify connected devices in a recursive discovery that use an IPv6
address; however, the initial device that is discovered must use an IPv4 address.
For more information about supported network devices, see Network Devices Supported for
Discovery by Operations Manager 2012.

Application Performance Monitoring Requirements

To view Application Performance Monitoring event details, you must install the Operations
Manager web console. For more information, see How to Install the Operations Manager Web
Console.
Application Performance Monitoring requires the following software:
.NET Framework 2.0, .NET Framework 3.5, .NET Framework 3.5 SP1, .NET Framework 4, or
.NET Framework 4.5.
Internet Information Services (IIS) 7.0. Application monitoring on a clustered IIS configuration
is not supported.
ISAPI and CGI Restrictions in IIS be enabled for ASP.NET 4.0. To enable this, select the web
server in IIS Manager, and then double-click ISAPI and CGI Restrictions. Select ASP.NET
v4.0.30319, and then click Allow.
Additionally, you must start the SQL Server Agent service and set the startup type to automatic.

40
System Requirements: System Center 2012 -
Operations Manager
This document provides information about the operating systems, hardware configurations,
software requirements, installation combinations, and security configurations for System
Center 2012 Operations Manager. This document focuses on the system requirements and
only mentions unsupported configurations when necessary. If operating systems, hardware
configurations, software requirements, installation combinations, and security configurations are
not presented here, they have not been tested and are not supported.
The Prerequisites checker is no longer a separate option in Setup. However, you can begin the
installation process to check the hardware and software prerequisites, and then cancel
installation after the required prerequisites have been determined.
We recommend that you also review the key concepts of Operations Manager. Areas to review
include the following documents:
Release Notes for System Center 2012 - Operations Manager identify any changes that
could affect planning for a new deployment of System Center 2012 Operations Manager.
TheSystem Center 2012 - Operations Manager Deployment Guide provides detailed
information about the security-related features and settings in Operations Manager that can
affect your deployment.
This document contains the following sections:
Operations Manager Virtualization Support
Minimum Screen Resolution Requirements
Minimum Hardware Requirements
Minimum Software Requirements
Requirements by Feature
Management Server
Operations Console
Web Console
Operational Database
Operations Manager Agent Windows-Based Computers
Operations Manager Agent UNIX- or Linux Computers
Operations Manager Reporting
Operations Manager Data Warehouse
Operations Manager Gateway Server
Supported Firewall Scenarios
Minimum Network Connectivity Speeds
Supported Cluster Configurations
Monitored Item Capacity
Operations Manager Feature Firewall Exceptions
Support for Languages in Addition to English
41
 Supported Network Monitoring Scenarios
Application Performance Monitoring Requirements

Operations Manager Virtualization Support

Microsoft supports running all System Center 2012 Operations Manager server features in any
physical or virtual environment that meets the minimum requirements that are stated in this
document. However, for performance reasons, we recommend that you store the operational
database and data warehouse database on a directly attached physical hard drive, and not on a
virtual disk. Specifically, virtual computers that are running any Operations Manager server
feature must not use any functionality that does not immediately commit all activity on the virtual
computer to the virtual hard drive. This includes making use of point-in-time snapshots and
writing changes to a temporary virtual hard drive. This is true for every virtualization technology
that is used with Operations Manager.

Minimum Screen Resolution Requirements

Operations Manager is optimized for screen resolutions of 1280 x 1024 or larger. The minimum
supported screen resolution is 1024 x 768.

Minimum Hardware Requirements

Use the Operations Manager Sizing Helper to determine hardware requirements for each System
Center 2012 Operations Manager server feature. If you want to install more than one feature on
the same computer, use the higher of the recommended hardware requirements for any of the
combined features.
Supported Processors, Memory, and Disk Space

Note
Operations Manager does not support installing the 32-bit agent on a 64-bit operating
system. Operations Manager provides native support for x86-based computers for agents
and consoles, and x64-based computers for all server features and support for agents on
computers with 64-bit Itanium processors.

Minimum Software Requirements

Operations Manager server features require a supported operating system. For a list of the
supported operating systems for each server feature, see the Requirements by Feature section
in this document.

Important
During the initial installation of the operational database, only use Windows
Authentication on the SQL server that hosts the Operations Manager operational
database. Do not use Mixed Mode (Windows Authentication and SQL Server
Authentication) because using SQL Server Authentication mode during the initial

42
 installation of the operational database can cause issues. Although enabling Mixed Mode
security is possible on the SQL Server hosting the Operations Manager operational
database, it is not supported as all contact with the database is accomplished using
Windows accounts only.
We recommend that you check for updates and hotfixes for SQL Server. Note the following
database considerations for Operations Manager:
SQL Server 2008 is available in both Standard and Enterprise editions. Operations Manager
will function with both editions.
Operations Manager does not support hosting its databases or SQL Server Reporting
Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not
supported. The same version should be used for all features.
SQL Server collation settings for all databases must be one of the following:
SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS,
Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or
Latin1_General_CI_AS. No other collation settings are supported.
The SQL Server Agent service must be started, and the startup type must be set to
automatic.
Side-by-side installation of System Center Operations Manager 2007 R2 Reporting and
System Center 2012 Operations Manager Reporting on the same server is not supported.
The db_owner role for the operational database must be a domain account. If you set the
SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on
the operational database, the Data Access service will not be able to start. For information
about how to resolve the issue, see System Center Data Access Service Start Up Failure
Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 Operations
Manager, you should move the tempdb database to a separate disk that has multiple
spindles. For more information, see tempdb Database.
If you want to install more than one Operations Manager feature on the same computer, you must
install the prerequisite software for all of the combined features.

Requirements by Feature

Management Server
Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Server Operating System: must be Windows Server 2008 R2 SP1.
Processor Architecture: must be x64.
Windows PowerShell version: Windows PowerShell version 2.0.
Windows Remote Management: Windows Remote Management must be enabled for the
management server.

43
 Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required
for the management server.
Both .NET Framework 3.5 Service Pack 1 (SP1) and .NET Framework 4 are required. For
more information, see the following documents:
.NET Framework 3.5 SP1 redistributable package
.NET Framework 4 redistributable package

Operations Console
Microsoft Report Viewer 2010 Redistributable Package
Microsoft .NET Framework 3.5 SP1 hotfix
Disk space: %SYSTEMDRIVE% requires at least 512 MB free hard disk space.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Server Operating System: must be Windows Vista, Windows 7, Windows Server 2008,
Windows Server 2008 R2, or Windows Server 2008 R2 SP1.
Processor Architecture: must be x64 for servers and x64 or x86 for a client computer.
Windows Installer version: at least Windows Installer 3.1.
Windows PowerShell version: Windows PowerShell version 2.0. Windows PowerShell
version 3.0 is required to use Windows PowerShell cmdlets for administration of UNIX and
Linux computers.
Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information,
see the following documents:
.NET Framework 3.5 SP1 redistributable package
.NET Framework 4 redistributable package

Web Console
Operating System: Windows Server 2008 R2 SP1.
Processor Architecture: must be x64.
Web browsers: Internet Explorer 7, Internet Explorer 8, Internet Explorer 9
Internet Information Services (IIS) 7.5 and later versions, with the IIS Management Console
and the following role services installed:
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Logging
Request Monitor
Request Filtering
Static Content Compression
Web Server (IIS) Support

44
 IIS 6 Metabase Compatibility
ASP.NET
Windows Authentication
Selected website for web console: requires a configured http or https binding.

Warning
Installing the web console on a computer that has SharePoint installed is not
supported.
Both .NET Framework 3.5 SP1 and .NET Framework 4 are required for Setup to run. For
more information, see the following documents:
.NET Framework 3.5 SP1 redistributable package
.NET Framework 4 redistributable package

Note
Installation of the web console requires that ISAPI and CGI Restrictions in IIS are
enabled for ASP.NET 4. To enable this, select the web server in IIS Manager, and then
double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click
Allow.

Important
You must install IIS before installing .NET Framework 4. If you installed IIS after installing
.NET Framework 4, you must register ASP.NET 4.0 with IIS. Open a Command prompt
window by using the Run As Administrator option, and then run the following command:
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r

Operational Database
Disk space: The operational database must have at least 1024 MB free disk space. This is
enforced at the time of database creation, and it will likely grow significantly. For information
about SQL Server Planning, see Installing SQL Server 2008 or Installing SQL Server 2008
R2.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating System: Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.
Processor Architecture: x64.
Windows Installer version: at least Windows Installer 3.1.
Microsoft SQL Server: SQL Server 2008 SP1, SQL Server 2008 SP2, SQL Server 2008 SP3,
SQL Server 2008 R2, SQL Server 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server
2012, or SQL Server 2012 SP1.
SQL Server Full Text Search is required.
Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information, see
the following documents:
.NET Framework 3.5 SP1 redistributable package

45
 .NET Framework 4 redistributable package

Operations Manager Agent Windows-Based Computers

File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating Systems: Windows Server 2003 SP2, Windows Server 2008 SP2, Windows Server
2008 R2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows XP Professional
x64 Edition SP2, Windows XP Professional SP3, or Windows Vista SP2, or Windows 7,
POSReady, Windows XP Embedded Standard, orWindows XP Embedded Enterprise, or
Windows XP Embedded POSReady, Windows 7 Professional for Embedded Systems,
orWindows 7 Ultimate for Embedded Systems.
Processor Architectures: x64, x86, or IA64.
Windows Installer version: at least Windows Installer 3.1.
Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required
for the Operations Manager agent.
Windows PowerShell version: Windows PowerShell version 2.0.

Note
Windows PowerShell is required for agents that will be monitored by a management
pack that uses PowerShell scripts.

Operations Manager Agent UNIX- or Linux Computers

Supported operating systems:
HP-UX 11i v2 and v3 (PA-RISC and IA64)
Oracle Solaris 9 (SPARC), Solaris 10 (SPARC and x86), and Solaris 11 (SPARC and x86)
Red Hat Enterprise Linux 4, 5, and 6 (x86/x64)
Novell SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86/x64), and 11 (x86/x64)
IBM AIX 5.3, AIX 6.1 (POWER), and AIX 7.1 (POWER)

Operations Manager Reporting

Disk space: The %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Operating System: Windows Server 2008 R2 SP1.
Processor Architecture: x64.
Microsoft SQL Server: SQL Server 2008 SP1, SQL Server 2008 SP2, SQL Server 2008 SP3,
SQL Server 2008 R2, SQL Server 2008 R2 SP1, or SQL Server 2008 R2 SP2.
The Remote Registry service must be enabled and started.
Microsoft SQL Server Reporting Services: Microsoft SQL Server: SQL Server 2008 SP1,
SQL Server 2008 SP2, SQL Server 2008 SP3, SQL Server 2008 R2, SQL Server 2008 R2
SP1, or SQL Server 2008 R2 SP2.
System Center 2012 Operations Manager supports SQL Server Reporting Services in
native mode only; do not use SharePoint integrated mode.

46
 Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information,
see the following documents:
.NET Framework 3.5 SP1 redistributable package
.NET Framework 4 redistributable package

Operations Manager Data Warehouse

Disk space: The data warehouse database must have at least 1024 MB free hard disk space.
This is enforced at the time of database creation, and the required disk space will likely grow
significantly. For information about requirements in SQL Server Planning, see Installing SQL
Server 2008 or Installing SQL Server 2008 R2.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating System: Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.
Processor Architecture: x64.
Windows Installer version: at least Windows Installer 3.1.
Microsoft SQL Server: Microsoft SQL Server: SQL Server 2008 SP1, SQL Server 2008 SP2,
SQL Server 2008 SP3, SQL Server 2008 R2, SQL Server 2008 R2 SP1, SQL Server 2008
R2 SP2, SQL Server 2012, or SQL Server 2012 SP1.
SQL Server Full Text Search is required.
Both .NET Framework 3.5 SP1 and .NET Framework 4 are required for Setup to run. For
more information, see the following documents:
.NET Framework 3.5 SP1 redistributable package
.NET Framework 4 redistributable package

Operations Manager Gateway Server

Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Server Operating System: must be Windows Server 2008 R2 SP1.
Processor Architecture: must be x64.
Windows PowerShell version: Windows PowerShell version 2.0.
Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required
for the management server.
.NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network
devices.

Supported Firewall Scenarios

The following table shows Operations Manager feature interaction across a firewall, including
information about the ports used for communication between the features, which direction to open
the inbound port, and whether the port number can be changed.
Operations Manager 2012 Firewall Scenarios

47
Operations Port number Feature B Configurable Note
Manager Feature A and direction

Management server 1433 ---> Operational Yes (Setup)

database

Management server 1434 UDP < - Operational No If the operational

-- database database is
installed on a
named instance of
SQL Server 2008
SP1, SQL Server
2008 SP2, SQL
Server 2008 SP3,
SQL Server 2008
R2, SQL Server
2008 R2 SP1, or
SQL Server 2008
R2 SP2 such as in
a cluster, and the
Windows Firewall
is enabled on the
management
server, you have
to also open UDP
1434 inbound on
the management
server.

Management server 1433 ---> Operational Yes (Setup)

database

Management server 5723, 5724 -- Management No Port 5724 must be

-> server open to install this
feature and can be
closed after this
feature has been
installed.

Management server 1433 --> Reporting data No

warehouse

Management server 1433 ---> Reporting data No

warehouse

Reporting server 5723, 5724 -- Management No Port 5724 must be

48
Operations Port number Feature B Configurable Note
Manager Feature A and direction
-> server open to install this
feature and can be
closed after this
feature has been
installed.

Operations console 5724 ---> Management No

server

Connector 51905 ---> Management No

Framework source server

Web console server Selected web Management No

site port ---> server

Web console (for 1433, 1434 -- Operational Yes (Setup)

Application -> database
Diagnostics

Web console (for 1433, 1434 -- Data warehouse Yes (Setup)

Application Advisor) ->

Web console (for 80 ---> SQL Server No

Application Advisor) Reporting
Services

Web console browser 80, 443 ---> web console Yes (IIS Admin) Default for HTTP
server or SSL.
For either Network
Authentication or
Mixed
Authentication, an
account name and
password can be
sent as part of the
request. We
recommend you
use SSL.

Agent installed by 5723 ---> Management Yes (Setup)

using MOMAgent.msi server

Agent installed by 5723 ---> Management Yes (Setup)

using MOMAgent.msi server

49
Operations Port number Feature B Configurable Note
Manager Feature A and direction

Agent installed by 5723 ---> Gateway server Yes (Setup)

using MOMAgent.msi

Gateway server 5723 ---> Management Yes (Setup)

server

Agent (Audit 51909 ---> Management Yes (Registry)

Collection Services server Audit
(ACS) forwarder) Collection
Services (ACS)
Collector

Agentless Exception 51906 ---> Management Yes (Client

Monitoring data from server Agentless Monitoring
client Exception Wizard)
Monitoring (AEM)
file share

Customer Experience 51907 ---> Management Yes (Client

Improvement server (Customer Monitoring
Program data from Experience Wizard)
client Improvement
Program)
Endpoint

Operations console 80 ---> SQL Server No The Operations

(reports) Reporting console uses port
Services 80 to connect to
the SQL Server
Reporting Services
website.

Reporting server 1433 ---> Reporting data Yes

warehouse

Management server 1433 ---> Audit Collection Yes

(Audit Collection Services (ACS)
Services Collector) database

Management Server 161, 162 <--- Network device Yes All firewalls
> between the
management
servers in the
resource pool and
the network
50
Operations Port number Feature B Configurable Note
Manager Feature A and direction
devices need to
allow SNMP
(UDP) and ICMP
bi-directionally,
and ports 161 and
162 need to be
open bi-
directionally. This
includes Windows
Firewall on the
management
server itself.
If your network
devices are using
a port other than
161 and 162, you
need to open bi-
directional UDP
traffic on these
ports as well.

Management server 1270 --- > UNIX or Linux No

or gateway server computer

Management server 22 --- > UNIX or Linux Yes

or gateway server computer

In the preceding table, if SQL Server 2008 SP1, SQL Server 2008 SP2, SQL Server 2008 SP3,
SQL Server 2008 R2, SQL Server 2008 R2 SP1, or SQL Server 2008 R2 SP2 is installed by
using a default instance, the port number is 1433. If SQL Server is installed with a named
instance, it is probably using a dynamic port. To identify the port, do the following:
1. Run SQL Server Configuration Manager.
2. Open SQL Server Network Configuration.
3. Open Protocols for INSTANCE1 (or the instance that is running under it).
4. Open TCP/IP.
5. Click IP Addresses.
6. The port is under IPAll (usually the TCP Dynamic Ports).

51
Minimum Network Connectivity Speeds
Operations Manager requires the following minimum network connectivity speeds between the
specified features.

Feature A Feature B Minimum requirement

Management server Agent 64 Kbps

Management server Agentless 1024 Kbps

Management server Database 256 Kbps

Management server Console 768 Kbps

Management server Management server 64 Kbps

Management server Data warehouse database 768 Kbps

Management server Reporting server 256 Kbps

Management server Gateway server 64 Kbps

Local management group Connected management group 1024 Kbps

(tiered)

Web console server web console 128 Kbps

Reporting Data Warehouse Reporting server 1024 Kbps

Console Reporting server 768 Kbps

Audit collector Audit database 768 Kbps

Supported Cluster Configurations

Operations Manager supports the clustering configurations for Operations Manager features as
shown in the following table:

Warning
Clustering of management servers is not supported in System Center 2012 Operations
Manager.
Only Cluster service quorum node clusters are supported. Multisite clusters (geographically
dispersed clusters) are supported for all Operations Manager cluster roles. You can use
replication technology to help provide high availability for data in Operations Manager, but the
latency of communications between components introduce risks to data replication and might
introduce failover issues. We recommend that you use synchronous mirroring of data disks
between sites. Synchronous mirroring means that the data is fully synchronized across all sites
and ensures the correct behavior of applications in the event of failover across sites.

52
 Important
Microsoft is not obligated to release a hotfix on any Operations Manager issue that
cannot be reproduced in a non-multisite cluster environment. If an analysis determines
that non-Microsoft components in the configuration are causing the issue, the customer
must work with the appropriate vendor for those components.

Server Feature Cluster Notes

Operations Manager Single Active-Passive cluster Other Operations Manager

Operational database features must not be installed
on the cluster or nodes of the
cluster.

Operations Manager Reporting Single Active-Passive cluster Other Operations Manager

data warehouse features must not be installed
on the cluster or nodes of the
cluster.

Audit Collection Services (ACS) Single Active-Passive cluster Other Operations Manager
database features must not be installed
on the cluster or nodes of the
cluster.

Supported, But Not Recommended Cluster Configurations

Operations Manager supports the following clustering configurations for Operations Manager
server roles, as shown in the following table; however, because of a potential performance effect
on your computer running SQL Server, these configurations are not recommended:

Server Feature Cluster Notes

Operations Manager Active-Active cluster where the There might be some

operational database and operational database is performance issues with SQL
Operations Manager installed on one node of the Server in this configuration.
Reporting data warehouse. cluster and the Reporting data
warehouse is installed on the
other node of the cluster.

Operations Manager Single Active-Passive or There might be some

operational database, Active-Active cluster where all performance issues with SQL
Reporting data warehouse, three components are on a Server in this configuration.
and Audit Collection Services single cluster.
(ACS) database.

Operations Manager Single Active-Passive cluster There might be some

53
Server Feature Cluster Notes
operational database and where both components are performance issues with SQL
Audit Collection Services on a single cluster. Server in this configuration.
database.

Operations Manager Single Active-Passive cluster There might be some

operational database and where both components are performance issues with SQL
Reporting data warehouse. on a single cluster. Server in this configuration.

Reporting data warehouse Single Active-Passive cluster There might be some

and Audit Collection Services where both components are performance issues with SQL
database. on a single cluster. Server in this configuration.

Monitored Item Capacity

Operations Manager supports the following number of monitored items.

Monitored item Recommended limit

Simultaneous Operations consoles 50

Agent-monitored computers reporting to a 3,000

management server

Agent-monitored computers reporting to a 2,000

gateway server

Agentless Exception Monitored (AEM)- 25,000

computers per dedicated management server

Agentless Exception Monitored (AEM)- 100,000

computers per management group

Collective client monitored computers per 2,500

management server

Management servers per agent for multihoming 4

Agentless-managed computers per 10

management server

Agentless-managed computers per 60

management group

Agent-managed and UNIX or Linux computers 6,000 (with 50 open consoles); 15,000 (with 25
per management group open consoles)

UNIX or Linux computers per dedicated 500

54
Monitored item Recommended limit
management server

UNIX or Linux computers monitored per 100

dedicated gateway server

Network devices managed by a resource pool 1,000

with three or more management servers

Network devices managed by two resource 2,000

pools

Agents for Application Performance Monitoring 700

(APM)

Applications for Application Performance 400

Monitoring (APM)

URLs monitored per dedicated management 3000

server

URLs monitored per dedicated management 12,000

group

URLs monitored per agent 50

Operations Manager Feature Firewall Exceptions

Feature Exception Port and protocol Configured by

Management server System Center 5723/TCP Setup

Management 5724/TCP Setup
service
51905/TCP Setup
System Center
Data Access 51907/TCP Setup
service 51906/TCP Setup
Operations
Manager
Connector
Framework
Operations
Manager Customer
Experience
Improvement
Operations
Manager

55
Feature Exception Port and protocol Configured by
Application Error
Monitoring

Web console Operations Manager Selected web site Setup

web console port/TCP

Web console, http World Wide Web 80/TCP Windows Firewall

Services, http

Web console, https Secure World Wide 443/TCP Windows Firewall

Web Service, https

Operational database SQL Server 1433/TCP Windows Firewall

database server 1434/UDP Windows Firewall
If using a named
instance, add.

Operations Manager SQL Server 1433/TCP Windows Firewall

data warehouse database server 1434/UDP Windows Firewall
database If using a named
instance, add.

Operations Manager SQL Server Reporting 80/TCP Windows Firewall

Reporting Services

Agent, manual System Center 5723/TCP Windows Firewall

installation of Management service
MOMAgent.msi

Agent, push installation System Center 5723/TCP Windows Firewall

Management 137/UDP, 138/UDP, Windows Firewall
service
139/TCP, 445/TCP Windows Firewall
File and Print
135/TCP, 445/TCP
Sharing
Remote
Administration

Agent, pending repair System Center 5723/TCP Windows Firewall

Management 137/UPD, 138/UPD, Windows Firewall
service
139/TCP, 445/TCP Windows Firewall
File and Print
135/TCP, 445/TCP
Sharing
Remote
Administration

Agent, pending upgrade System Center 5723/TCP Windows Firewall

Management 137/UDP, 138/UDP, Windows Firewall

56
Feature Exception Port and protocol Configured by
service 139/TCP, 445/TCP Windows Firewall
File and Print 135/TCP, 445/TCP
Sharing
Remote
Administration

Gateway System Center 5723/TCP Setup

Management service

Operations Manager SQL Server 1433/TCP Windows Firewall

Audit Collection If using a named 1434/UDP Windows Firewall
Services database instance, add.

Operations Manager ACS Collector Service 51909/TCP Windows Firewall

Audit Collection
Services Collector

Support for Languages in Addition to English

Operations Manager supports the following languages: English, German, French, Japanese,
Spanish, Simplified Chinese, Russian, Italian, and Portuguese (Brazil).
Support for different languages
If your systems run a language other than English, you can install Operations Manager for that
language. You also have the option of installing English Operations Manager for your
management group.
For example, if you use a German version of a Windows operating system on all your servers,
you can install German Operations Manager features for your entire management group, or you
can optionally install English Operations Manager features for your entire management group.
Agents for different languages
If you use an English management group, you can monitor any Windows Operating System
Locale type.
If you use another language, you can monitor Windows operating systems for English and that
language. For instance, if you use a German management group, you can monitor only English
and German Windows operating systems.
Console for different languages
Operations Manager consoles are language independent. For example, you can use an Italian
Operations Manager console to connect to a German management group.

57
Supported Network Monitoring Scenarios
Operations Manager supports monitoring of network devices that support Simple Network
Management Protocol (SNMP). Port monitoring is available for devices that have implemented
the interface MIB (RFC 2863) and MIB-II (RFC 1213) standards. In addition, peripheral
monitoring, including processor and memory monitoring, is supported on a subset of devices. For
more information, see System Center Operations Manager 2012: Network Devices with Extended
Monitoring Capability.
Operations Manager can identify connected devices in a recursive discovery that use an IPv6
address; however, the initial device that is discovered must use an IPv4 address.
For more information about supported network devices, see Network Devices Supported for
Discovery by Operations Manager 2012.

Application Performance Monitoring Requirements

To view Application Performance Monitoring event details, you must install the Operations
Manager web console. For more information, see How to Install the Operations Manager Web
Console.
Application Performance Monitoring requires the following software:
.NET Framework 2.0, .NET Framework 3.5, .NET Framework 3.5 SP1, or .NET Framework 4.
Internet Information Services (IIS) 7.0. Application monitoring on a clustered IIS configuration
is not supported.
ISAPI and CGI Restrictions in IIS be enabled for ASP.NET 4.0. To enable this, select the web
server in IIS Manager, and then double-click ISAPI and CGI Restrictions. Select ASP.NET
v4.0.30319, and then click Allow.
Additionally, you must start the SQL Server Agent service and set the startup type to automatic.

58