Export (0) Print
Expand All

Operations Manager 2007 R2 Supported Configurations

Updated: February 18, 2013

Applies To: Operations Manager 2007 R2

Did you know that System Center 2012 is available? System Center 2012 offers you a single, flexible platform to manage traditional datacenters, private and public clouds, and client computers and devices. Learn more about System Center 2012.

This document provides information about the supported operating systems, hardware configurations, software requirements, installation combinations, and security configurations for Microsoft System Center Operations Manager 2007. This document focuses on the supported configurations 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.

You can use the Operations Manager 2007 Prerequisite Viewer to check the hardware and software prerequisites and to create a report that lists which prerequisites your system meets or does not meet to install and use Operations Manager 2007.

noteNote
Operations Manager 2007 components can be installed on the same computers with Operations Manager 2005 components.

noteNote
Operations Manager 2007 SP1 is supported on Windows Server 2008. Both Windows Server 2008 and Operations Manager 2007 SP1 hotfixes are required. Official supported scenarios with the required hotfixes can be found at: http://go.microsoft.com/fwlink/?LinkId=119299. Operations Manager 2007 R2 is supported on Windows Server 2008, no hotfixes are required.

It is recommended that you also review the key concepts of Operations Manager 2007 and your deployment design and planning documents. Areas to review include the following:

  • The Operations Manager 2007 Release Notes identify any changes that could affect planning for a new deployment of Operations Manager 2007.

  • The Microsoft Operations Manager 2007 security content provides detailed information about the security-related features and settings in Operations Manager 2007 that can affect your deployment.

Operations Manager 2007 Virtualization Support

Microsoft supports running all Operations Manager 2007 components in any physical or virtual environment that meets the minimum requirements that are stated in this document. However, for performance reasons, Microsoft recommends against virtualizing the root management server (RMS), the OperationsManager database, and the OperationsDW database. There are some restrictions on virtualization functionality that can be used with Operations Manager 2007. Specifically, virtual computers running any Operations Manager 2007 component must not make use of any functionality where all activity on the virtual computer is not immediately committed 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 no matter what virtualization technology is used with Operations Manager 2007.

Supported Operating Systems

The following table lists the operating systems that are supported by each Operations Manager 2007 component.

 

Operations Manager 2007 Component Supported Microsoft Windows Operating Systems

Operations Manager Operations database

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 Datacenter Edition with SP1 or SP2

Windows Server 2003 Datacenter Edition with SP2

Windows Server 2003 Datacenter x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter x64 Edition with SP1 or SP2

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Management server or root management server

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 Datacenter Edition with SP1

Windows Server 2003 Datacenter Edition with SP2

Windows Server 2003 Datacenter x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter x64 Edition with SP1 or SP2

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter with SP1 or SP232-Bit

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Operations console and Authoring console

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 Datacenter Edition with SP1

Windows Server 2003 Datacenter Edition with SP2

Windows Server 2003 Datacenter x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter x64 Edition with SP1 or SP2

Windows XP Professional with SP2

Windows XP Professional x64 Edition

Windows Vista Ultimate

The 64-bit edition of Windows Vista Ultimate

Windows Vista Business

The 64-bit edition of Windows Vista Business

Windows Vista Enterprise

The 64-bit edition of Windows Vista Enterprise

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Windows 7

Windows 7 with SP1

Reporting data warehouse

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 Datacenter Edition with SP1

Windows Server 2003 Datacenter Edition with SP2

Windows Server 2003 Datacenter x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter x64 Edition with SP1 or SP2

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Reporting server

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 Datacenter Edition with SP1

Windows Server 2003 Datacenter Edition with SP2

Windows Server 2003 Datacenter x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter x64 Edition with SP1 or SP2

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Gateway server

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Web console server

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition

Windows Server 2003 R2 Standard Edition

Windows Server 2003 R2 Standard x64 Edition

Windows Server 2003 R2 Enterprise Edition

