Chat now with support
지원 담당자와 채팅

Active Administrator 8.3 - Web Console User Guide

Active Administrator Web Console Overview Active Directory Health Alerts Notifications Active Directory Health Check
Using the Health Check landing page Creating a Health Check Setting options for Health Check tests Health check tests
Forest tests Domain tests Domain controller tests Site tests
Active Directory Topology Reports Network Operations Center

Naming operations master is not a global catalog server

Indicates that a server possessing the domain naming operations master does not host a global catalog (GC).

Supported on: Windows Server® 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Required permissions: Domain user privilege in the domain where the schema and naming masters reside.

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.

Naming operations master not responding

Indicates if the naming operations master is not responding within the configured threshold.

Supported on: Windows Server® 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Required permissions: Domain user privilege is required.
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.

Schema operations master inconsistent

Indicates that the schema operations master is not consistent among all domain controllers in the forest.

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

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 force the operations master to another domain controller. This can also be transient if the replication latency for the schema naming context is fairly large.

Schema operations master not responding

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

Supported on: Windows Server® 2008 R2, Windows Server 2012, Windows Server 2012 R2, and Windows Server 2016
Required permissions: Domain user privilege is required.
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.
관련 문서