About Operations Manager 2007 Deployment Scenarios

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

All Operations Manager 2007 individual management group deployments will either be an "all-in-one" installation, where all components are loaded on a single server, or a distributed installation, where Operations Manager server roles are distributed across servers. Any number of these can then be combined together to form an overall Operations Manager 2007 infrastructure that consists of multiple management groups. These management groups can then relate to each other in a hierarchical fashion as your business needs dictate. This guide classifies these deployment configurations into three scenarios:

  • Single server, single management group: the all-in-one installation

  • Multiple server, single management group: roles distributed across servers

  • Connected management groups: multiple management groups working together to provide monitoring, alerting, and troubleshooting services

This section of the Operations Manager 2007 Deployment guide describes these scenarios, how they are most commonly used, and any restrictions that may exist with any individual scenario.

In This Section

This guide helps you in the deployment of Operations Manager 2007. It does not assist in the design process. Before you start deploying Operations Manager 2007, you should have completed a design plan that includes a mapping of the following:

  • Business and IT needs to Operations Manager 2007 features and functions.

  • Operations Manager 2007 features a server design that supports those features and functions (a topology).

  • Infrastructure services, such as security, directory, network, and storage, to support the server design.

  • Your company's monitoring, alerting, and troubleshooting processes to the set of Operations Manager 2007 services that you plan to implement.

For complete guidance in developing an Operations Manager design plan, see the Operations Manager 2007 Design Guide at http://go.microsoft.com/fwlink/?LinkId=104550.

Server Role Compatibility

An Operations Manager 2007 management group can provide a multitude of services. These services can be distributed to specific servers, thereby classifying a server into a specific role. Not all server roles and services are typically deployed onto the same server. The following table lists the compatibilities and dependencies and if the role can be installed on a failover cluster.

Server role Requirements and Compatibilities Can be placed in a failover cluster

OperationsManager database

SQL Server 2005 SP1, SQL Server 2005 SP2, SQL Server 2005 SP2a, SQL Server 2005 SP3, or SQL Server 2008 (for Operations Manager 2007 R2 only). This role can be co-deployed with all server roles in the Single Server, Single Management Group scenario (gateway and management server roles are excluded); otherwise, it is most commonly deployed as a stand-alone or co-deployed with other databases.

Yes, n+1 cluster

Audit Collection Services (ACS) database

SQL Server 2005 SP1, SQL Server 2005 SP2, SQL Server 2005 SP2a, SQL Server 2005 SP3, or higher or SQL Server 2008. This role can be co-deployed with all server roles in the Single Server, Single Management Group scenario (gateway and management server roles are excluded); otherwise, it is most commonly deployed in a stand-alone configuration for performance purposes.

Yes, n+1 cluster

Data Warehouse database

SQL Server 2005 SP1, SQL Server 2005 SP2, SQL Server 2005 SP2a, SQL Server 2005 SP3, or SQL Server 2008 (for Operations Manager 2007 R2 only).. This role can be co-deployed with all server roles in the Single Server, Single Management Group scenario (gateway and management server roles are excluded); otherwise, it is most commonly deployed with the Reporting database or in a stand-alone configuration for performance purposes.

Yes, n+1 cluster

SQL Reporting Services database

Dedicated SQL Server Reporting Services instance; not on a domain controller. This role can be co-deployed with all server roles in the Single Server, Single Management Group scenario (Gateway and management server roles are excluded); otherwise, it is most commonly deployed with the Data Warehouse database or in a stand-alone configuration for performance purposes.

No

root management server (RMS)

Not compatible with management server or gateway server role. This role is co-deployed with all server roles in the Single Server, Single Management Group scenario (gateway and management server roles are excluded); otherwise, it is most commonly deployed into a n+1 active-passive-passive cluster with no other roles on the cluster.

Yes, n+1 cluster, no other roles on the cluster

management server (MS)

Not compatible with Root management server. This role is not deployed in the Single Server, Single management server scenario. It is most commonly deployed in a stand-alone configuration,

No

Administrator console

Windows Server 2003, Windows XP, Windows Vista, Windows Server 2008.

N/A

ACS collector

This role is co-deployed with all other server roles in the Single Server, Single Management Group scenario (gateway and management server roles are excluded); otherwise, it must be co-deployed with the management server role. It can be combined with gateway server and audit database.

No

gateway server

Can be co-deployed with ACS collector only, cannot be combined with management server; must be a domain member.

No

Web console server

Windows Server 2003, Windows Server 2008.

N/A

Agent

Automatically deployed to root management server and management server in a management group. Deployable to all other roles in management group.

N/A

Note

For more information about SQL Reporting Services database installed on a cluster, see http://go.microsoft.com/fwlink/?LinkId=96623.

See Also

Other Resources

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