Shockwave’s Blog

Just another geeky blog…
  • Home
  • About

SCOM 2007 R2 Performance History (% Processor Time) Report

Rob | January 29, 2010

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:

SCOM Performance Report 1

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

SCOM Performance Report 2

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

SCOM Performance Report 3

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.

SCOM Performance Report 4

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:

SCOM Performance Report 5

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!

Categories
Tech
Tags
How-To, Monitoring, SCOM
Comments rss
Comments rss
Trackback
Trackback

« Managing Non Domain Integrated DMZ Servers in SCOM 2007 R2 Active Directory will not start! Aaaaaargh! »

Leave a Reply

Click here to cancel reply.

Blogroll

  • Ops Man Jam
  • Petri
  • Server Chronicle
  • System Centre Forum

Tags

AD BES ByteNight Charity Exchange FundRaising How-To HP ITIL Mac Mail Management Monitoring Openview OSX Patching Photography Powershell Problem Problem Management Reboot Restart SCOM SCW Security Server SIM Snow Leopard SysAdmin Virtualisation Windows 7 Work WSUS
rss Comments rss valid xhtml 1.1 design by jide powered by Wordpress get firefox