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

DFSR conflict files generated

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.

Monitoring this performance counter enables administrators to keep track of the number of replication conflicts generated for replicated folders on the monitored computer. Monitoring the space utilization of the Conflict and Deleted area helps ensure that there is enough space to store replication conflicts and files deleted from replicated folders on the monitored computer. You can view a log of conflict files and their original file names by viewing the ConflictandDeletedManifest.xml file in the DfsrPrivate folder.

Frequent conflicts indicate that files in a replicated folder are frequently being modified on multiple servers in a short period.

In general, resolution of this alert condition involves deciding whether a conflict object contains useful information, moving that information into a different directory object, and then deleting the object. Determining whether the conflict object has any useful information is up to you, the administrator.

DFSR RDC not enabled

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

Remote Differential Compression (RDC) only updates changes to files, which is useful when replicating across a wide area network.

Resolution

Enable Remote Differential Compression.

DFSR sharing violation

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 DFRS debug log for reports of sharing violations. If the sharing violation exists for a period exceeding the configured duration, the agent sets this alert condition.

One possibility for the sharing violation is that other sources may have opened the file to be replicated on the target computer.

Another possibility for a sharing violation is that other sources have open handles to the file to be replicated. Typically, programs that can instigate sharing violations are:

Resolution
Related article

https://support.microsoft.com/en-us/help/822300/frs-encounters-error-sharing-violation-errors-when-it-tries-to-replicate-data-that-is-still-in-use

DFSR staged file age

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 age of files in the DFRS staging area. If the file is older than the configured time then the alert condition is set.

This problem could be caused by the following factors:

Resolution

If a D2 was not performed on a downstream partner, look for failure indicators at either the upstream or downstream partners. If you cannot find failure indicators, re-examine the schedule and network bandwidth on this connection to ensure that enough replication time is scheduled to allow the data to replicate.

Verwandte Dokumente

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating