It is important to understand that global catalog objects must be physically located close to all objects in a network that require prompt login times and fast connectivity. Because a global catalog entry is parsed for universal group membership every time a user logs in, this effectively means that this information must be close at hand. This can be accomplished by placing GC/DCs on the same WAN site or by using a process new to Windows Server 2003 called universal group caching. Universal Group CachingUniversal group caching is a process by which an Active Directory site caches all universal group membership locally so that the next time clients log in, information is more quickly provided to the clients and they are able to log in faster. Universal group caching is more effective than placing a GC/DC server locally because only those universal groups that are relevant to a local site's members are replicated and are cached on the local domain controller. The downside to this approach, however, is that the first login for clients will still be longer than if a local GC/DC were provided, and the cache eventually expires , requiring another sync with a GC/DC. You can set up universal group caching on a site level as follows :
Global Catalog/Domain Controller PlacementAs you learned in the preceding sections, you must make decisions regarding the most efficient placement of DCs and GC/DCs in an environment. Decisions on placement of GC/DCs and universal group caching sites must be made with an eye toward determining how important fast logins are for users in a site compared to higher replication throughput. However, for many Windows Server 2003 environments, the following rules apply:
The recommendations listed here are generalized and should not be construed as relevant to every environment. However, these general guidelines should help you to size an Active Directory environment for domain controller placement. |