Changes in This Update

  • Article

Applies To: Operations Manager 2007, Windows Server 2012

This section describes the changes made to the Active Directory Management Pack.

  • March 2012 Update

  • September 2011 Update

  • October 2009 Update

  • November 2008 Update

March 2012 Update

The March 2012 update does not include new functionality, but it does include several fixes requested by customers. The following table lists the updates and which operating system monitoring rules are impacted.

Note

The guide was also updated in October 2012 to reflect that it applies to running ADMP on Windows Server 2012 domain controllers.

Fix Operating system monitoring rules impacted

Corrected some Publisher names (for example, changed from PublisherName=KDC to PublisherName=Microsoft-Windows-Kerberos-Key-Distribution-Center).

Windows Server 2008 and later

Updated several important rules to generate Alerts and not only go to the Event Viewer.

Windows Server 2008 and later

Removed unnecessary check for Event Source Name for all NTDS rules (for example, removed EventSourceName=”NTDS General”).

Windows Server 2003 and later

Corrected event parameter validation.

Windows Server 2003 and later

Updated some queries to search for correct event IDs.

Windows Server 2003 and later

Fixed spelling errors.

Windows Server 2003 and later

Added missing descriptions to several rules.

Windows Server 2003 and later

Fixed several problems with Health Monitoring scripts.

Windows Server 2003 and later

Removed user name checks from Userenv rules.

Windows Server 2003

September 2011 Update

The September 2011 update includes fixes to problems and deprecation of certain rules, monitors, and discoveries.

Fixes

This table lists the fixes to problems reported by users and other architectural fixes and how they can affect your environment.

Fix Impact

Active Directory databases larger than 4 GB reported incorrectly

This prevents incorrect logging of Event ID 333 with the following text:

AD Database and Log : Free space (KB) on drive  is lower than the required reserved space for AD Log file. It should be at least 200000 KBytes.

20% of the alerts are not triggered due to wrong event ID mapping

This prevents several event-driven rules from breaking due to using the old event sources from Windows Server 2003 in their event rules rather than the new event sources for Windows Server 2008 and Windows Server 2008 R2.

Performance data is not collected due to wrong event ID mapping

Prevents the following alert caused by rules that fail to collect performance data on domain controllers that run Windows Server 2008:

In PerfDataSource, could not find counter NTDS, DRA Inbound Bytes Not Compressed (Within Site)/sec, in Snapshot. Unable to submit Performance value. Module will not be unloaded.

Performance counter selected by default is wrong

Fixes problems that prevented Replication Latency Performance data from appearing.

Time skew alert is not triggered due to script defect

Matches the names of arguments in a function in AD_Time_Skew.vbs to variables passed to LogScriptEvent to enable events related to time skew to be created as designed.

Operation master monitor is broken due to script defect

Corrected a variable name in the Discovery script so the DNS Naming Master property is discovered correctly for proper Operations Master Consistency monitoring.

Frequent operation master alert description misspelled

Corrected misspelling of “inconsistent.”

Discovery interval for client perspectives set to larger values

Discovery interval for client perspectives had an interval set too high, which could cause performance issues that could block installation of an updated management pack.

Discovery scheduler class is not used on several discoveries

Some workflows use System.Scheduler instead of System.Discovery.Scheduler.

Views target a custom AD DS MP class instead of System.Entity

This could have blocked installation of an updated management pack.

Reports target a custom AD DS MP class instead of System.Entity

This could have blocked installation of an updated management pack.

Some discovery targets will not change Properties

This problem could cause bad performance for organizations with many domain controllers.

Deprecated rules, monitors, and discoveries

The following rules, monitors, and discoveries were deprecated in version 6.0.7065.1.

For Windows 2000 Server:

  • AD Enterprise License Discovery (deprecated)

For Windows Server 2003:

  • License Discovery for Microsoft Windows Server AD (Deprecated)

For Windows Server 2008:

  • License Discovery for Microsoft Windows Server AD (Deprecated)

The following common monitors were replaced with a separate rule for Windows Server 2003 and Windows Server 2008 instead of sharing a common monitor:

  • AD DC Performance Collection - Metric NTDS DRA Inbound Bytes Compressed (Between Sites, Before Compression)/sec (Deprecated)

  • AD DC Performance Collection - Metric NTDS DRA Inbound Bytes Compressed (Between Sites, After Compression)/sec (Deprecated)

  • AD DC Performance Collection - Metric NTDS DRA Inbound Bytes Not Compressed (Within Site)/sec (Deprecated)

  • AD DC Performance Collection - Metric NTDS DRA Inbound Bytes Total/sec (Deprecated)

  • AD DC Performance Collection - Metric NTDS DRA Inbound Bytes Compressed (Between Sites, After Compression)/sec (Deprecated)

  • AD DC Performance Collection - Metric NTDS DRA Outbound Bytes Compressed (Between Sites, After Compression)/sec (Deprecated)

  • AD DC Performance Collection - Metric NTDS DRA Outbound Bytes Compressed (Between Sites, Before Compression)/sec (Deprecated)

  • AD DC Performance Collection - Metric NTDS DRA Outbound Bytes Not Compressed (Within Site)/sec (Deprecated)

  • AD DC Performance Collection - Metric NTDS RRA Outbound Bytes Total/Sec (Deprecated)

