Chat now with support
Chat with 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
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: Domain user privilege in the domain where the schema and naming masters reside.
Description

The Active Administrator® Foundation Service (AFS) monitors the owners of the domain naming operations master and schema operations master. When AFS finds that they reside on separate servers, an alert is issued.

Resolution

To determine the controllers have the domain naming and schema operations masters

a
Select Active Directory Health | Analyzer.
b
Expand Sites, and select the site.
c
Locate the domain controllers with Yes in the Schema and Naming columns.

Domain naming operations master inconsistent

Previous Next


Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: Domain user privilege in all domains in the forest.
Description

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

The domain naming operations master is contained in the fSMORoleOwner property of the CN=Partitions,CN=Configuration,DC=<root domain> container. Because the partitions container is part of the configuration naming context, every domain controller in the forest has a copy of the domain naming operations master. The domain naming operations master determines what domain controller in the forest can initiate a domain renaming operation. If the domain naming operations master is inconsistent, it is possible to issue a domain renaming operation simultaneously at two different domain controllers, with potentially disastrous consequences.

The domain naming 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. It can also occur because of replication errors.

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

Domain naming operations master is not a GC

Previous Next


Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: Domain user privilege in the domain where the schema and naming masters reside.
Description

The Active Administrator® Foundation Service (AFS) monitors the domain naming operations master status for each domain in Active Directory®, continually checking to see that each domain naming operations master also hosts a global catalog. When a domain naming operations master is found that does not host a global catalog, this alert is triggered.

The domain naming operations master must be a global catalog server because the domain naming operations master is responsible for creating objects that represent new domains. In order to do this, the domain naming operations master must be able to make sure that no other object — whether it is a domain object or not — has the same name as the new domain object. The domain naming operations master always runs a global catalog, which contains a partial replica of every object, to allow the domain naming operations master to quickly check for a duplicate object name prior to creating a new domain object.

Resolution
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating