Shockwave’s Blog

We have been using SCOM 2007 R2 for some time now, in fact we were the first organisation in the UK to implement the product as part of a Microsoft Rapid Deployment Programme (RDP). Since then I have been one of the biggest advocates of the product, however, one bug that I did come across relates to the description of one of the reports – Performance History (% Processor Time) which is part of the Windows Server 2003 Operating System Management Pack.

The description of this report informs you that:

“The report finds data if the objects supplied are of type: Windows Server 2003 Processor”

This is untrue, the object you actually need to monitor is ‘Windows Server Operating System’.

To filter your search results to include this class, you need to do the following:

1. Double click on the Performance History (% Processor Time) report from the Windows Server 2003 Operating System Management Pack in the reporting pane of your SCOM console and click on the “Add Object” button:

2. Select “Options” from the second window that pops up as shown below:

3. Select “Add” from the Options dialogue box:

4.Under class name choose “Contains”, enter “Windows Operating System” and click “Search”. Add the resulting class by selecting it and clicking “Add” then Okay twice.

5. You should find yourself back at the original search screen from step 2. If you click the “Search” button this should bring back all instances and you can select the servers you want to monitor from the “Path” column as shown below:

Once you’ve added you servers you should be confronted with the report you wanted. I haven’t used many of the reports in the console but I’m guessing there may be others that suffer similar issues. I need to take some time out to read the details of what is fixed in Cumulative Update 1 or the latest version of the Management Pack, we’re currently using 6.0.6321.5 as this may be resolved. If you know, feel free to leave a comment!