Windows Server 2003 R2 Enterprise x64 Edition

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

noteNote
The Operations Manager 2007 Web console browser runs on any operating system that supports Internet Explorer 6, 7, 8 or 9.

Audit database

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 Datacenter Edition with SP1

Windows Server 2003 Datacenter Edition with SP1

Windows Server 2003 Datacenter x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter x64 Edition with SP1 or SP2

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Management server with audit collector

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Management server with Agentless Exception Monitoring file share

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Agent

Windows 2000 Server with Service Pack 4 (SP4)

Windows 2000 Professional with SP4

Windows Server 2003 Standard Edition with Service Pack 1 (SP1)

Windows Server 2003 Standard Edition with Service Pack 2 (SP2)

Windows Server 2003 Standard x64 Edition

Windows Server 2003 Enterprise Edition with SP1

Windows Server 2003 Enterprise Edition with SP2

Windows Server 2003 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 Enterprise Edition for Itanium-based Systems with SP1

Windows Server 2003 Enterprise Edition for Itanium-based Systems with SP2

Windows Server 2003 Datacenter Edition with SP1

Windows Server 2003 Datacenter Edition with SP2

Windows Server 2003 Datacenter x64 Edition with SP1 or SP2

Windows Server 2003 Datacenter Edition for Itanium-based Systems with SP1

Windows Server 2003 Datacenter Edition for Itanium-based Systems with SP2

Windows Server 2003 R2 Standard Edition with SP1 or SP2

Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2

Windows Server 2003 R2 Enterprise Edition for Itanium-based Systems with Service Pack 1 (SP1) or Service Pack 2 (SP2)

Windows Server 2003 R2 Datacenter Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter x64 Edition with SP1 or SP2

Windows Server 2003 R2 Datacenter Edition for Itanium-based Systems with SP1 or SP2

Windows XP Professional with SP2

Windows XP Professional x64 Edition with SP2

Windows Vista Ultimate

The 64-bit edition of Windows Vista Ultimate

Windows Vista Business

The 64-bit edition of Windows Vista Business

Windows Vista Enterprise

The 64-bit edition of Windows Vista Enterprise

Windows Server 2008 Standard 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2

Windows Server 2008 Standard 32-Bit, Core role installed with SP1 or SP2

The 64-bit edition of Windows Server 2008 Standard, Core role installed with SP1 or SP2

Windows Server 2008 Enterprise 32-Bit, Core role installed with SP1 or SP2

The 64-bit edition of Windows Server 2008 Enterprise, Core role installed with SP1 or SP2

Windows Server 2008 Datacenter 32-Bit, Core role installed with SP1 or SP2

The 64-bit edition of Windows Server 2008 Datacenter, Core role installed with SP1 or SP2

Windows Server 2008 for Itanium-based Systems with SP1 or SP2

Windows Server 2008 R2

Windows Server 2008 R2 with SP1

Windows 7

Windows 7 with SP1

Windows Server 2008 Foundation

Microsoft Hyper-V Server 2008

Microsoft Hyper-V Server 2008 R2

WePOS v1

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

Minimum Hardware Requirements

The following table lists the minimum and the recommended hardware requirements for each Operations Manager 2007 component. If you want to install more than one component on the same computer, use the higher of the recommended hardware requirements for any of the combined components.

You can use the Operations Manager 2007 Prerequisite Checker in Setup to check the hardware and software prerequisites and to create a report that lists which prerequisites your system meets or does not meet to install and use Operations Manager 2007.

Supported Processors, Memory, and Disk Space

noteNote
Operations Manager 2007 does not support installing the 32-bit agent on an operating system for x64-based computers. Operations Manager 2007 provides native support for x86-based computers and x64-based computers for all components and support for agents on computers with 64-bit Itanium processors.

 

Operations Manager 2007 Component Recommended Hardware Requirements

Operations Manager Operations database

2.8 GHz or faster

4 GB of RAM or higher

50 GB of available hard disk space

Root management server

2.8 GHz or faster

