This is the first MP update for Active directory we have seen in two years. This MP update contains mostly fixes to the top reported customer issues in the MP’s.
As the ADMP is a very large and complex MP with a lot of moving parts, I recommend you consider giving sufficient time and attention in testing this MP in your lab, test, and dev environments before migration into production.
From the ADMP guide:
Fixes to problems reported by customers:
- Active Directory databases larger than 4 GB reported incorrectly.
- 20% of the alerts are not triggered due to wrong event ID mapping.
- Performance data is not collected due to wrong event ID mapping.
- Performance counter selected by default is wrong.
- Time skew alert is not triggered due to script defect.
- Operation master monitor is broken due to script defect.
- Frequent operation master alert description misspelled.
Fixes to architectural issues to facilitate future System Center Operations Manager releases:
- Discovery interval for client perspectives set to larger values.
- Discovery scheduler class is used on several discoveries.
- Views target a custom AD DS MP class instead of System.Entity.
- Reports target a custom AD DS MP class instead of System.Entity.
- Some discovery targets will not change Properties.
If you were running a custom override addendum MP, like the one posted at http://blogs.technet.com/b/jimmyharper/archive/2010/08/27/admp-for-windows-server-2008-alerts-not-generated-for-some-rules.aspx then you will not need this anymore, as the MP has been updated to resolve this key issue.
I ran a DIFF on the majority of the files – and I didn’t see anything sticking out that wasn’t covered above. There is a new or changed report for replication bandwidth, but that’s about all I noticed.