• |
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019 |
• |
Required permissions: Domain user privilege in the domain where the schema and naming masters reside. |
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.
• |
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 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:
• |
Active Directory® on the domain controller has failed, or is overloaded and taking too long to respond. |
• |
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. |
• |
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) 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.
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 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 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:
• Active Directory® on the domain controller has failed, or is overloaded and taking too long to respond.Resolution
• 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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center