Chat now with support
Chat with Support

Active Administrator 8.4 - User Guide

Active Administrator Overview Certificates Security & Delegation Azure Active Directory  Active Directory Health
Switching to Active Directory Health Using the Active Directory Health landing page Installing Active Directory Health Analyzer agents Using the Active Directory Health Analyzer agent configuration utility Excluding domain controllers Managing the Remediation Library Analyzing Active Directory health Analyzing Azure Active Directory Managing Active Directory Health Analyzer alerts Managing alert notifications Pushing alerts to System Center Operations Manager and SNMP managers Managing monitored domain controllers Managing data collectors Active Directory Health Templates Managing Active Directory Health Analyzer agents Using the Troubleshooter Recovering Active Directory Health data
Auditing & Alerting Group Policy Active Directory Recovery Active Directory Infrastructure DC Management DNS Management Configuration
Using the Configuration landing page Managing tasks Defining role-based access Setting email server options Configuring SCOM and SNMP Settings Configuring Azure Active Directory Setting notification options Setting Active Template options Setting agent installation options Setting recovery options Setting GPO history options Setting certificate configuration Setting service monitoring policy Managing archive databases Migrating data to another database Setting a preferred domain controller Setting up workstation logon auditing Managing configuration settings Setting user options Managing the Active Directory server
Diagnostic Console Alerts Appendix
Domain controller alerts
Active Directory Certificate Services service is not running Active Directory Domain Services is not running Active Directory Web Services service is not running Consecutive replication failures DC cache hits DC DIT disk space DC DIT log file disk space DC LDAP load DC LDAP response too slow DC Memory Usage DC properties dropped DC RID pool low DC SMB connections DC SYSVOL disk space DC time sync lost Detected NO_CLIENT_SITE record DFS Replication service not running DFS service is not running DFSR conflict area disk space DFSR conflict files generated DFSRS CPU load DFSR RDC not enabled DFSR sharing violation DFSR staged file age DFSR staging area disk space DFSR USN records accepted DFSRS unresponsive DFSRS virtual memory DFSRS working set DNS Client Service is not running Domain controller CPU load Domain controller page faults Domain controller unresponsive File Replication Service is not running File replication (NTFRS) staging space free in kilobytes GC response too slow Group policy object inconsistent Hard disk drive Intersite Messaging Service is not running Invalid primary DNS domain controller address Invalid secondary DNS domain controller address KDC service is not running LSASS CPU load LSASS virtual memory LSASS working set Missing SRV DNS record for either the primary or secondary DNS server NETLOGON not shared NetLogon service is not running Orphaned group policy objects exist Review the reported orphaned GPO folders in the local SYSVOL and remove any that are obsolete. Physical memory Power supply Primary DNS resolver is not responding Secondary DNS resolver is not responding Security Accounts Manager Service is not running SRV record is not registered in DNS SYSVOL not shared W32Time service is not running Workstation Service is not running
Domain alerts Site alerts Forest alerts Azure Active Directory Connect alerts
Event Definitions PowerShell cmdlets

GC response too slow

Indicates that the response time of the servers that host the replica of the Global Catalog (GC) equals or exceeds the configured threshold value.

Category: Performance Counters
Name: NTDS LDAP searches a second
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
Required permissions: When monitored locally and remotely, only domain user privilege is required and the user must be a part of the Performance Logs user group.

The Directory Analyzer agent periodically issues a query against a well-known object in the GC and records the time that it takes to receive a response. If the time taken exceeds the configured threshold for a period exceeding the configured duration, the agent will set this alert condition.

This error can occur if any of the following occurs:

Active Directory® on the domain controller has failed in some way.

Make sure the indicated domain controller actually exists. If it is not, run NTDSUTIL and select the metadata cleanup option to clean up the erroneous objects in the directory.

Make sure the domain controller is running. If the domain controller is not running, start it.

Make sure the domain controller hosts a replica of the Global Catalog.

Ping the domain controller to see if there is connectivity. If there is not, fix that problem. The problem may be that DNS has the incorrect address or that the IP stack for the domain controller or the Directory Analyzer agent is misconfigured.

Check the LDAP response time for the domain controller on the Active Directory Health Analyzer Summary tab for the domain controller. If the LDAP response time is too high, you may need to add another domain controller for the same domain in the same site.

If this is the only server that hosts a replica of global catalog, you may need to add another global catalog to the site.

Group policy object inconsistent

Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
Permission requirements: When monitored locally and remotely, only domain user privilege is required.

The Directory Analyzer agent periodically compares the directory representation of GPOs in a domain to their representation on the local SYSVOL. This alert is active when the version number stored in SYSVOL differs from the version number expected in the local directory. This situation typically arises from high replication latency or duplicated NTDS Connection Objects.

A Group Policy Object on <server-name> is represented inconsistently between the local directory and the local file system. This problem can be remedied by forcing NTFRS and Active Directory® to refresh.

Hard disk drive

Indicates that issues have been detected for the hard disk drive on the domain controller.

Category: General
Name: Hard drive failed
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
Required permissions: When monitored locally, only domain user privilege is required. When monitored remotely, the target server must have WMI remote access enabled and the user must be a member of the Distributed COM Users group.

The Active Directory Health agent monitors the Hard drive failed data collector on the domain controller. When the hard disk drive of the selected domain controller has a status other than OK for a period of time equal to or longer than the configured threshold, this alert is raised.

Review the device configuration and contact your hardware vendor if required.

Intersite Messaging Service is not running

Indicates the Intersite Messaging Service is currently not running on the domain controller.

Category: Windows Services
Name: Intersite Messaging
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
Required permissions: When monitored locally or remotely, domain administrator privilege is required.

The Directory Analyzer agent periodically checks to ensure the Intersite Messaging Service is running.

Use the Services MCC snap-in or another SCP application to restart the Intersite Messaging Service.

Related Documents