Remove Windows 2000 MPs

The Windows 2000 Server monitoring management pack has been removed as of this release of the Active Directory Management Pack. Windows 2000 Server is no longer a supported product.

Increase Script Time-Outs

Many scripts in the Active Directory Management Pack have time-out values that may cause the script to be terminated prematurely by the agent. If frequent time-outs are occurring in your environment, consider increasing the amount of time that the script is allowed to execute.

Missing Roll-Ups

The following monitors do not roll up to a standard aggregate monitor, and thus will not be included in the overall health status of the server:

  1. Microsoft Windows Server AD 2003 Monitoring Management Pack:

    * AD Replication Monitoring

* All of the replication partners failed to replicate.

  2. Microsoft Windows Server AD 2008 Monitoring Management Pack:

    * AD Replication Monitoring

* All of the replication partners failed to replicate.

Mismatched Alert Severity

Alerts raised by the AD Client Serverless Bind Monitor do not match the state of the monitor when an error condition is detected. The monitor will raise an alert with a severity of Error, while the monitor will be in the Warning state.

Undocumented Overrides

Microsoft.Windows.Server.AD.DomainController.DRAIntersiteOutBytes.Collection.Override.RODCGroup
Microsoft.Windows.Server.AD.DomainController.DRAOutboundBytesComp.Collection.Override.RODCGroup
Microsoft.Windows.Server.AD.DomainController.DRAOutboundBytesNotComp.Collection.Override.RODCGroup
Microsoft.Windows.Server.AD.DomainController.DRAOutboundBytesTotal.Collection.Override.RODCGroup

These overrides disabled the following replication performance counter rules for Windows Server 2008 and Windows Server 2008 R2 Read-Only Domain Controllers:

AD 2008 DC Performance Collection - Metric NTDS DRA Outbound Bytes Compressed (Between Sites, After Compression)/sec

AD 2008 DC Performance Collection - Metric NTDS DRA Outbound Bytes Compressed (Between Sites, Before Compression)/sec

AD 2008 DC Performance Collection - Metric NTDS DRA Outbound Bytes Not Compressed (Within Site)/sec

AD 2008 DC Performance Collection - Metric NTDS RRA Outbound Bytes Total/Sec

Scripts with Syntax Errors

The ADClientPerspective.vbs script used by the AD Client Monitoring Discovery contains a script error and will not execute when run.

October 2009 Update

The October 2009 revision of the Active Directory Management Pack includes the following additions:

  • Support for monitoring Windows Server® 2008 R2 server operating systems as well as Windows® 7 client operating systems.

  • Support for monitoring the Active Directory Web Service (ADWS) in Windows Server 2008 R2 as well as the Active Directory Management Gateway Service in Windows Server 2008 and Windows Server 2003.

November 2008 Update

The November 2008 update of the Active Directory Management Pack includes the following scenario improvements.

Scenario Improvement

Description

Windows Server 2008 discovery for writeable domain controllers and read-only domain controllers (RODCs)

Discovery of the following objects for a Windows Server 2008 domain controller: domains, forests, sites, site links, RODC, primary domain controller (PDC) emulator, relative ID (RID) master and infrastructure master and connection objects.

Windows Server 2008 replication monitoring—multiple service level agreements (SLAs), enhanced workflow, and new essential services (File Replication Service (FRS), Distributed File System Replication (DFSR), and NTDS).

The multiple SLA function is performed by creating a group and adding computers to it and then setting an override for the replication monitoring script that is pregroup.

Multiple forest topology discovery and views

Active Directory Multiple Forests Topology Discovery is a new feature in this management pack that was added to provide feature parity with the Active Directory Management Pack for Microsoft Operations Manager (MOM) 2005 with Service Pack 1 (SP1). In both Active Directory management packs for Operations Manager 2005 (SP1) and Operations Manager 2007 (SP1), to discover other forests, a trust relationship is required between the forest hosting the Operations Manager Root Management Server (RMS) and other forests. Forests that have a two-way transitive trust with the RMS forest will be discovered. The following objects will be created and displayed in the Topology views: Forest, Domain, Site, Site Link, and Replication Connection.

New essential services roll-up models for Windows Server 2008 and Windows Server 2003

The Essential Service health state roll-up was redesigned in Active Directory Management Pack for Operations Manager 2007 SP1 for two reasons:

  • To add an Overall Essential Service state as the parent health state for all the Essential Services and to present a correct hierarchical entity relationship for DC Availability, Overall Essential Services, and individual Essential Services.

  • To accurately reflect the dependencies for four essential services: SysVol, Distributed File System (DFS), NetLogon, and DCLocator.

Implement new reports

Domain Changes and Synchronous Access Mode (SAM) Account Changes for Windows Server 2000, Windows Server 2003, and Windows Server 2008.