OK Learn more. Cookie and Privacy Settings. How we use cookies. Essential Website Cookies. Other external services. Privacy Policy. You can read about our cookies and privacy settings in detail on our Privacy Policy Page. To understand how the global catalog works, it is important to first understand a little bit about how the Active Directory database is structured.
To simplify administration and facilitate efficient replication, the database itself is logically separated into partitions. Domain controllers may also maintain application partitions.
These partitions contain information relating to AD-integrated applications e. Application partitions have no specific replication requirements; they are not required to replicate to other domain controllers but can be configured to replicate to any domain controller in a forest. The graphic below contains a depiction of a forest consisting of three domains and simple representations of domain controllers from each of the three domains.
As the graphic illustrates, each domain controller maintains a replica of its local domain partition, the configuration partition, and the schema partition. In a multi-domain forest like the one shown above, global catalog servers also host an additional set of read-only partitions.
Each of these partitions contains a partial, read-only replica of the domain partition from one of the other domains in the forest.
It is the information in these partial, read-only partitions that allow global catalog servers to function as a reliable central repository of domain information. As a result, domain controllers that have been configured as global catalog servers are used to process authentication and forest-wide search requests in a multi-domain forest. In multiple-domain forests, global catalog servers facilitate user logon requests and forest-wide searches.
The following illustration shows how to determine which locations require global catalog servers. In most cases, it is recommended that you include the global catalog when you install new domain controllers.
The following exceptions apply:. Determine whether any applications that perform poorly over a slow WAN link are running in locations or whether the locations require Microsoft Exchange Server. If your locations include applications that do not deliver adequate response over a WAN link, you must place a global catalog server at the location to reduce query latency.
Read-only domain controllers RODCs can be promoted successfully to global catalog server status. However, certain directory-enabled applications cannot support an RODC as a global catalog server. However, Microsoft Exchange Server works in environments that include RODCs, as long as there are writable domain controllers available.
Exchange Server also ignores RODCs in default conditions where Exchange components automatically detect available domain controllers. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Directory Services. Sign in to vote. Hi I wish to know what the correct path I should type to allow the below to work:?
Edited by mikey Wednesday, January 18, PM. Wednesday, January 18, PM.
0コメント