Chat now with support
Chat with Support

Active Administrator 8.6.2 - User Guide

Active Administrator Overview User Provisioning Certificates Security & Delegation  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 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 DFSR RDC not enabled DFSR sharing violation DFSR staged file age DFSR staging area disk space DFSR USN records accepted DFSRS CPU load 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 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

Physical memory

Previous Next



Physical memory

Indicates that issues have been detected for the physical memory on the domain controller.

Data collector
Category: General
Name: Memory degrade
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Not supported on: Virtual computers
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.
Description

The Directory Analyzer agent monitors the Memory degrade data collector on the domain controller. When the physical memory 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.

Resolution

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

Power supply

Previous Next



Power supply

Indicates that issues have been detected for the power supply on the domain controller.

Data collector
Category: General
Name: Power supply failed
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Not supported on: Virtual computers
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.
Description

The Active Directory Health agent monitors the Power supply failed data collector on the domain controller. When the power supply 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.

Resolution

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

Primary DNS resolver is not responding

Previous Next


Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: When monitored locally and remotely, 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.
Description

The Directory Analyzer agent periodically checks each of its configured DNS resolvers to make sure that they are responding within an acceptable duration. If any configured resolver is unavailable or not responding within a preset duration threshold, this alert is generated.

The test for responsiveness is done by timing the lookup of critical DNS service records from each resolver.

Resolution

Check to make sure that the identified resolver is actually available and responsive.

Secondary DNS resolver is not responding

Previous Next


Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: When monitored locally and remotely, 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.
Description

The Directory Analyzer agent periodically checks each of its configured DNS resolvers to make sure that they are responding within an acceptable duration. If any configured resolver is unavailable or not responding within a preset duration threshold, this alert is generated.

The test for responsiveness is done by timing the lookup of critical DNS service records from each resolver.

Resolution

Check to make sure that the identified resolver is actually available and responsive.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating