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 time sync lost

Previous Next


Alerts Appendix > Domain controller alerts > DC time sync lost

DC time sync lost

Indicates that the time of the target domain controller differs from one of its reference sources by more than the configured threshold (in seconds).

Data collector
•
Category: General
•
Name: Domain controller time synchronization
•
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 periodically checks its local time against the configured time reference servers. If the time is off by more than the configured threshold (in seconds), the alert is raised.

The Windows® Time (W32Time) service on a domain controller is responsible for maintaining the accuracy of the clock with respect to the time sources. Active Directory® defines rules for time sources as follows:

•
A domain controller in a domain will synchronize its clock to the domain controller in the domain that is the PDC Role Owner for its domain, unless the domain controller in question is the PDC Role Owner.
•
If the domain controller is the PDC Role Owner, it will synchronize its clock with the PDC Role Owner of its parent domain, unless the domain controller is in the root domain.
•
If the domain controller is in the root domain and it is the PDC Role Owner for that domain, it must be configured to synchronize its clock to an external time source.

A special case exists for the PDC Role Owner in domains that are at the root of the forest but are not the root domain (the root domain being defined as the first domain ever created in the forest). These domain controllers synchronize themselves to the PDC Role Owner in the root domain.

Any domain controller can have these settings overridden by configuring the domain controller to synchronize with an external time source using the Net Time command. If the domain controllers are so configured, then the Directory Analyzer agent will check the time against the configured external time source(s).

Resolution
•
Ensure that the W32Time service is running on the domain controller that has this alert.
•
Check the event log on the domain controller to determine ensure that the W32Time service is not reporting errors.
•
Since the domain controller must have connectivity to its time source in order to synchronize its clock, use Active Directory Health Analyzer to determine if other connectivity related alerts may be occurring.

Detected NO_CLIENT_SITE record

Previous Next


Alerts Appendix > Domain controller alerts > Detected NO_CLIENT_SITE record

Detected NO_CLIENT_SITE record

Detected NO_CLIENT_SITE record in netlogon.log file.

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

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.

Resolution

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

DFS Replication service not running

Previous Next


Alerts Appendix > Domain controller alerts > DFS Replication service not running

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.

Data collector
•
Category: Windows Services
•
Name: DFS Replication Service
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: When monitored locally, only domain user privilege is required. When monitored remotely, domain administer privilege is required.
Description

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.

Resolution
•
Check the status of the service by running the Services MMC snap-in. Select the Server DNS (not DNS Client) entry. If the status is stopped, then the service is actually down.
•
If the DFS service is stopped, use the Services MCC snap-in or another SCP application to restart the DFS Service. Check the Event Logs and fix any problems indicated by the logs.

DFS service is not running

Previous Next


Alerts Appendix > Domain controller alerts > DFS service is not running

DFS service is not running

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

Data collector
•
Category: Windows Services
•
Name: DFS Namespace Service
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
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 the DFS Namespace Service is running.

Resolution

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

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen