Chat now with support
Chat with Support

Active Administrator 8.4 - User Guide

Active Administrator Overview Certificates Security & Delegation Azure Active Directory  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 Configuring Azure Active Directory 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 DFSRS CPU load DFSR RDC not enabled DFSR sharing violation DFSR staged file age DFSR staging area disk space DFSR USN records accepted 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 Review the reported orphaned GPO folders in the local SYSVOL and remove any that are obsolete. 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

Missing root PDC time source

Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
Required permissions: Domain user privilege is required and the target server must have WMI remote access enabled. The user must be a member of the Distributed COM Users group.

Since Active Directory®, by default, sets all the clocks on all of the domain controllers in the forest from the PDC Role Owner of the root domain, it is recommended that the domain controller be configured to synchronize its time with an external time source. This alert is active if the root domain PDC Owner is not so configured.

Use the w32time command at an elevated PowerShell session to configure the PDC Role Owner to use an external time source.

Where TimeSource is one or more NTP servers noted by DNS or IP address. When TimeSource is a list of time servers the list must be enclosed in double quotes and each entry must be separated by at least one space. Some examples are listed below:

Objects exist in the Lost and Found container

Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
Required permissions: Domain user privilege is required.
Description

The Active Administrator® Foundation Service (AFS) periodically checks to see if there are any objects in the Lost And Found container in the domain. If there are, the DC Agent will issue an alert.

During the replication process, Active Directory® may encounter orphaned objects, which are objects that have no parent container. For example, a user deletes container X on domain controller A, and another user modifies object Y contained in container X on domain controller B. During replication, domain controller A will receive an update operation for an object that has no container because container X was deleted. In this case, the directory system agent (DSA) on domain controller A puts the object in the Lost And Found container.

The DSA will place objects in the Lost And Found container as part of its normal operation. However, serveral Lost And Found objects may indicate a replication problem, or at least the deletion of a container that should not have been deleted.

Resolution

Inspect the objects in the Lost And Found container of the replica indicated in the alert using an appropriate utility. Move the objects to an appropriate container or delete them from the Lost And Found container.

PDC operations master inconsistent

Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
Required permissions: Domain user privilege is required.
Description

The Active Administrator® Foundation Service (AFS) periodically checks the consistency of the domain PDC operations master value across all of the domain controllers in the domain. If any of the domain controllers has a differing value for the domain PDC operations master, an alert is issued.

The domain PDC operations master is contained in the fSMORoleOwner property of the domain object itself. Every domain controller in the domain has a copy of the domain PDC operations master.

The domain PDC operations master determines which domain controller in the domain is responsible for acting as a downlevel primary domain controller (PDC). If the domain PDC operations master is inconsistent, it is possible that two different domain controllers will act as the PDC, with potentially disastrous consequences.

The domain PDC operations master can become inconsistent because an administrator used NTDSUTIL.EXE to move the operations master when there was incomplete connectivity to all domain controllers in the domain. It can also occur because of replication errors.

Resolution

Wait to see if the error clears. An inconsistent operations master alert can be transitory in nature. If an administrator has moved an operations master to another domain controller, replication to all domain controllers in the domain can take some time. During this period, Active Directory Health Analyzer will indicate this alert condition.

If alert does not clear, contact your Microsoft Windows support representative.

Related article

https://blogs.technet.microsoft.com/mempson/2007/11/08/how-to-find-out-who-has-your-fsmo-roles/

PDC operations master not responding

Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
Required permissions: Domain user privilege is required.
Description

The Active Administrator® Foundation Service (AFS) periodically queries to find the response time of the PDC operations master. If the response time is above the configured threshold, an alert is issued.

This error can occur if any of the following occurs:

Active Directory® on the domain controller has failed in some way.
Resolution
Related Documents