4 GB of RAM or more

20 GB of available hard disk space

Management server

2.8 GHz or faster

2 GB of RAM or more

20 GB of available hard disk space

Operations console

2.8 GHz or faster

2 GB of RAM or more

20 GB of available hard disk space

Authoring console

2.8 GHz or faster

2 GB of RAM or more

20 GB of available hard disk space

Reporting data warehouse

2.8 GHz or faster

4 GB of RAM or more

100 GB of available hard disk space

Reporting server

2.8 GHz or faster

2 GB or more

20 GB of available hard disk space

gateway server

2.8 GHz or faster

2 GB of RAM or more

20 GB of available hard disk space

Web console server

2.8 GHz or faster

2 GB of RAM or more

20 GB of available hard disk space

Audit database

2.8 GHz or faster

4 GB of RAM or more

100 GB of available hard disk space

Management server with audit collector

2.8 GHz or faster

2 GB of RAM or more

50 GB of available hard disk space

Management server with Agentless Exception Monitoring file share

2.8 GHz or faster

2 GB of RAM or more

30 GB of available hard disk space

Agent

Please refer to the recommended hardware requirement required by the operating system.

Minimum Software Requirements

Operations Manager 2007 components require a supported operating system. For a list of the supported operating systems for each component, see the Supported Operating Systems section earlier in this document.

