Connect management groups in Operations Manager

Connecting management groups in System Center Operations Manager enables the ability to view and interact with data from multiple management groups in a single Operations console. The management group in which the consolidated view is available is called the local management group, and those that contribute their data to the consolidated view are called the connected management groups. They relate to each other in a hierarchical fashion, with connected groups in the bottom tier and the local group in the top tier. The connected groups are in a peer-to-peer relationship with each other. Each connected group has no visibility or interaction with the other connected groups; the visibility is strictly from the local group into the connected group.

Note

Operations Manager doesn't support communication of data between peer management groups. Only the local to connected hierarchy configuration is supported. Multiple tiers, where a management group would be both a local group and a connected group, aren't supported.

When you connect management groups, you aren't deploying any new servers; rather, you're allowing the local management group to have access to the alerts and discovery information that is in a connected management group. In this way, you can view and interact with all the alerts and other monitoring data from multiple management groups in a single Operations console. In addition, you can run tasks on the monitored computers of the connected management groups.

Connecting management groups offers these additional services:

• Consolidated monitoring and alerting for greater than 6,000 agents

• Consolidated monitoring across trust boundaries

Important

Both management groups must be running the same build of Operations Manager. For example, both management groups must be running System Center 2025 - Operations Manager.

In addition to all the communication channels used in the multiple server, single management group configuration, connected management groups require communication between the management servers of the local group and the management servers of the connected group over TCP 5723 and 5724. For a complete list of ports used by Operations Manager, see Configuring a Firewall for Operations Manager.

Connected management groups support all Operations Manager user roles and make use of the Operations Manager Connector Framework to enable bidirectional communication between the connected groups and local groups.

In this procedure, you can create a connection between two management groups. These management groups can be in the same domain, or they can be in trusted domains. You can connect to management groups that are in domains that aren't trusted, but you can't view data from those domains until you add an account from the domain of the local management groups to an Operations Manager role for the connected management group. To do this, a trust must be established between the domains.

Before you start

1. To connect management groups, you must provide the fully qualified domain name (FQDN) of a management server of the connected management group. The management server of the local management group must be able to resolve this FQDN. If the two management groups don't use the same Domain Name System (DNS) service, you must create a secondary DNS zone in the DNS service that the local management group uses. This secondary DNS zone transfers the DNS information from the primary DNS zone of the connected management group. The transferred information is essentially a copy of the DNS information that's available to the management server of the local management group.

2. Add the System Center Data Access service and System Center Management Configuration service account of the connected management groups to the Operations Manager Administrator role for the connected management group, or add it to the domain-based Operations Manager Administrator security group in the connected management group's domain, which has already been added to the Operations Manager Administrator role.

3. Collect the System Center Data Access service and System Center Management Configuration service account credentials from the connected management groups. These credentials are needed when you add the connected management group in the local management group.

4. Identify users in the domain of the local management group that will need access to data from the connected management groups. They must be added to the appropriate Operations Manager roles in the connected management group.

Connect management groups

1. Sign in to the computer with an account that's a member of the Operations Manager Administrators user role.

2. In the Operations console that's connected to the destination management group, select Administration.

3. In the Administration workspace, right-click Connected Management Groups, and select Add Management Group.

4. In the Add Management Group dialog, do the following:

   1. Enter the Management Group name of the management group to be connected.

   2. Enter the fully qualified domain name (FQDN) of a Management Server in the desired management group to be connected.

   3. Specify the account that will be used for the initial connection to the connected management group, either by leaving Use SDK service account selected or selecting Other user account and entering in the User name, Password, and Domain. The account must be a member of the Operations Manager Administrators role for the connected management group.

5. Select Add.

Grant access to Connected Management Groups

1. Identify users in the local management group that need access to the connected management groups.

2. Add those users as members to the appropriate user role in the connected management groups.

   Note

   If local and connected management groups aren't in the same domain and there's no trust relationship between the two domains, you'll have to create accounts in the connected management group domain for the users in the local management group domain to use.

3. In the Operations console for the local management group, in the Administration view, expand Security, and select User Roles.

4. In the right pane, right-click the user role to which you want to grant connected management group access, and select Properties.

5. On the Group Scope tab, select the connected management groups to which you want to grant access to this user role, and select OK. A user with both permission and access to at least one connected management group will see the Show Connected Alerts button in the toolbar of any Alert view in the Monitoring space.

6. A Log On dialog appears and prompts the user for credentials (to sign in to the connected management groups). Enter the credentials, and select OK. Alerts appear from all connected management groups for which you've access and permission. You can run tasks in the managed computers of the connected management groups.

Next steps

• To stop monitoring of a computer, group of computers or monitored object temporarily during planned maintenance using a schedule, or to stop monitoring while troubleshooting an issue, see How to Suspend Monitoring Temporarily by Using Maintenance Mode.

• Groups help categorize, classify, or arrange one or more monitored objects to manage targeting of visualized data, overrides, reports, and more. To learn how to create groups and common uses for groups, see Creating and Managing Groups.

• Operations Manager extends the PowerShell command-line environment and task-based scripting technology to automate most Operations Manager administrative tasks. See Using Operations Manager Shell.

• To learn how to launch common tools or commands from the Operations Manager console to help reduce your time investigating and diagnosing issues, see Running Tasks in Operations Manager.