Chat now with support
Chat mit Support

Active Administrator 8.7 - 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

DC DIT log file disk space

Previous Next


Alerts Appendix > Domain controller alerts > DC DIT log file disk space

DC DIT log file disk space

Indicates that the amount of disk space available on the volume Active Directory® uses for its log files is less than or equal to the configured threshold.

Data collector
Category: General
Name: Active Directory database log details
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 monitors the disk space available on the volume containing the Active Directory log files. If the amount of disk space available on this volume drops below the configured threshold for a period exceeding the configured duration, the agent sets this alert condition.

If Active Directory runs out of disk space during processing, it will eventually fail, and the server will shut down immediately.

A low disk space condition can be due to many different things, such as:

The directory service agent (DSA) periodically runs a cleanup task that recovers space from deleted objects in the directory for reuse by Active Directory.

Resolution

First, check the registry on the server to determine the disk volume that contains the Active Directory log files. Under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters registry key, the value Database log files path contains the path of the file in which Active Directory keeps its log files.

If you have recently deleted a large number of objects, you can reclaim disk space from the directory using Ntdsutil.exe to compact files.

DC LDAP load

Previous Next



DC LDAP load

Indicates that the amount of Lightweight Directory Access Protocol (LDAP) traffic serviced by the domain controller equals or exceeds the configured threshold.

Data collector
Category: Performance Counters
Name: NTDS LDAP writes a second
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 and the user must be a part of the Performance Logs user group.
Description

The Directory Analyzer agent monitors the NTDS LDAP writes a second performance counter on the domain controller. If the value goes above the configured threshold for a period exceeding the configured duration, the agent sets this alert condition.

Active Directory® clients use LDAP to communicate with the Directory Service Agent (DSA). A high LDAP load indicates that a lot of clients are making many requests of the DSA. Increased LDAP load can reduce the throughput of the DSA, and can cause important directory transactions, such as login and authentication, to fail.

Resolution

Identify the source of the LDAP traffic by using a network traffic analyzer. Note that a traffic analyzer will not detect the traffic generated by a process running on the domain controller itself.

DC LDAP response too slow

Previous Next


Alerts Appendix > Domain controller alerts > DC LDAP response too slow

DC LDAP response too slow

Indicates that the response time of the domain controller to a Lightweight Directory Access Protocol (LDAP) request equals or exceeds the configured threshold.

Data Collector
Category: General
Name: LDAP response time
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.
Description

The Directory Analyzer agent periodically issues a simple LDAP query to each domain controller in the site it monitors and measures the time between issuing the LDAP request and receiving a response. An alert is generated if the response time exceeds the configured threshold for longer than the configured duration.

Active Directory® clients use LDAP to communicate with the Directory Service Agent (DSA). A high response time value indicates that the domain controller is not satisfying directory requests quickly, which can result in poor client response times and, if bad enough, login and authentication failures.

Anything that could cause a reduction in overall system performance can increase LDAP response time. For instance, running too many processes, or running processes that use too much memory or CPU can reduce system performance and increase LDAP response times.

A poorly configured server can also increase LDAP response times. For instance, if the paging file is not large enough or if the disks are badly fragmented, poor disk performance can increase LDAP response time.

In some cases faulty hardware can also cause an increase in LDAP response time. For instance, a marginal Network Interface Card (NIC) can reduce network performance on the server, and a failing disk can make directory queries take a long time.

It is possible that the DSA on the domain controller is overloaded by incoming directory requests, by excessive Access Control List (ACL) propagation, or by too many complex directory queries.

Resolution

DC Memory Usage

Previous Next



DC Memory Usage

Indicates that the RAM memory usage on the domain controller is greater than 60 percent. The alert becomes critical if the memory usage is greater than 80 percent.

Data collector
Category: Performance Counters
Name: Memory Usage
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 and the user must be a part of the Performance Logs user group.
Description

The Directory Analyzer agent monitors the Memory Usage performance counter on the domain controller. 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.

Increased memory usage is a result of running too many applications on the server, or running applications that require too much physical memory.

It is also possible that memory use has increased due to some pathological condition in a particular application. For instance, Active Directory® itself requires substantial resources when it is processing inherited Access Control Lists (ACLs). Active Directory can also require a lot of resources when it processes complex, non-indexed directory searches.

Resolution

First, try to determine if the increased memory use is due to a particular program, or if it is due to running too many programs. Use a utility like Task Manager to inspect the memory usage of all processes on the system. If there are several processes getting more than 60% of the memory, then the problem is most likely due to running too many programs on the server. If possible, stop some of the programs.

If one process is using all of the memory for an extended period of time, it may be due to a bug in the software, or it may be that the program just requires too much memory. If possible, stop the program and run it on a different computer.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen