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

Invalid primary DNS domain controller address

•
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. 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

Active Directory Health Analyzer queries DNS for the Service (SRV) records and compares the results to the IP address reported by the Directory Analyzer agent hosted on the domain controller. This alert is raised if the address retrieved in the DNS query is malformed, does not exist, or does not match the address reported by the agent.

This alert is accompanied by a list of aberrant DNS SRV entries. Each entry consists of an IP address and a DNS name delimited by a single space. For example:

194.165.85.104 mothra.destroy.all.monsters.com
194.165.85.99 gammra.destroy.all.monsters.com

Typically, this alert condition is raised due to invalid SRV entries in the DNS database file, or interrupted connectivity between the domain controller and the DNS Server. This condition may also occur if a domain controller is configured to obtain its IP address dynamically (via DHCP). If the DNS server is either not configured to use Dynamic DNS or does not recognize the new lease once the domain controller is rebooted, an alert is raised. Note that it is strongly recommended that the IP addresses of all domain controllers be statically assigned.

Resolution

Reconcile the DNS SRV entries with the IP address reported by the network adapter (or by DHCP, if applicable). The SRV entries appear under _ldap._tcp.dc._msdcs.<zone-name> in the DNS Management Console.

Invalid secondary DNS domain controller address

•
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. 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

Active Directory Health Analyzer produces this alert by querying DNS for the Service (SRV) records and compares the results to the IP address reported by the Directory Analyzer agent hosted on the domain controller. This alert is raised if the address retrieved in the DNS query is malformed, does not exist, or does not match the address reported by the agent.

This alert is accompanied by a list of aberrant DNS SRV entries. Each entry consists of an IP address and a DNS name delimited by a single space. For example:

194.165.85.104 mothra.destroy.all.monsters.com
194.165.85.99 gammra.destroy.all.monsters.com

Typically, this alert condition is raised due to invalid SRV entries in the DNS database file, or interrupted connectivity between the domain controller and the DNS Server. This condition may also occur if a domain controller is configured to obtain its IP address dynamically (via DHCP). If the DNS server is either not configured to use Dynamic DNS or does not recognize the new lease once the domain controller is rebooted, an alert is raised. Note that it is strongly recommended that the IP addresses of all domain controllers be statically assigned.

Resolution

Reconcile the DNS SRV entries with the IP address reported by the network adapter (or by DHCP, if applicable). The SRV entries appear under _ldap._tcp.dc._msdcs.<zone-name> in the DNS Management Console.

KDC service is not running

Indicates the Kerberos Key Distribution Center (KDC) service is not currently running on the domain controller.

Data collector
•
Category: Windows Services
•
Name: Kerberos Key Distribution Center Service
•
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, domain administrator privilege is required.
Description

The Directory Analyzer agent periodically checks to ensure that the KDC service is running.

Resolution

Use the Services MCC snap-in or another SCP application to restart the KDC service.

LSASS CPU load

Indicates that the CPU for the Local Security Authority Service (LSASS) service on the domain controller is too busy, which can indicate a problem with directory service.

Data collector
•
Category: Performance Counters
•
Name: LSASS % processor time
•
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.
Description

The Directory Analyzer agent monitors the Process(lsass)\% Processor Time performance counter on the domain controller for the LSASS service. If the value of the performance counter goes above the configured threshold for a period exceeding the configured duration, the agent will set this alert condition.

Resolution

Please refer to the documents listed below for resolutions when Lsass.exe causes high CPU usage.

Related articles
•
https://msdn.microsoft.com/en-us/library/bb727054.aspx
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating