(0) exportieren Drucken
Alle erweitern
EN
Dieser Inhalt ist in Ihrer Sprache leider nicht verfügbar. Im Folgenden finden Sie die englische Version.

Preparing your environment for System Center 2012 R2 Operations Manager

Updated: July 9, 2014

Applies To: System Center 2012 R2 Operations Manager

Here are the system requirements and considerations to keep in mind before you deploy System Center 2012 R2 Operations Manager.

If you’re evaluating your environment, see System Requirements for System Center 2012 R2

Before you begin, it’s a good idea to get to know this information:

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.

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.

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.

System Center 2012 R2 Operations Manager runs on virtual machines in Microsoft Azure just as it does on physical computer systems. We recommend using Operations Manager with Microsoft Azure virtual machines in the following scenarios:

  • Scenario 1: You can run Operations Manager on a Microsoft Azure virtual machine and use it to monitor other Microsoft Azure virtual machines.

  • Scenario 2: You can run Operations Manager on a Microsoft Azure virtual machine and use it to monitor instances that are not running on Microsoft Azure.

  • Scenario 3: You can run Operations Manager on-premises and use it to monitor Microsoft Azure virtual machines.

Microsoft tested Operations Manager by installing and using it in a Microsoft Azure virtual machine. The standard sizing and supported configuration for Operations Manager applies to Microsoft 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

noteNote
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 Server Operating Systems in System Center 2012 R2.

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 install Operations Manager without WoW64 support installed, you’ll see an error message telling you that the side-by-side configuration is wrong.

Check for updates and hotfixes for Microsoft SQL Server. See SQL Server in System Center 2012 R2.

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

  • For SQL Server collation settings, see SQL Server in System Center 2012 R2

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

 

Hardware/Software Requirement

Disk space

%SYSTEMDRIVE% requires at least 1024 MB free hard disk space

Server Operating System

See Server Operating Systems in System Center 2012 R2

Processor architecture

x64

Windows PowerShell

See Windows PowerShell Support in System Center 2012 R2

Windows Remote Management

Windows Remote Management must be enabled for the management server

.NET Framework 

.NET Framework 4 or .NET Framework 4.5 is required. For more information, see .NET Framework in System Center 2012 R2 and .NET Framework 4 redistributable package

  • You need Microsoft Report Viewer 2012 Redistributable Package

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

 

Hardware/Software Requirement

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

See Server Operating Systems in System Center 2012 R2

Processor architecture

x64 for servers and x64 or x86 for a client computer

Windows Installer

At least Windows Installer 3.1

Windows PowerShell

See Windows PowerShell Support in System Center 2012 R2

.NET Framework

For more information, see .NET Framework 4 redistributable package

 

Hardware/Software Requirement

Operating System

See Server Operating Systems in System Center 2012 R2

Processor architecture

x64

Web browsers

See Self-Service Web Console Support in System Center 2012 R2a

Internet Information Services (IIS)

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

  • ImportantImportant
    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:

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

ImportantImportant
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

 

Hardware/Software Requirement

Disk space

Needs 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 systems

See Server Operating Systems in System Center 2012 R2

Processor architecture

x64

Windows Installer

At least Windows Installer 3.1

Microsoft SQL Server

See SQL Server in System Center 2012 R2

SQL Server Full Text Search

Required

.NET Framework

.NET Framework 4 is required. For more information, see .NET Framework in System Center 2012 R2 and .NET Framework 4 redistributable package

 

Hardware/Software Requirement

File system

%SYSTEMDRIVE% must be formatted with the NTFS file system

Operating systems

See Server Operating Systems in System Center 2012 R2

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

Windows PowerShell version 2.0, or Windows PowerShell version 3.0

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

 

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

Operating system

See Server Operating Systems in System Center 2012 R2

Processor architecture

x64

Microsoft SQL Server

See SQL Server in System Center 2012 R2

Remote Registry service

must be enabled and started

Microsoft SQL Server Reporting Services

See SQL Server in System Center 2012 R2

WarningWarning
System Center 2012 – Operations Manager supports SQL Server Reporting Services in native mode only; do not use SharePoint integrated mode.

.NET Framework

.NET Framework 4 is required. For more information, see .NET Framework in System Center 2012 R2 and .NET Framework 4 redistributable package

 

Hardware/Software Requirement

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

See Server Operating Systems in System Center 2012 R2

Processor architecture

x64

Windows Installer version

At least Windows Installer 3.1

Microsoft SQL Server Full Text Search

Required

.NET Framework

.NET Framework 4 is required for Setup to run. For more information, see .NET Framework in System Center 2012 R2 and .NET Framework 4 redistributable package

 

Hardware/Software Requirement

Disk space

%SYSTEMDRIVE% requires at least 1024 MB free hard disk space

Server operating system

Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 Core Installation, or Windows Server® 2012 R2.

Processor architecture

x64

Windows PowerShell

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

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

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

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

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

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 Application Advisor)

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.

Agent installed by using MOMAgent.msi

5723 --->

Management server

Yes (Setup)

Agent installed by using MOMAgent.msi

5723 --->

Management 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)

51909 --->

Management server Audit Collection Services (ACS) Collector

Yes (Registry)

Agentless Exception Monitoring data from client

51906 --->

Management server Agentless Exception Monitoring (AEM) file share

Yes (Client Monitoring Wizard)

Customer Experience Improvement Program data from client

51907 --->

Management 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

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

22 --- >

UNIX or Linux computer

Yes

In the preceding table, if SQL Server 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).

 

Feature Exception Port and protocol Configured by

Management server

  • System Center Management service

  • System Center Data Access service

  • Operations Manager Connector Framework

  • Operations Manager Customer Experience Improvement

  • Operations Manager Application Error Monitoring

5723/TCP

5724/TCP

51905/TCP

51907/TCP

51906/TCP

Setup

Setup

Setup

Setup

Setup

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

443/TCP

Windows Firewall

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

80/TCP

Windows Firewall

Agent, manual installation of MOMAgent.msi

System Center Management service

5723/TCP

Windows Firewall

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

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 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:

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

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.

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

Operations Manager Reporting data warehouse

Single Active-Passive cluster

Other Operations Manager features must not be installed on the cluster or nodes of the cluster.

Audit Collection Services (ACS) database

Single Active-Passive cluster

Other Operations Manager features must not be installed on the cluster or nodes of the cluster.

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 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 other node of the cluster.

There might be some performance issues with SQL Server in this configuration.

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 performance issues with SQL Server in this configuration.

Operations Manager operational database and Audit Collection Services database.

Single Active-Passive cluster where both components are on a single cluster.

There might be some performance issues with SQL Server in this configuration.

Operations Manager operational database and Reporting data warehouse.

Single Active-Passive cluster where both components are on a single cluster.

There might be some performance issues with SQL Server in this configuration.

Reporting data warehouse and Audit Collection Services database.

Single Active-Passive cluster where both components are on a single cluster.

There might be some performance issues with SQL Server in this configuration.

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

Agent-monitored computers reporting to a gateway server

2,000

Agentless Exception Monitored (AEM)-computers per dedicated management server

25,000

Agentless Exception Monitored (AEM)-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 management server

10

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

URLs monitored per dedicated management group

12,000

URLs monitored per agent

50

For supported languages, see Language Support for System Center 2012 R2

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.

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.

    noteNote
    Application monitoring built 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.

 
Fanden Sie dies hilfreich?
(1500 verbleibende Zeichen)
Vielen Dank für Ihr Feedback.
Anzeigen:
© 2014 Microsoft