Here's a great FYI sent in by Lenny Wile, one of our top OpsMgr guru's from the Las Colinas, Texas office:
Issue: When viewing the Computer views of the Monitoring pane in the Operations Manager 2007 Operations Console, the Root Management Server (RMS) displays in a gray state, which is indicative of a not monitored condition. The following events may also be logged in the System Center Operations Manager 2007 event log:
Event Type: Error Event Source: HealthService Event ID: 5300 Description: Local health service is not healthy. Alert flow is stalled with pending acknowledgement.
Event Type: Error Event Source: HealthService Event Category: Health Service Event ID: 5300 Description: Local health service is not healthy. Entity state change flow is stalled with pending acknowledgement.
Cause: This issue can occur if the SQL Server hosting the OperationsManager database has been unavailable for an extended period of time, typically more than 15 minutes. When this occurs the Root Health Service may be unable to completely re-establish SQL Server connectivity when SQL Server becomes available. This can be caused by the SQL Server service being stopped, or the SQL Server being unavailable to the Root Health Service.
Resolution: Restart the Root Management Server’s Root Health Service (OpsMgr Health Service) to allow the Root Management Server to go back to a monitored state.
J.C. Hornbeck | Manageability Knowledge Engineer
PingBack from http://ianblythmanagement.wordpress.com/2008/08/29/rms-and-time/
Source: SMS&MOM J.C. Hornbeck published an article from Lenny Wile on the Health of the Root Management
We have the same issue, but bouncing the health service doesn't help....
I also notice this issue if we have issue with connectivity to Data Warehouse DB. Restarting the RHS will only help for some moments and RMS will grayed out soon.