Home > OpsMgr > Does my Operations manager environment healthy ?

Does my Operations manager environment healthy ?

Update – 17/05/2011 – I Changed the query to show only agents that aren’t in maintenance mode.

After several OpsMgr deployments at different costumers I discovered that most of us concerned about OpsMgr Management server health and/or Database health, but what about agent health? How can we tell if all our agents report to their managements servers?

In one of my previous posts I wrote about WMI and agent health , these hotfixes are not for operations manager , those are bugs that discovered in the operating system components that monitoring solution use, like WMI. So for agent reliability it’s important to keep the OS updated.

Sometimes agents seems to be healthy, Operations manager MP point that, but when we starts to investigate, we can see that some gents did not report any new alerts for long time. Operations manager event log at the client side seems to be healthy and there are no errors. But if we will look closer we can see that there are several events rapidly reoccurring (6022, 21025).

Since OpsMgr gives us the ability to monitor agents availability, performance and configuration we need to find a way to discover if agents really writing data to OperationsManager DB. I decided to search for the right approach.

Daniele Grandini wrote two SQL queries that check the OperationsManager database for agents that did not collected event or performance data in the last 4 hours. I decided to monitor only the performance data collection since we do use the HealthService and MonitoringHostCPU usage. If you disabled these rules the query can be changed to target any monitoring class id (like operating system).

Thanks to a colleague of mine, Evyatar Nezer, we re-write the query to create a scheduled report using operations manager reporting services. the report show us all the agents that are not in good health.


to fix this issues I found that we need to take this actions (client side only):

1. restart the HealthService .

2. rebuild the perf registry strings and info using LODCTR.EXE /R (the command is case sensitive!!!) – this step should be done with extra care!

Here are the steps taken to create the scheduled report.

First we need to take note about the SQL server that hosts the OperationsManager DB. This could be done using REGEDIT.EXE against the RMS as shown below.


The next step uses Microsoft Visual Studio report builder. Open the application and under new project select the following:


Enter the OpsMgr database server name and choose the OperationsManager database.




Paste the query (click here to download) in the next screen and continue as describe in the next screen shots.







And finally the report we are looking for, now its time to add the report to the operations manager reporting pane.


Click on File (there is no need to save the file first) , Open -> File as shown


Right click on the RDL file in Open File dialog and click copy


Now go to the reporting services we site, create a new folder and name it “MYCOMP Custom Reports”


Enter the folder that you created in the previous step and click Upload File


Give the new report a name and click the browse button


Choose the RDL file that you copied earlier and click open


And that’s it. We have a report that show us all the agents that missed to collect performance data in the last 4 hours.


Categories: OpsMgr Tags: , ,
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: