1
00:00:08,850 --> 00:00:11,510
I've already mentioned a global catalog.

2
00:00:11,520 --> 00:00:13,770
So what is a global catalog?

3
00:00:13,800 --> 00:00:21,560
A global catalog is a partial, regionally searchable copy of all the objects in the forest.

4
00:00:21,570 --> 00:00:28,620
It spreads up searches for objects that might be stored on domain controllers in a different domain

5
00:00:28,620 --> 00:00:31,530
in the forest within a single domain.

6
00:00:31,530 --> 00:00:39,690
The address database on each domain controller contains all the information about every object in the

7
00:00:39,690 --> 00:00:40,410
domain.

8
00:00:40,410 --> 00:00:48,570
However, only a subset of this information replicates on the global catalog servers in other domains

9
00:00:48,570 --> 00:00:57,330
in the forest within a domain, a query for an object is directed to one of the domain controllers in

10
00:00:57,330 --> 00:00:58,230
that domain.

11
00:00:58,230 --> 00:01:06,390
But that query does not include results about objects in other domains in the forest For a query to

12
00:01:06,390 --> 00:01:14,070
include results from other domains in the forest, you must query a domain controller that is a global

13
00:01:14,070 --> 00:01:15,540
catalog server.

14
00:01:15,540 --> 00:01:24,360
By default, the domain the domain controller in the forest root domain is the only hosted global catalog

15
00:01:24,360 --> 00:01:32,370
server to enhance search and across domains in a forest, you should configure additional domain controllers

16
00:01:32,370 --> 00:01:36,360
to each store a copy of the Global Catalog.

17
00:01:36,390 --> 00:01:41,760
A global catalog does not contain all the attributes of each object.

18
00:01:41,760 --> 00:01:51,030
Instead, the global catalog maintains the subset of attributes that are most likely to be useful in

19
00:01:51,030 --> 00:01:52,830
gross domain searches.

20
00:01:52,830 --> 00:01:58,230
These attributes include given name, display, name and male.

21
00:01:58,260 --> 00:02:06,780
You can modify the set of attributes replicated to the global catalog by modifying the partial attribute

22
00:02:06,780 --> 00:02:09,570
set or path in the schema.

23
00:02:09,570 --> 00:02:14,280
Search in against a global catalog can be useful in many situations.

24
00:02:14,280 --> 00:02:22,260
For example, when a server that is run an exchange server receives an incoming email, it needs to

25
00:02:22,260 --> 00:02:31,890
search for the recipient's account so that it can decide how to route this mail this message by automatically

26
00:02:32,010 --> 00:02:39,120
where in a global catalog the server can locate the recipient in a multiple domain environment.

27
00:02:39,120 --> 00:02:45,660
In addition, when the user is signed into their Active Directory accounts, the domain controller that

28
00:02:45,660 --> 00:02:55,920
performs the authentication must contact a global catalog to check for universal group memberships before

29
00:02:55,920 --> 00:02:59,160
authenticating the user in a single domain.

30
00:02:59,160 --> 00:03:05,520
You should configure all the domain controllers to hold a copy of the global catalog.

31
00:03:05,520 --> 00:03:12,510
However, in a multiple domain environment, the infrastructure master should not be a global catalog

32
00:03:12,510 --> 00:03:19,740
server unless all the domain controllers in the domain are also global catalog server.

33
00:03:19,740 --> 00:03:27,960
So please remember again in a multiple domain environment, the infrastructure master should not be

34
00:03:27,960 --> 00:03:36,560
a global catalog server unless all the domain controllers in the domain are also global catalog servers.

35
00:03:36,570 --> 00:03:44,220
When you have multiple sites, you should also make at least one domain controller at each site a global

36
00:03:44,220 --> 00:03:50,010
catalog server so that you are not dependent on other sites.

37
00:03:50,010 --> 00:03:58,080
When you require global catalog queries, decide in which domain controllers to configure to hold a

38
00:03:58,080 --> 00:04:04,740
copy of the global catalog depends on replication, traffic and network bandwidth.

39
00:04:04,740 --> 00:04:12,390
Many organizations opt to make every domain controller a global catalog server.

40
00:04:12,390 --> 00:04:17,820
But again, this domain controller should not be the infrastructure master.