Note the following database considerations for Operations Manager 2007:

  • Operations Manager 2007 does not support a 32-bit Operations Manager Operations database, Reporting Server data warehouse, or Audit Collection database, or SQL Server Reporting Services on a 64-bit operating system.

  • The use of SQL Server 2005 SP4 is supported for Operations Manager 2007 R2 (See KB2591380 for details.)

  • The use of SQL Server 2008 R2 is supported for both new installations of Operations Manager 2007 R2 (See KB2425714 (http://go.microsoft.com/fwlink/?LinkId=215404) for details) and SQL Server 2008 R2 database upgrades (See KB2449679 (http://go.microsoft.com/fwlink/?LinkId=215802) for details).

  • The use of SQL Server 2008 SP3 is supported for Operations Manager 2007 R2 with CU5 applied. For more information, see the Supported Software Requirements for Operations Manager 2007 table below.

  • The use of SQL Server 2008 R2 Service Pack 2 is supported for Operations Manager 2007 R2 with Cumulative Update 7 applied. Note: Installation of reporting mail fail with SQL Server 2008 R2 SP2. If this occurs, follow the procedures in the Support article: Support for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database.

  • Using a different version of SQL Server for different Operations Manager 2007 roles is not supported. The same version should be used for each role.

  • SQL collation for all databases must be SQL_Latin1_General_CP1_CI_AS; no other collation configurations are supported.

The following table lists the minimum software requirements for each Operations Manager 2007 component beyond the operating system. If you want to install more than one component on the same computer, you must install the prerequisite software for all the combined components.

Supported Software Requirements for Operations Manager 2007

 

Operations Manager Component Software Requirement(s)

Operations Manager Operations database

  • SQL Server 2005 Standard or SQL Server 2005 Enterprise Edition SP1, SQL Server 2005 Enterprise Edition SP2, SQL Server 2005 Enterprise Edition SP3, or SQL Server 2005 Enterprise Edition SP4, or SQL Server 2008 SP1, SQL Server 2008 SP2, SQL Server 2008 R2, or SQL Server 2008 R2 SP1. For Operations Manager 2007 R2 with CU5 applied, SQL Server 2008 SP3 is supported. For Operations Manager 2007 R2 with Cumulative Update 7 applied, SQL Server 2008 R2 Service Pack 2 is supported.

  • SQL collation must be SQL_Latin1_General_CP1_CI_AS; no other collation configurations are supported

Management server and root management server

  • .NET Framework 2.0

  • .NET Framework 3.0

  • Microsoft Core XML Services (MSXML) 6.0

  • WS-MAN v1.1 (this is only needed if UNIX\Linux computers will be monitored)

Reporting server

  • .NET Framework 3.0

  • SQL Server 2005 Reporting Services with Service Pack 1, Service Pack 2, Service Pack 3 or Service Pack 4 (See KB2591380),or SQL Server 2008 Reporting Services with Service Pack 1, Service Pack 2, or SQL Server 2008 R2 Reporting Services. For Operations Manager 2007 R2 with CU5 applied, SQL Server 2008 SP3 is supported. For Operations Manager 2007 R2 with Cumulative Update 7 applied, SQL Server 2008 R2 Service Pack 2 is supported. Note: Installation of reporting mail fail with SQL Server 2008 R2 SP2. If this occurs, follow the procedures in the Support article: Support for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database.

    noteNote
    When using SQL 2008 Service Pack 2, reports will only run correctly from the Operations Console. Running reports directly from SQL Reporting Services will not render correctly. This is a known issue that will be corrected in a future Cumulative Update.

gateway server

  • .NET Framework 2.0

  • Microsoft Core XML Services (MSXML) 6.0

Reporting data warehouse

  • SQL Server 2005 Standard or SQL Server 2005 Enterprise Edition with Service Pack 1, Service Pack 2, Service Pack 3, or Service Pack 4, or SQL Server 2008 with Service Pack 1, Service Pack 2, SQL Server 2008 R2, or SQL Server 2008 R2 SP1. For Operations Manager 2007 R2 with CU5 applied, SQL Server 2008 SP3 is supported. For Operations Manager 2007 R2 with Cumulative Update 7 applied, SQL Server 2008 R2 Service Pack 2 is supported. Note: Installation of reporting mail fail with SQL Server 2008 R2 SP2. If this occurs, follow the procedures in the Support article: Support for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database.

Audit collection database

  • SQL Server 2005 Standard Edition or SQL Server 2005 Enterprise Edition with Service Pack 1, Service Pack2, Service Pack 3 or Service Pack 4, or SQL Server 2008 with Service Pack 1, Service Pack 2, SQL Server 2008 R2, or SQL Server 2008 R2 SP1. For Operations Manager 2007 R2 with Cumulative Update 7 applied, SQL Server 2008 R2 Service Pack 2 is supported.

Operations console

  • .NET Framework 2.0

  • .NET Framework 3.0

  • Optionally, Windows PowerShell. It is required for the Operations Manager 2007 Command Shell.

  • Optionally, Microsoft Office Word 2003 with the .NET Programmability feature and Microsoft Visual Studio 2005 Tools for the Microsoft Office System. They are required to create or edit management pack knowledge data.

Web console server

  • .NET Framework 2.0

  • .NET Framework 3.0

  • Internet Information Services, an optional component of Windows Server 2003.

  • ASP.NET, an optional component of Windows Server 2003

  • Microsoft ASP.NET 2.0 AJAX Extensions 1.0

Agent

  • Microsoft Core XML Services (MSXML) 6.0

noteNote
MSXML 6.0 requires Windows Installer 3.1

Authoring console

  • .NET Framework 2.0

  • .NET Framework 3.0

  • .NET Framework 3.5 SP1

  • Optionally, Microsoft Windows PowerShell. It is required for the Operations Manager 2007 Command Shell.

  • Optionally, Microsoft Office Word 2003 with the .NET Programmability feature and Microsoft Visual Studio 2005 Tools for the Microsoft Office System. They are required to create or edit management pack knowledge data.

Supported Firewall Scenarios

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

Operations Manager 2007 Firewall Scenarios

 

Operations Manager 2007 Component A Port Number and Direction Operations Manager 2007 Component B Configurable Note

Root management server

1433 --->

OperationsManager database

Yes (Setup)

 

Root management server

1434 UDP < ---

OperationsManager database

No

If the OperationsManager database is installed on a named instance of SQL Server 2005 or 2008 (such as in a cluster) and the Windows Firewall is enabled on the RMS server, then you will need to also open UDP 1434 inbound on the RMS server

Management server

1433 --->

OperationsManager database

Yes (Setup)

 

Management server

5723, 5724 --->

Root management server

No

Port 5724 must be open to install this component and can be closed after this component has been installed.

Management server

1433 -->

reporting data warehouse

No

gateway server

5723 --->

Root management server

No

 

Root management server

1433 --->

Reporting data warehouse

No

 

Reporting server

5723, 5724 --->

Root management server

No

Port 5724 must be open to install this component and can be closed after this component has been installed.

Operations console

5724 --->

Root management server

No

 

Connector framework source

51905 --->

Root management server

No

 

Web console server

5724 --->

Root management server

No

 

Web console browser

51908 --->

Web console server

Yes (IIS Admin)

Port 51908 is the default port used when selecting Windows Authentication. If you select Forms Authentication, you will need to install an SSL certificate and configure an available port for https functionality for the Operations Manager 2007 Web Console Web site.

Connected root management server (Local)

5724 --->

Connected root management server (Connected)

No

 

Agent installed using MOMAgent.msi

5723 --->

Root management server

Yes (Setup)

 

Agent installed using MOMAgent.msi

5723 --->

Management server

Yes (Setup)

 

Agent installed using MOMAgent.msi

5723 --->

gateway server

Yes (Setup)

 

gateway server

5723 --->

Management server

Yes (Setup)

 

Agent (Audit Collection Services forwarder)

51909 --->

Management server Audit Collection Services collector

Yes (Registry)

 

Agentless Exception Monitoring data from client

51906 --->

Management server Agentless Exception Monitoring file share

Yes (Client Monitoring Wizard)

 

Customer Experience Improvement Program data from client

51907 --->

Management server (Customer Experience Improvement Program End) Point

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 Web site.

Reporting server

1433 --->

Reporting data warehouse

Yes

 

Management server (Audit Collection Services collector)

1433 --->

Audit Collection Services database

Yes

 

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 2005 or SQL Server 2008 is installed 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 2007 requires the following minimum network connectivity speeds between the specified components.

 

Component A Component B Minimum Requirement

Root management server or management server

Agent

64 Kbps

Root management server or management server

Agentless

1024 Kbps

Root management server or management server

Database

256 Kbps

Root management server

Console

768 Kbps

Root management server

Management server

64 Kbps

Root management server or management server

Data warehouse database

768 Kbps

Root 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

Supported Cluster Configurations

Operations Manager 2007 supports the clustering configurations for Operations Manager server roles as shown in the following table:

Only Cluster service quorum node clusters are supported. Multisite clusters (geographically dispersed clusters) are supported for all Operations Manager 2007 cluster roles. You can use replication technology to help provide high availability for data in Operations Manager 2007, but the latency of communications between components introduce risks to data replication and might introduce failover issues. For best practices on multisite clustering see “Geographically Dispersed Clusters in Windows Server 2003” at http://go.microsoft.com/fwlink/?LinkId=151337 It is recommended that you use synchronous mirroring of data disks between sites, this means that the data is fully synchronized across all sites. This will ensure the correct behavior of applications in the event of failover across sites.

ImportantImportant
Microsoft is not obligated to release a fix on any Operations Manager 2007 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 Role Cluster Notes

Operations Manager 2007 Operations database

Single Active-Passive cluster

Setup needs to be run only once on the active node of the cluster. Other Operations Manager 2007 server roles must not be installed on the cluster or nodes of the cluster.

Root management server

Single Active-Passive cluster

Setup needs to be run on every node of the cluster. Other Operations Manager 2007 server roles must not be installed on the cluster or nodes of the cluster.

Operations Manager 2007 Reporting data warehouse

Single Active-Passive cluster

Other Operations Manager 2007 server roles must not be installed on the cluster or nodes of the cluster.

Audit collection database

Single Active-Passive cluster

Other Operations Manager 2007 server roles must not be installed on the cluster or nodes of the cluster.

noteNote
A root management server is the first management server installed in a management group

noteNote
For clustering Operations Manager 2007 on Windows Server 2008, see: http://go.microsoft.com/fwlink/?LinkId=119299

Supported, But Not Recommended Cluster Configurations

Operations Manager 2007 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 SQL Server-based computer, these configurations are not recommended:

 

Server Role Cluster Notes

Operations Manager 2007 Operations database and Operations Manager 2007 Reporting data warehouse.

Active-Active cluster where the Operations Manager Operations 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 Operations database, Reporting data warehouse, and audit collection 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 Operations database and audit collection 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 Operations 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 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.

Non-Supported Cluster Configurations

The cluster configurations listed in the following table are not supported:

 

Server Role Cluster Notes

Operations Manager Operations database and root management server

Single Active-Passive where both components are on the same node of the cluster.

Not supported

Operations Manager Operations database and root management server

Active-Active-Passive cluster where the Operations Manager Operations database in one active node, the root management server is on the other active node, and the passive node acts as the failover node for both.

Not supported

Operations Manager Operations database and root management server

Active-Active cluster where the Operations Manager Operations database is on one active node, the root management server is on the other active node, and they each act as the passive node for the other component.

Not supported

UNIX or Linux Operating Systems

Operations Manager 2007 R2 supports monitoring UNIX or Linux computers. The list of UNIX or Linux operating systems that Operations Manager 2007 R2 can monitor is listed below.

  • AIX 5.3 (Power), 6.1 (Power)

  • HP-UX 11iv2 (PA-RISC and IA64), and 11iv3 (PA-RISC and IA64)

  • Red Hat Enterprise Linux 4 (x86 and x64), 5 (x86 and x64), and 6 (x86 and x64)

  • Solaris 8 (SPARC), 9 (SPARC) and 10 (SPARC and x86 versions later than 120012-14)

  • SUSE Linux Enterprise Server 9 (x86), 10 SP1 (x86 and x64), and 11 (x86 and x64)

noteNote
SUSE Linux Enterprise Server 11 (x86 and x64) support requires Cross Platform Cumulative Update 2 (KB979490) for System Center Operations Manager 2007 R2.  Red Hat Enterprise Linux version 6 support requires Cumulative Update 5 (KB2495674).

Monitored Item Capacity

Operations Manager 2007 R2 supports the following number of monitored items. For monitored Item Capacity for Operations Manager 2007 SP1, see the Operations Manager 2007 SP1 Supported Configurations.

 

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

1,500

Agentless Exception Monitored computers per dedicated management server

25,000

Agentless Exception Monitored 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); 10,000 (with 25 open consoles

UNIX or Linux computers per dedicated management server

500

UNIX or Linux computers monitored per dedicated gateway server

100

URLs monitored per dedicated management server

3000

URLs monitored per dedicated management group

12,000

URLs monitored per agent

50

Operations Manager 2007 Component Firewall Exceptions

 

Component Exception Port and Protocol Configured By

RMS

  • 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

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

51908/TCP

Setup

Web console, forms authentication, http

World Wide Web Services, http

80/TCP

Windows Firewall

Web console, forms authentication, https

Secure World Wide Web Service

443/TCP

Windows Firewall

OperationsManager 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 Service database

  • SQL Server

  • If using a named instance, add

1433/TCP

1434/UDP

Windows Firewall

Windows Firewall

Operations Manager Audit Collection Service Collector

ACS Collector Service

51909/TCP

Windows Firewall

Support for Languages in Addition to English

Operations Manager supports the following languages: English, German, French, Japanese, Spanish, Korean, Simplified Chinese, Traditional Chinese, Russian, Italian, and Portuguese (Brazil).

Supported components for different languages

If your systems run a language other than English, you can install Operations Manager 2007 for that language. You also have the option of installing English Operations Manager 2007 for your management group.

For instance, if you use a German version of a Windows operating system on all your servers, you can install German Operations Manager 2007 components 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 2007 components 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.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft