Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

OpsMgr: MP Update: Active Directory MP version 6.0.7670.0 ships

OpsMgr: MP Update: Active Directory MP version 6.0.7670.0 ships

  • Comments 7
  • Likes

 

Get it at:   http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=21357

 

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.

Comments
  • Hi Kevin.

    do you know what exactly was changed for

    >>Active Directory databases larger than 4 GB reported incorrectly<<<

    as 4GB is limit for uint32. I wonder what was changed to pass this limit?  

  • Pavel - are you asking me on the AD side - or on the script side that collects the value?

  • I haven't checked MP yet. Likely mentioned collection rule relies on values from AD helper COM object. I do not see any binaries for ADHelper published.

    i'm asking in regards to this forum thread:

    social.technet.microsoft.com/.../9b76d8cf-08fd-4220-9c86-6e5bdc361c86

    as the tread discovered limitation in ADHelper object which reports incorrectly AD logical disk size for disks >2TB.(upper limit for int32).

  • Hi Kevin,

    MS had provided us with the Active Directory Server 2008 (Monitoring) -Addendum MP (v 6.0.7065.0)  around May -June this year , which was supposed to fix issues with the orginal MP. Do we need to delete this MP, after we install v 6.0.7067.0 to avoid duplicate Alerts?

  • @M.Mathew -

    MS didnt provide that MP - that addendum MP was published by Jimmy Harper in the blog post I linked above, as a workaround for the community as soon as this issue was discovered.

    Yes - you should remove that MP to avoid duplicate alerts, if you are running it, as the updated ADMP resolves this issue.  I would probably run a test of some of the rules, just to be sure, using:  blogs.technet.com/.../how-to-test-fire-any-windows-event-on-any-server-from-any-application.aspx

  • Hi Kevin.

    There seem to be a couple of errors / catch's with the new version of the AD MP and client monitoring.  If you set the "ping threshold" greater than 60 because your client is on the other side of a wan then you get errors with the LDAPPingTimeout as they both seem to use the same override.  So you can either have sites that put up errors each time they go over 60 ms ping time or put up an alert saying that there is an error in the script parameters.

    2nd one that i have noticed is the "AD Serverless bind is not possible, or the response is too slow" seems to come up for each site which is being covered by a RODC.  So for each site that has a RODC we seem to be seeing this alert.  

  • Hi Kevin,

    On my DC with 2008 R2 I get an alert "Could not determine the FSMO role holder" on the neighbouring 2003 DC. It also gave a script error from "AD Replication Partner Op Master Consistency AD Client Side Script Based Test Failed to Complete".  The script checks the FSMO roles remotely on the neighbouring 2003 DC. Answer in SCOM is: The error returned was 'The server is not operational.'(0x80040E37). Though the server is fully operational.

    When I fire the corresponding AD_Replication_Partner_Op_Master_Consistency.vbs script with the remote DC as first argument and a 1 or 0 as second argument I get value GOOD.

    Is this a fault in the MP?

    Regards,

    Mark

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs