Microsoft Knowledge Base Email Alertz

Health Service problems occur when an active Root Management Server is targeted as an agent from other Management Groups

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 956471 - Last Review: September 16, 2008 - Revision: 1.1

Health Service problems occur when an active Root Management Server is targeted as an agent from other Management Groups

SYMPTOMS

When an active Root Management Server (RMS) is targeted as an agent from other Management Groups, problems can arise because of stress on the local Health Service and Health Service Extensible Storage Engine (ESE) data store.

RESOLUTION

A Root Management Server already has built in health monitoring that occurs within its configured Management Group. To see whether the Root Management Server is targeted as an agent from other disconnected Management Groups, check the following registry subkeys.

Registry subkey 1
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups


Note This is an agent registry subkey, and this subkey does not ordinarily exist on the RMS.
Registry subkey 2
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\Management Groups\<management group name>


Note This subkey ordinarily reflects only the Management Group of the RMS itself if there are multiple entries for Management Groups. This subkey reflects that a disconnected Management Group agent is installed.
Immediate problems can occur if an agent is accidentally installed on a Root Management Server and that agent is targeted at the Management Group that the RMS is configured to manage. The following is a short list of known problems with this configuration:
  • Alerts do not flow.
  • Management servers are unavailable in the console.
  • Heartbeat failures occur with error code 20022.
  • All monitored agents cannot update their configuration.

APPLIES TO
  • Microsoft System Center Operations Manager 2007
  • Microsoft System Center Operations Manager 2007 Service Pack 1
  • Microsoft System Center Operations Manager 2007 R2
Keywords: 
kbhowto kbexpertiseinter kbinfo KB956471
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate