SCOM 2007 R2 obsolete performance rules shown in performance view
I'm monitoring a few servers that were reloaded from Win2000 to Win2008 quite awhile ago and noticed that there are duplicate performance rules showing up when I right-click on one of the servers in a state view and open a performance view. Performance collection rules for both Win2000 and Win2008 are listed, although there is only data for the Win2008 rules. Has anyone else seen this before, or is this unique to my environment? Thanks, Dave
November 18th, 2011 2:26pm
when you say reloaded do you mean the OS was upgraded?Scott Moss MVP (Operations Manager) | President - System Center Virtual Users Group | Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you!
November 19th, 2011 11:53am
we have this permanently for custom rules. for instance, when we change CounterName for perfromance collection rule, SCOM creates new Counter, leaving old names forever in Database. for such cases we created custom grooming procedure. of course, unsupported by Microsoft.
November 20th, 2011 4:35pm
Hi Dave, Could you please let us know how you reloaded the servers from Windows Server 2000 to Windows Server 2008? I suspect there was some information from the old agent left, please try the following methods and see if it works: OpsMgr 2007 SP1 – Banish the Undead. How to remove “Not Monitored” dead agents. http://blogs.technet.com/b/daviddixon/archive/2009/05/14/opsmgr-2007-sp1-banish-the-undead-how-to-remove-not-monitored-dead-agents.aspx Remove-DisabledMonitoringObject http://blogs.technet.com/b/jonathanalmquist/archive/2008/09/14/remove-disabledmonitoringobject.aspx Meanwhile, please update the corresponding Management Pack if there is a new version. If the issue persists, please check the Event Log on the management server; if there are any related errors, please let us know the details. Hope this helps. Leon Liu - Technical Lead
November 22nd, 2011 2:38am
we have this permanently for custom rules. for instance, when we change CounterName for perfromance collection rule, SCOM creates new Counter, leaving old names forever in Database. for such cases we created custom grooming procedure. of course, unsupported by Microsoft. In any Management Packs where we use a property of a class to populate the Instance Name and that property isn't discovered yet this occurs. We have duplicated performance instances shown. One without the Instance Name populated, and then after the property of the class is discovered the new performance instance is shown. Pavel, did you find a fix for this?
August 1st, 2012 10:56am