Finally, note that the Universal Group Membership Caching feature only works for user authentication. If, for example, you have an Exchange Server on the infrastructure, and the link to a GC Server is not feasible, then there will be problems and UGMC will not help it beyond authenticating users.
When a user attempts to log in to an AD Domain, he then tries to communicate with a Domain Controller (DC) on the same AD Site, the Global Catalog (GC) Server reads the Universal Group Membership owned by the user and then authenticates him.
The UGMC automatic update interval from a DC to a GC Server is 8 hours. If there are frequent changes to Universal Memberships, it is a good idea to place a GC Server instead of caching. Also, UGMC is used when there is no communication with a GC Server.
When a user attempts to log in to an AD Domain, he then tries to communicate with a Domain Controller (DC) on the same AD Site, the Global Catalog (GC) Server reads the Universal Group Membership owned by the user and then authenticates him.
The UGMC automatic update interval from a DC to a GC Server is 8 hours. If there are frequent changes to Universal Memberships, it is a good idea to place a GC Server instead of caching. Also, UGMC is used when there is no communication with a GC Server.
UGMC can be enabled on a Site level, not on DC level. Also, to be able to connect a user through UGMC, each user should have previously authenticated successfully when both a Global Catalog Server was available and the UGMC was enabled. This way, the DC can cache the Universal Group Membership of the users. If a user has not logged in ...