Active Administrator 8.6.2 - User Guide

DC SYSVOL disk space

DC SYSVOL disk space

Indicates that the available disk space on the volume host SYSVOL is less than or equal to the configured threshold.

Data collector

•	Category: General

•	Name: SysVol 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 partition containing the SYSVOL directory. If the amount of free disk space on this partition drops below the threshold set by the administrator for a period exceeding the configured duration, the agent will set this alert condition.

The SYSVOL is a directory that contains user profile information that is replicated (via File Replication Services) to each domain controller in the domain. Although the SYSVOL is not actually part of Active Directory®, a failure in SYSVOL replication can cause user login failures.

Resolution

Find the directory containing the SYSVOL information by checking the registry key \\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetLogon\Parameters and looking at the value for the Sysvol value. This is the path of the SYSVOL directory.

If files in the SYSVOL directory are using the disk space, remove as many of these files as you can.

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

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

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.