As you may remember from the 70-640 MCTS Windows Server 2008 Active Directory exam, a global catalog server is a server that contains a master list of all the objects in a domain or forest. The global catalog itself is the master list, and it is transmitted across servers for the purpose of informing individual machines throughout the environment of what objects actually exist and, more importantly, where they can be found. The Sybex 70-640 book Windows Server 2008 Active Directory Configuration Study Guide calls this list the ?universal phone book?of Active Directory. Not only is that pretty clever, it’s also very accurate.
The global catalog serves two more functions. First, it enables users to log on because it informs a domain controller of the universal group membership of the rest of the servers. Second, it resolves user principal names of which a particular domain controller may not be aware.
Deciding which server is going to contain your global catalog is one of the most important decisions you will make when you are beginning to design a network. Depending on its location, it can directly affect the speed of your site replication, the amount of time your servers spend updating themselves with the latest objects, and how quickly the rest of the environment becomes aware of changes.
By default, the first tree (domain) in a forest is always a global catalog server. This is because if a forest didn?t have a copy of the global catalog, it really wouldn?t achieve much, because no credentials would be cached and it wouldn?t have a list of what user accounts existed. Beyond the initial global catalog servers, here are a couple of other reasons you might want to add a global catalog server: users of custom applications, unavailable WAN links, and roaming users.
Just like the global catalog server location, the operations master location is one of the most important design decisions you will have to make when creating your network infrastructure. However, unlike the global catalog server, the operations master server is broken down into ?ve separate roles that have to be considered.
If you have a choice in the matter, the best decision for the schema master is to use it as little as possible. Modifying the schema isn?t something you want to do very often, because it tends to be very heavy handed and can cause a lot of problems if you aren?t careful. When placing the schema master, the main thing you have to keep in mind is the location of your schema administrators. They will be the sole benefactors of this location, and therefore you need to plan accordingly.