system requirements for system center 2012 · pdf filesystem requirements for system center...

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].

mailto:[email protected]?subject=System%20Center%202012%20System%20Requirements%20Operations%20%20Manager%20(SP1)%20Documentation%20published%20November,%201,%202013

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

4

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.

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:

Note

http://go.microsoft.com/fwlink/p/?LinkId=309285


http://go.microsoft.com/fwlink/?LinkId=306555

5

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


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.

6

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.


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

supported screen resolution is 1024 x 768.


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

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.


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

Note


7

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.


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.




8

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

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.


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.


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

Important










9

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.

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

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.

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


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.


Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012

Core Installation or Windows Server® 2012 R2.

Processor Architecture: x64.


Important

Note

Important


http://go.microsoft.com/fwlink/p/?linkID=248494


10

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


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.

Windows PowerShell is required for agents that will be monitored by a management

pack that uses Windows PowerShell scripts.


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)


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

Note



11

Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server

2012 Core Installation or Windows Server® 2012 R2.


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:



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.


Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server

2012 Core Installation or Windows Server® 2012 R2.







document:




Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012,

Windows Server 2012 Core Installation or Windows Server® 2012 R2.



version 3.0.


for the management server.

.NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network

devices.






12


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

Manager Feature A

Port number

and direction

Feature B Configurable Note

Management server 1433 ---> Operational

database

Yes (Setup)

Management server 1434 UDP < -

--

Operational

database

No If the operational

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.


database

Yes (Setup)

Management server 5723, 5724 --

->

Management

server

No Port 5724 must be

open to install this

feature and can be

closed after this

feature has been

installed.

Management server 1433 --> Reporting data

warehouse

No

13

Operations

Manager Feature A

Port number

and direction


Management server 1433 ---> Reporting data

warehouse

No

Reporting server 5723, 5724 --

->

Management

server



feature and can be

closed after this

feature has been

installed.

Operations console 5724 ---> Management

server

No

Connector

Framework source

51905 ---> Management

server

No

Web console server Selected web

site port --->

Management

server

No

Web console (for

Application

Diagnostics

1433, 1434 --

->

Operational

database

Yes (Setup)

Web console (for

Application Advisor)

1433, 1434 --

->

Data warehouse Yes (Setup)

Web console (for


80 ---> SQL Server

Reporting

Services

No

Web console browser 80, 443 ---> web console

server

Yes (IIS Admin) Default for HTTP

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.

14

Operations

Manager Feature A

Port number

and direction


Agent installed by

using MOMAgent.msi


server

Yes (Setup)

Agent installed by

using MOMAgent.msi


server

Yes (Setup)

Agent installed by

using MOMAgent.msi

5723 ---> Gateway server Yes (Setup)

Gateway server 5723 ---> Management

server

Yes (Setup)

Agent (Audit

Collection Services

(ACS) forwarder)


server Audit

Collection

Services (ACS)

Collector

Yes (Registry)

Agentless Exception

Monitoring data from

client


server Agentless

Exception

Monitoring (AEM)

file share

Yes (Client

Monitoring

Wizard)

Customer Experience

Improvement

Program data from

client


server (Customer

Experience

Improvement

Program)

Endpoint

Yes (Client

Monitoring

Wizard)

Operations console

(reports)

80 ---> SQL Server

Reporting

Services

No The Operations

console uses port

80 to connect to

the SQL Server

Reporting Services

website.

Reporting server 1433 ---> Reporting data

warehouse

Yes

Management server

(Audit Collection

Services Collector)

1433 ---> Audit Collection

Services (ACS)

database

Yes

15

Operations

Manager Feature A

Port number

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

or gateway server

1270 --- > UNIX or Linux

computer

No

Management server

or gateway server


computer

Yes

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.

16

5. Click IP Addresses.

6. The port is under IPAll (usually the TCP Dynamic Ports).


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

(tiered)

1024 Kbps

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


Operations Manager supports the clustering configurations for Operations Manager features as

shown in the following table:

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.

Important



17

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.

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

Operational database

Single Active-Passive cluster Other Operations Manager

features must not be installed

on the cluster or nodes of the

cluster.


data warehouse




cluster.

Audit Collection Services (ACS)

database




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:


Operations Manager

operational database and

Operations Manager

Reporting data warehouse.

Active-Active cluster where the

operational database is

installed on one node of the

cluster and the Reporting data

warehouse is installed on the

There might be some

performance issues with SQL

Server in this configuration.

Important

18


other node of the cluster.

Operations Manager

operational database,

Reporting data warehouse,

and Audit Collection Services

(ACS) database.

Single Active-Passive or

Active-Active cluster where all

three components are on a

single cluster.

There might be some



Operations Manager


Audit Collection Services

database.

Single Active-Passive cluster

where both components are

on a single cluster.

There might be some



Operations Manager






There might be some



Reporting data warehouse


database.




There might be some




Operations Manager supports the following number of monitored items.

Monitored item Recommended limit

Simultaneous Operations consoles 50

Agent-monitored computers reporting to a

management server

3,000


gateway server

2,000

Agentless Exception Monitored (AEM)-

computers per dedicated management server

25,000


computers per management group

100,000

Collective client monitored computers per

management server

2,500

Management servers per agent for multihoming 4

Agentless-managed computers per 10

19


management server

Agentless-managed computers per

management group

60

Agent-managed and UNIX or Linux computers

per management group

6,000 (with 50 open consoles); 15,000 (with 25

open consoles)

UNIX or Linux computers per dedicated

management server

500

UNIX or Linux computers monitored per

dedicated gateway server

100

Network devices managed by a resource pool

with three or more management servers

1,000

Network devices managed by two resource

pools

2,000

Agents for Application Performance Monitoring

(APM)

700

Applications for Application Performance

Monitoring (APM)

400

URLs monitored per dedicated management

server

3000


group

12,000

URLs monitored per agent 50


Feature Exception Port and protocol Configured by

Management server System Center

Management

service

System Center

Data Access

service

Operations

Manager

5723/TCP

5724/TCP

51905/TCP

51907/TCP

51906/TCP

Setup

Setup

Setup

Setup

Setup

20


Connector

Framework

Operations

Manager Customer

Experience

Improvement

Operations

Manager

Application Error

Monitoring

Web console Operations Manager

web console

Selected web site

port/TCP

Setup

Web console, http World Wide Web

Services, http

80/TCP Windows Firewall

Web console, https Secure World Wide

Web Service, https


Operational database SQL Server

database server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

data warehouse

database

SQL Server

database server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

Reporting

SQL Server Reporting

Services


Agent, manual

installation of

MOMAgent.msi

System Center

Management service


Agent, push installation System Center

Management

service

File and Print

Sharing

Remote

Administration

5723/TCP

137/UDP, 138/UDP,

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

Agent, pending repair System Center

Management

5723/TCP

137/UPD, 138/UPD,

Windows Firewall

21


service

File and Print

Sharing

Remote

Administration

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Agent, pending upgrade System Center

Management

service

File and Print

Sharing

Remote

Administration

5723/TCP

137/UDP, 138/UDP,

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

Gateway System Center

Management service

5723/TCP Setup

Operations Manager

Audit Collection

Services database

SQL Server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

Audit Collection

Services Collector

ACS Collector Service 51909/TCP Windows Firewall


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.

22

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.


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.


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.

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.

Note





http://go.microsoft.com/fwlink/p/?LinkID=225203


23

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.

For system requirements across all components of System Center 2012 SP1, see

System Requirements for System Center 2012 SP1.




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.







Management Server

Operations Console

Web Console


Operations Manager Agent – Windows-Based Computers






Note

24









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.





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.




and consoles, and x64-based computers for all server features and support for agents on

computers with 64-bit Itanium processors.




in this document.

Note


25

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.

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.






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.


automatic.

Important

http://blogs.technet.com/b/servicemanager/archive/2012/05/24/clarification-on-sql-server-collation-requirements-for-system-center-2012.aspx

http://blogs.technet.com/b/servicemanager/archive/2012/05/24/clarification-on-sql-server-collation-requirements-for-system-center-2012.aspx

26

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.






If you plan to use the Network Monitoring features of System Center 2012 – Operations






Management Server


Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or

Windows Server 2012 Core Installation.



version 3.0.


management server.



Operations Console

Microsoft Report Viewer 2010 SP1 Redistributable Package



Server Operating System: must be Windows 7, Windows 8, Windows Server 2008 R2 SP1,

or Windows Server 2012.





Linux computers.









27

Web Console

Operating System: Windows Server 2008 R2 SP1, or Windows Server 2012.


Web browsers: Internet Explorer 8, Internet Explorer 9, Internet Explorer 10, Silverlight 5.0



Static Content

Default Document

Directory Browsing

HTTP Errors

HTTP Logging

Request Monitor

Request Filtering




ASP.NET (both the 2.0 and 4.0 versions of ASP.NET are required.)



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.


documents:





Allow.





Important

Note

Important


28




about SQL Server Planning, see Installing SQL Server 2008 or Installing SQL Server 2008

R2.


Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server

2012 Core Installation.



Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server

2012, SQL Server 2012 SP1.







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.



for the Operations Manager agent.


version 3.0.


pack that uses Windows PowerShell scripts.



CentOS 5 and 6 (x86/x64)

Debian GNU/Linux 5, 6, and 7 (x86/x64)


Note





29




Oracle Linux 5 and 6 (x86/x64)


Ubuntu Linux Server 10.04 and 12.04 (x86/x64)



Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows

Server 2012 Core Installation.





Microsoft SQL Server Reporting Services: SQL Server SQL 2008 R2 SP1, SQL Server 2008

R2 SP2, SQL Server 2012, SQL Server 2012 SP1.











Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows

Server 2012 Core Installation.







document:







30



Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, or

Windows Server 2012 Core Installation.



version 3.0.




devices.



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

Manager Feature A

Port number

and direction



database

Yes (Setup)


--

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

31

Operations

Manager Feature A

Port number

and direction


server.


database

Yes (Setup)


->

Management

server



feature and can be

closed after this

feature has been

installed.


warehouse

No


warehouse

No

Reporting server 5723, 5724 --

->

Management

server



feature and can be

closed after this

feature has been

installed.


server

No

Connector

Framework source


server

No


site port --->

Management

server

No

Web console (for

Application

Diagnostics

1433, 1434 --

->

Operational

database

Yes (Setup)

Web console (for


1433, 1434 --

->


Web console (for


80 ---> SQL Server

Reporting

Services

No


server


or SSL.

32

Operations

Manager Feature A

Port number

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

using MOMAgent.msi


server

Yes (Setup)

Agent installed by

using MOMAgent.msi


server

Yes (Setup)

Agent installed by

using MOMAgent.msi



server

Yes (Setup)

Agent (Audit

Collection Services

(ACS) forwarder)


server Audit

Collection

Services (ACS)

Collector

Yes (Registry)

Agentless Exception


client


server Agentless

Exception

Monitoring (AEM)

file share

Yes (Client

Monitoring

Wizard)

Customer Experience

Improvement

Program data from

client


server (Customer

Experience

Improvement

Program)

Endpoint

Yes (Client

Monitoring

Wizard)

Operations console 80 ---> SQL Server

Reporting

No The Operations

console uses port

33

Operations

Manager Feature A

Port number

and direction


(reports) Services 80 to connect to

the SQL Server

Reporting Services

website.


warehouse

Yes

Management server

(Audit Collection

Services Collector)


Services (ACS)

database

Yes


>


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

or gateway server


computer

No

Management server 22 --- > UNIX or Linux Yes

34

Operations

Manager Feature A

Port number

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:




4. Open TCP/IP.





specified features.











(tiered)

1024 Kbps





35




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.






Operations Manager





cluster.


data warehouse




cluster.


database




cluster.





Important

Important

36


Operations Manager


Operations Manager








There might be some



Operations Manager




(ACS) database.




single cluster.

There might be some



Operations Manager



database.




There might be some



Operations Manager






There might be some





database.




There might be some








management server

3,000


gateway server

2,000



25,000



100,000

37



management server

2,500



management server

10


management group

60




open consoles)

UNIX or Linux computers per dedicated

management server

500



100



1,000


pools

2,000


(APM)

700


Monitoring (APM)

400


server

3000


group

12,000





Management

service

5723/TCP

5724/TCP

Setup

Setup

38


System Center

Data Access

service

Operations

Manager

Connector

Framework

Operations

Manager Customer

Experience

Improvement

Operations

Manager

Application Error

Monitoring

51905/TCP

51907/TCP

51906/TCP

Setup

Setup

Setup


web console

Selected web site

port/TCP

Setup


Services, http



Web Service, https



database server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

data warehouse

database

SQL Server

database server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

Reporting


Services


Agent, manual

installation of

MOMAgent.msi

System Center

Management service



Management

service

File and Print

5723/TCP

137/UDP, 138/UDP,

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall

39


Sharing

Remote

Administration


Management

service

File and Print

Sharing

Remote

Administration

5723/TCP

137/UPD, 138/UPD,

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall


Management

service

File and Print

Sharing

Remote

Administration

5723/TCP

137/UDP, 138/UDP,

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall


Management service

5723/TCP Setup

Operations Manager

Audit Collection

Services database

SQL Server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

Audit Collection

Services Collector



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.




management group.


you can install German Operations Manager features for your entire management group. If you

40

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.



Locale type.





















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.











41

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.




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.







Management Server

Operations Console

Web Console














http://go.microsoft.com/fwlink/?LinkID=328069

42




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.





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.




and consoles, and x64-based computers for all server features and support for agents on

computers with 64-bit Itanium processors.




in this document.

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

Note

Important


43

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.






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.


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.






If you plan to use the Network Monitoring features of System Center 2012 – Operations






Management Server


Server Operating System: must be Windows Server 2008 R2 SP1.


Windows PowerShell version: Windows PowerShell version 2.0.


management server.




44



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


Operations Console

Microsoft Report Viewer 2010 Redistributable Package

Microsoft .NET Framework 3.5 SP1 hotfix



Server Operating System: must be Windows Vista, Windows 7, Windows Server 2008,

Windows Server 2008 R2, or Windows Server 2008 R2 SP1.





Linux computers.

Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information,

see the following documents:



Web Console

Operating System: Windows Server 2008 R2 SP1.


Web browsers: Internet Explorer 7, Internet Explorer 8, Internet Explorer 9



Static Content

Default Document

Directory Browsing

HTTP Errors

HTTP Logging

Request Monitor

Request Filtering









45


ASP.NET



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







Allow.








about SQL Server Planning, see Installing SQL Server 2008 or Installing SQL Server 2008

R2.


Operating System: Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.



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.


Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information, see

the following documents:


Warning

Note

Important







46





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.



for the Operations Manager agent.



pack that uses PowerShell scripts.










Operating System: Windows Server 2008 R2 SP1.


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.


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.



Note


47

Both .NET Framework 3.5 SP1 and .NET Framework 4 are required. For more information,

see the following documents:









Operating System: Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.



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.


Both .NET Framework 3.5 SP1 and .NET Framework 4 are required for Setup to run. For






Server Operating System: must be Windows Server 2008 R2 SP1.






devices.



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








48

Operations

Manager Feature A

Port number

and direction



database

Yes (Setup)


--

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.


database

Yes (Setup)


->

Management

server



feature and can be

closed after this

feature has been

installed.


warehouse

No


warehouse

No

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

49

Operations

Manager Feature A

Port number

and direction


-> server open to install this

feature and can be

closed after this

feature has been

installed.


server

No

Connector

Framework source


server

No


site port --->

Management

server

No

Web console (for

Application

Diagnostics

1433, 1434 --

->

Operational

database

Yes (Setup)

Web console (for


1433, 1434 --

->


Web console (for


80 ---> SQL Server

Reporting

Services

No


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

using MOMAgent.msi


server

Yes (Setup)

Agent installed by

using MOMAgent.msi


server

Yes (Setup)

50

Operations

Manager Feature A

Port number

and direction


Agent installed by

using MOMAgent.msi



server

Yes (Setup)

Agent (Audit

Collection Services

(ACS) forwarder)


server Audit

Collection

Services (ACS)

Collector

Yes (Registry)

Agentless Exception


client


server Agentless

Exception

Monitoring (AEM)

file share

Yes (Client

Monitoring

Wizard)

Customer Experience

Improvement

Program data from

client


server (Customer

Experience

Improvement

Program)

Endpoint

Yes (Client

Monitoring

Wizard)

Operations console

(reports)

80 ---> SQL Server

Reporting

Services

No The Operations

console uses port

80 to connect to

the SQL Server

Reporting Services

website.


warehouse

Yes

Management server

(Audit Collection

Services Collector)


Services (ACS)

database

Yes


>


between the

management

servers in the

resource pool and

the network

51

Operations

Manager Feature A

Port number

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

or gateway server


computer

No

Management server

or gateway server


computer

Yes

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:




4. Open TCP/IP.



52



specified features.











(tiered)

1024 Kbps








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.

Warning

53






Operations Manager





cluster.


data warehouse




cluster.


database




cluster.






Operations Manager


Operations Manager








There might be some



Operations Manager




(ACS) database.




single cluster.

There might be some



Operations Manager Single Active-Passive cluster There might be some

Important

54




database.





Operations Manager






There might be some





database.




There might be some








management server

3,000


gateway server

2,000



25,000



100,000


management server

2,500



management server

10


management group

60




open consoles)

UNIX or Linux computers per dedicated 500

55


management server



100



1,000


pools

2,000


(APM)

700


Monitoring (APM)

400


server

3000


group

12,000





Management

service

System Center

Data Access

service

Operations

Manager

Connector

Framework

Operations

Manager Customer

Experience

Improvement

Operations

Manager

5723/TCP

5724/TCP

51905/TCP

51907/TCP

51906/TCP

Setup

Setup

Setup

Setup

Setup

56


Application Error

Monitoring


web console

Selected web site

port/TCP

Setup


Services, http



Web Service, https



database server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

data warehouse

database

SQL Server

database server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

Reporting


Services


Agent, manual

installation of

MOMAgent.msi

System Center

Management service



Management

service

File and Print

Sharing

Remote

Administration

5723/TCP

137/UDP, 138/UDP,

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall


Management

service

File and Print

Sharing

Remote

Administration

5723/TCP

137/UPD, 138/UPD,

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall

Windows Firewall

Windows Firewall


Management

5723/TCP

137/UDP, 138/UDP,

Windows Firewall

Windows Firewall

57


service

File and Print

Sharing

Remote

Administration

139/TCP, 445/TCP

135/TCP, 445/TCP

Windows Firewall


Management service

5723/TCP Setup

Operations Manager

Audit Collection

Services database

SQL Server

If using a named

instance, add.

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager

Audit Collection

Services Collector



Operations Manager supports the following languages: English, German, French, Japanese,

Spanish, Simplified Chinese, Russian, Italian, and Portuguese (Brazil).




management group.


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.



Locale type.







58















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.









