Updated & Improved - Extended Active Directory Management Pack
Updated & Improved - Extended Active Directory Management Pack
Feed: Matt Goedtel on Operations Management
Posted on: Sunday, January 25, 2009 10:19 PM
Author: mgoedtel
Subject: Updated & Improved - Extended Active Directory Management Pack
This management pack has been revised based on the updated Microsoft Active Directory management pack, version 6.0.6452.0, which has some rules that were in the first version of my custom AD management pack.
This management pack augments the existing Active Directory management pack by monitoring the following specific components and subsystems that Active Directory relies on, which are not captured in the current version:
· Monitor the Windows Time Service (W32Time) for time synchronization issues with authoritative time source.
· Monitor for clients not authenticating against a local domain controller, indicating site boundaries are not properly defined or scoped.
· Monitor for expensive or inefficient LDAP queries performed against a DC
· Monitor for FRS related events that affect the health and availability of the SYSVOL shared directory and its replication on a domain controller.
· Monitor for specific performance characteristics of a domain controller with respect to Free System Page Table Entries and Database Name Cache hit rate.
· Includes two Tasks to remotely shutdown and reboot a domain controller from within the Operations Console.
If you used the Extended Active Directory management pack (6.0.6246.0), delete it from the management group before importing this one, as it won't upgrade to this new version. The zip file contains the sealed MP and the deployment guide for your review.
All future versions will be upgradeable from now on.
I am currently working on the next version which will verify that the AD Helper Object (OOMADS) is installed, is the latest version, and is running on the domain controller, as this can impact certain workflows from running successfully on a DC. This is something that we do not monitor by default today, and the only way you know there is a problem is if a script fails and the error refers to an "ActiveX component cannot create the object."
View article...
Enclosures:
3191369.ashx (121 KB)
http://blogs.technet.com/mgoedtel/attachment/3191369.ashx
Published with BlogMailr