There have been a couple good articles briefly covering this topic…. you might have read them.  I will reference some below.  Config churn is basically, when your RMS is in an almost never-ending loop of generating config.  This can be caused by “less than optimized” management packs,...

Updated 11/16/09 – I think this is pretty much resolve now – read below:   I have seen this at several customer sites, and even in my own lab.  You might find the following alerts (below) stemming from the DNS MP. To start, I would recommend the resolutions in my previous post:  Getting...

This is a problem in the 6.0.6480.0 version of the DNS MP. You will likely see a lot of DNS Resolution Time alerts popping into your console – then disappearing. This is because these alerts are generated by a monitor, which is frequently changing state.  These alerts get auto-resolved when the...

This is a problem in the 6.0.6480.0 version of the DNS MP. This MP includes a monitor to inspect the DNS server’s ability to resolve external domains. The problem is – that the moniotr defaults to inspecting “www.microsoft.com” when it should use a base domain, like “microsoft.com”.   You will find...