Small Bug Fix in OpsMgr Self Maintenance MP V2.5.0.0

Written by Tao Yang

Last night, someone left a comment on the my post for the OpsMgr Self Maintenance MP V2.5.0.0 and advised a configuration in the Data Warehouse staging tables row count performance collection rules is causing issues with the Exchange Correlation service – which is a part of the Exchange MP. This issue was previously identified for other MPs: https://social.technet.microsoft.com/Forums/en-US/f724545d-90a3-42e6-950e-72e14ac0bd9d/exchange-correlation-service-cannot-connect-to-rms?forum=operationsmanagermgmtpacks

In a nutshell, looks like the Exchange Correlation service does not like rules that have category set to “None”.

I would have never picked it up in my environment because I don’t have Exchange in my lab therefore no Exchange MP configured.

Anyways, I have updated the category for these rules in both the Self Maintenance MP as well as the OMS Add-On MP, changed them from “None” to “PerformanceCollection”. I have updated the download from TY Consulting’s website. The current version is now 2.5.0.1. So if you are have already downloaded v.2.5.0.0 and you are using Exchange MP in your environment, you might want to download the updated version again from the same spot HERE.

2 comments on “Small Bug Fix in OpsMgr Self Maintenance MP V2.5.0.0

  1. FYI, the correlation engine is only a component of the Exchange 2010 MP. Exchange 2013 (& 2007) should be fine.

  2. Hi Tao,
    Can you please share the PS script that is behind “OpsMgr 2012 Self Maintenance Detect Manually Closed Monitor Alerts Rule”?
    I’m asking because i had a monitor that was critical for 7+ days whilst there was no active alert. The state was so old that the last state change groomed out. So for some reason the rule did not pick up this one.
    Any idea why? In general it seems to work fine but of course i can’t spit through all hosts and states.
    Thanks!
    Regards
    Tommy

Leave a Reply