Multiple Server, Single Management Group Scenario

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

This type of management group installation will form the foundation of 99 percent of Operations Manager deployments. It allows for the distribution of server roles and services across multiple servers to allow for scalability and for the use of Windows failover clustering and Operations Manager-specific failover configurations. It can include all Operations Manager server roles and supports the monitoring of devices across trust boundaries through the use of the gateway server.

The following diagram presents one possible option for the multiple server, single management group topology.

This configuration supports all Operations Manager features:

• Monitoring and alerting, targeted for between 500 and 6,000 agents

• Monitoring across trust boundaries

• Reporting

• Audit collection

• Agentless exception management

• Agent failover between management servers

• Gateway failover between management servers

• Clustering high availability for database and root management server roles

This configuration supports all Operations Manager server roles:

• Audit Collection Services (ACS) collector

• ACS database

• ACS forwarder (on agent-managed devices)

• Gateway server

• Management server

• Operational database

• Operations console

• SQL Server 2005 or SQL Server 2008 Reporting database

• Reporting data warehouse database

• Root management server

• Web console server

Single management group configurations do not support partitioning. Partitioning is the separation of management group services across multiple management groups. In Operations Manager 2007, you may want to create multiple management groups for the following reasons.

Operations Manager 2007 management groups support only one installed language. If the overall IT environment that you need to monitor has more than one installed language, a separate management group will be needed per language.

Even the largest multiple server, single management group implementation will not be appropriate in every instance. This will lead you to implement multiple management groups, which will split your monitoring and alerting data between management groups. To provide a single, consolidated view of your environment, data from multiple management groups can be consolidated and viewed in another management group. For more information, see the Operations Manager 2007 Design Guide at https://go.microsoft.com/fwlink/?LinkId=104550 .

You may need to have separate groups as needed according to function, such as preproduction for testing management packs and new servers, and production for monitoring daily business processes.

Your company may have other administrative, security, or business needs that require complete separation of monitoring data and administrative teams, which will mandate additional management groups.

Multiple server, single management groups are most commonly used to monitor very large preproduction environments and large production environments that

• Span trust boundaries between domains and workgroups.

• Have multiple network environments segmented by firewalls.

• Have a need for high availability.

• Must have a scalable monitoring solution.

This configuration supports full distribution of server roles among servers in the management group as well as monitoring of devices across network boundaries, resulting in a longer list of ports that need to be available for communications. For more information, see Operations Manager 2007 Supported Configurations (https://go.microsoft.com/fwlink/?LinkId=86539).