Monitoring Operations Manager from a Second Management Group
Updated: May 13, 2016
Applies To: System Center 2012 R2 Operations Manager, System Center 2012 - Operations Manager, System Center 2012 SP1 - Operations Manager
Businesses using System Center 2012 – Operations Manager in multiple management groups sometimes want to monitor one management group from another management group. This topic provides some tips for monitoring one management group (management group A) from a second management group (management group B).
You can install an agent on management servers in management group A from management group B. If you install the agent manually, configure the agent to report to a management server in management group B.
Disable Active Directory integration for the agent you install on the management server in management group A.
To upgrade the management server in management group A, you must remove the management group B agent first.
After the agent is installed, ensure that you do not configure the agent to also report to management group A (“multihome” the agent).
Ensure that the Run As accounts for the Default Action Account and Privileged Monitoring Account profiles for the management server in management group B are using credentials that can remotely authenticate and that have sufficient permissions on the management servers in management group A.
Operations Manager Monitoring Scenarios
Integrating Active Directory and Operations Manager
Connecting Operations Manager With Other Management Systems
Collecting Security Events Using Audit Collection Services in Operations Manager
Monitoring UNIX and Linux Computers by Using Operations Manager
Monitoring .NET Applications
Monitoring Service Level Objectives by Using Operations Manager
Monitoring Networks by Using Operations Manager
Monitoring Clusters by Using Operations Manager
Client Monitoring Using Agentless Exception Monitoring in Operations Manager
Monitoring Across Untrusted Boundaries in Operations Manager
Agentless Monitoring in Operations Manager