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

Detected NO_CLIENT_SITE record

Detected NO_CLIENT_SITE record in netlogon.log file.

Category: General
Name: NO_CLIENT_SITE record in netlogon.log file
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.

Identifies NO_CLIENT_SITE entries in the Netlogon logs of domain controllers, which helps you detect gaps in your environment where you may have straying clients. Clients that are not assigned to sites will randomly choose a domain controller to authenticate to, which means authentication requests could take much longer than expected.

The alert detail indicates the client that is not assigned to a site.

DFS Replication service not running

Indicates that a server hosting Distributed File System (DFS) is running, but the DFS Replication (DFSR) service is not. A DFSR service not running can affect group policies.

Category: Windows Services
Name: DFS Replication 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 administer privilege is required.

The Directory Analyzer agent periodically queries the Service Control Manager (SCM) to determine if the DFS Replication service is up and running. If the service is available on the domain controller, but it is currently not running, the agent issues this alert.

DFS Namespaces and DFS Replication offer simplified but highly-available access to files, load sharing, and WAN-friendly replication.

The most typical cause of this alert is when a server administrator shuts down the DFS service and forgets to restart it.

DFS service is not running

Indicates the Distributed File System (DFS) Namespace Service is stopped.

Category: Windows Services
Name: DFS Namespace 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.

The Directory Analyzer agent periodically checks to ensure the DFS Namespace Service is running.

Use the Services MCC snap-in or another SCP application to restart the DFS Namespace Service.

DFSR conflict area disk space

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.

If the ConflictAndDeleted folder runs out of space, DFS Replication removes older conflicting or deleted files to free up disk space, which might temporarily decrease replication performance.

If a staging folder quota is configured to be too small, DFS Replication might consume additional CPU and disk resources to regenerate the staged files. Replication might also slow down because the lack of staging space can limit the number of concurrent transfers with partners. Increasing the size of the staging folder and the ConflictAndDeleted folder can increase replication performance and the number of recoverable conflicting and deleted files.

Delete files from the ConflictAndDeleted folder or increase the quota of the ConflictandDeleted folder for the appropriate replicated folder(s).

https://msdn.microsoft.com/en-us/library/cc754229(v=ws.11).aspx

Verwandte Dokumente

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating