Chat now with support
Chat mit Support

Active Administrator 8.5 - User Guide

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

Consecutive replication failures

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.

The Directory Analyzer agent constantly monitors replication events on a server. When replication fails too many consecutive times, this alert is issued.

DC cache hits

Indicates the performance of the server may be degraded because of too few cache read hits.

Category: Performance Counters
Name: Cache copy read hits
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 monitors the cache copy read hits data collector on the domain controller. If the value of the data collector drops below the configured threshold for a period exceeding the configured duration, the agent sets this alert condition.

DC DIT disk space

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

Category: General
Name: Active Directory database details
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.

The Directory Analyzer agent monitors the disk space available on the volume containing the Active Directory database. 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:

It is also possible that Active Directory may be using up more disk space than normal by importing a large number of objects into the directory through replication or by creating a large number of users or other directory objects.

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

Check the registry on the server to determine the disk volume that contains the Active Directory database. Under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters registry key, the value DSA Database file contains the path of the file in which Active Directory keeps its database. If the Active Directory database is stored on the C: drive and this is the same drive that contains the system TEMP directory (usually C:\TEMP), delete all of the files in the TEMP directory.

Determine what directories are using the most disk space. Using Windows® Explorer, right-click on each directory and select Properties. The disk space used by the directory sub-tree will appear on the Properties page. After you determine what is causing the directories to grow, run Ntdsutil.exe to compact files, move files to another volume, or move transaction logs to another volume.

If Active Directory ran low on disk space during a server backup, the problem may be due to the space used by temporary files created by the backup process. If this is the case, you can configure Active Directory to keep its backup files on a different volume.

As a general tip, it is a good idea to put the Active Directory database on its own file volume with only Administrator access so that the disk space available to Active Directory cannot be reduced by other applications.

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.

Category: General
Name: Active Directory database log details
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.

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.

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.

Verwandte Dokumente

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating