Need help sorting out what went wrong with WMI and Scripts in the Console?

After implementing the Ops Mgr 2007 you get to the point when adding MPs, upgrading MPs and other changes like upgrading to SP1 gives you some noise in the alert views. Our Ops Mgr 2007 Operators doesn´t like the noise and I think they are in good company. Does anyone like it? Anyway I have done some tweaking with the Console to get the Operation Manager noise, "Script or Executable Failed to run" and "WMI Probe Module Failed Execution" out of the alert log. I have made overrides to these 2 rules and changed the severity to "0" (from "1" Warning). With this value the alert comes as a Information alert instead of warning. To even more easy up the Active Alert log I have removed the Information alert from the default "Active Alerts" view and then created a new "Active Information Alerts" view were all the alerts with severity "0" = Information Alerts ends up.

Now the Operators just looks into the Active Alerts view and are told to not touch the Informational Alerts. By sorting the Alerts in this new "Active Informational Alerts" view by repeat count you can se witch rules on witch systems have the most noise problems? And looking at the end of this sorting you can check for alerts with no repeat count and Age 5 days or so and just close them as "bad luck" alerts. With this method you can keep your Operators in a good mood and it give the Ops Admin a good tool to fix (or report to the creator of the MP) bad scripting or miss configured servers. I would like in future release to have a new Severity for this kind of alerts. The Ops Admin Severity alerts that if they make sense (not all do!) it makes sense just to the Ops Mgr Admin and not the regular Operators.

Good luck hunting down the "Script or Executable Failed to run" backlog :)