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

Naming operations master not responding

Previous Next


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

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

This alert is generated if any of the following occurs:

•
The domain controller does not exist, is not running, or lost connectivity to the network
•
The DNS records for the domain controller are incorrect; e.g., the IP address for the domain controller is not what is published in DNS.
•
Active Directory® on the domain controller has failed, or is overloaded and taking too long to respond.
Resolution
•
Ping the domain controller to see if there is connectivity. If there is not, fix that problem. The problem may be that DNS has the incorrect address or the IP stack for the domain controller is misconfigured.
•
If the domain controller does not exist, run NTDSUTIL and select the metadata cleanup option to clean up the erroneous objects in the directory.
•
Check the LDAP response time for the domain controller on the Active Directory tab in the Active Directory Health module. If it is too high, you may need to add another domain controller for the same domain in the same site.

Schema operations master inconsistent

Previous Next


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

The Active Administrator® Foundation Service (AFS) monitors the value of the schema operations master attribute on each domain controller in the forest. If the value is not the same on each domain controller, an alert is generated.

The schema operations master object (CN=&ldots;) contains an attribute called fSMORoleOwner, which contains the distinguished name of the domain controller that is allowed to originate changes to the Active Directory® schema. When an administrator attempts to modify the Active Directory schema, the directory system agent (DSA) makes sure that the fSMORoleOwner property refers to the server on which the administrator is making the change. If it does not refer to that server, the DSA will not modify the schema. The schema operations master ensures that the schema cannot become inconsistent because of conflicting changes issued from different domain controllers.

If the schema operations master is inconsistent, meaning the domain controllers have differing values for the fSMORoleOwner attribute, it is possible for administrators (or others) to issue conflicting updates to the schema, potentially causing sufficient damage to Active Directory that replication will fail. It is important to not attempt to modify the Active Directory schema when the schema operations master is inconsistent.

The schema operations master can become inconsistent due to replication failures or due to an administrator using NTDSUTIL.EXE to require the operations master to another domain controller. This can also be a transient alert if the replication latency for the schema naming context is fairly large.

Resolution
•
Make sure that no one attempts to modify the Active Directory schema while the schema operations master is inconsistent.
•
Normally, the Active Directory replication process will correct this error, so the next step is to wait awhile to see if the alert clears by itself. The amount of time you should wait depends on the replication latency for the schema naming context. Active Directory Health Analyzer does not measure the latency of the schema naming context, but it does measure the latency of the configuration naming context, which will be the same.
•
If the alert does not clear itself in a reasonable amount of time, contact your Microsoft® Windows® support representative.

Schema operations master not responding

Previous Next


Alerts Appendix > Forest alerts > Schema operations master not responding

Schema operations master not responding

Indicates that the schema operations master is not responding within the configured threshold.

Data collector
•
Name: Schema operations master not responding
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: Domain user privilege is required.
Description

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

This alert is generated if any of the following occurs:

•
The domain controller does not exist, is not running, or lost connectivity to the network
•
The DNS records for the domain controller are incorrect; e.g., the IP address for the domain controller is not what is published in DNS.
•
Active Directory® on the domain controller has failed, or is overloaded and taking too long to respond.
Resolution
•
Ping the domain controller to see if there is connectivity. If there is not, fix that problem. The problem may be that DNS has the incorrect address or the IP stack for the domain controller is misconfigured.
•
If the domain controller does not exist, run NTDSUTIL and select the metadata cleanup option to clean up the erroneous objects in the directory.
•
Check the LDAP response time for the domain controller on the Active Directory tab in the Active Directory Health module. If it is too high, you may need to add another domain controller for the same domain in the same site.

Schema version inconsistent

Previous Next


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

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

Resolution
•
Wait for a while to see if the error clears itself. An inconsistent schema version alert can be transitory in nature.
•
If you have waited long enough for replication to have occurred to all domain controllers and the alert does not clear itself, contact your Microsoft® Windows® support representative.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating