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

Intra-site replication topology generation disabled

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

The Active Administrator® Foundation Service (AFS) periodically checks the Knowledge Consistency Checker (KCC) configuration for each site and alerts when the replication topology generation functionality of the KCC has been explicitly disabled. While disabling the KCC is a valid administrator action, it can result in poorly-tuned replication topologies.

Clear the first bit (1) of the <Root Domain>\Configuration\Sites\<Site name>\NTDS Site Settings\options value to re-enable inter-site topology generation.

Morphed directories exist in site

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

All files and folders that File Replication Service (FRS) manages are uniquely identified internally by a special file identifier. FRS uses these identifiers as the canonical identifiers of files and folders that are being replicated. If FRS receives a change order to create a folder that already exists, which by definition has a different file identifier than the duplicate folder, FRS protects the conflicting change by leaving the original directory structure intact, and renaming the conflicting directory to a unique name so that underlying files and folders can be preserved. The conflicting folder is given a new name in the following format: <FolderName>_NTFRS_<GUID>, where <FolderName> is the original name of the folder and <GUID> is a unique character string, such as 001a84b2.

Common causes of this condition are:

Resolution

No authority in site to resolve universal group memberships

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 Knowledge Consistency Checker (KCC) configuration for each site. If universal group membership caching is disabled and there are no global catalogs in the site, an alert is issued.

While this is a valid configuration for a site, if the site is connected through a slow link, it can result in poor logon performance.

Resolution

Too few global catalog servers in site

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 Directory Analyzer agent checks the state of all of the domain controllers in the site, and if the number of domain controllers that host a global catalog is less than the configured threshold for a period exceeding the configured duration, an alert is issued.

Each site in an Active Directory® enterprise should have at least one domain controller configured as a global catalog. The workstation login process always attempts to contact a global catalog server, and if none are running at the site where the workstation resides, the workstation will connect to a global catalog server outside of the site, which can cause excess WAN traffic and unnecessary delays in the login process.

Resolution
Related Documents