1
00:00:06,980 --> 00:00:14,960
When you adjourn I Windows client operating system to a domain and then restarted the client complete

2
00:00:15,250 --> 00:00:20,490
at the main controller location and registration process.

3
00:00:20,510 --> 00:00:28,250
The goal of this registration process is to locate the Domain Controller with the most efficient and

4
00:00:28,250 --> 00:00:35,030
closest location to the client's location based on IP subnet information.

5
00:00:35,060 --> 00:00:43,630
The process for locating a domain controller is as follows the new client queries for all domain controllers

6
00:00:43,640 --> 00:00:47,700
in the domain as the new domain client restarts.

7
00:00:47,840 --> 00:00:56,460
It receives an IP address from a DCP server and is ready to authenticate to the domain.

8
00:00:56,480 --> 00:01:01,230
However the client does not know where to find or domain controller.

9
00:01:01,250 --> 00:01:09,590
Therefore the client queries for a domain controller by wearing the underscored DCP folder which contains

10
00:01:09,680 --> 00:01:15,140
the as several real records for all domain controllers in the domain.

11
00:01:15,140 --> 00:01:23,880
The second step is that the client attempts and Eldad been to all domain controllers in a sequence.

12
00:01:24,050 --> 00:01:32,450
Janus returns a list of almost matching domain controllers and the client attempts to contact all of

13
00:01:32,780 --> 00:01:36,070
the domain controllers on its first startup.

14
00:01:36,080 --> 00:01:43,910
The third step is that the first domain controller response the first domain controller that responds

15
00:01:43,910 --> 00:01:53,720
to the client examines the client's IP address growth references that IP with subnet objects and informs

16
00:01:53,720 --> 00:01:57,610
the client of the site to reach the client belongs.

17
00:01:57,620 --> 00:02:04,160
The client stores the site name in its registry and then whereas the domain controller in the site's

18
00:02:04,160 --> 00:02:06,700
specific DCP folder.

19
00:02:06,770 --> 00:02:11,990
The next step the client queries for all domain controllers in the site.

20
00:02:12,020 --> 00:02:15,950
Dennis returns a list of all domain controllers on the site.

21
00:02:15,950 --> 00:02:17,300
Step number five.

22
00:02:17,390 --> 00:02:24,230
The client attempts an old Debian sequential ID to all domain controllers in the site.

23
00:02:24,260 --> 00:02:30,780
The domain controller that responds first authenticate the client and the last step.

24
00:02:30,830 --> 00:02:37,730
The client forms an affinity the client forms an affinity with the domain controller that responded

25
00:02:37,730 --> 00:02:43,730
first and then attempts to authenticate with the same domain controller in the future.

26
00:02:43,790 --> 00:02:46,990
If the domain controller is unavailable the client.

27
00:02:47,060 --> 00:02:56,120
Whereas the sites disappear folder again and again attempts to bind with the first domain controller.

28
00:02:56,120 --> 00:03:03,020
That response in the site if the client moves to another site which might be the case with a mobile

29
00:03:03,020 --> 00:03:09,790
computer the client attempts to authenticate to his preferred domain controller the Domain Controller

30
00:03:09,800 --> 00:03:18,500
notices that the client's IP addresses associated with a different side and it then refers the client

31
00:03:18,770 --> 00:03:20,050
to the new site.

32
00:03:20,120 --> 00:03:28,100
The client then whereas DNS for domain controllers in the local side you can configure a site to direct

33
00:03:28,100 --> 00:03:37,960
users to local Corpus of replicated resources such as shared folders replicated within a DFS namespace.

34
00:03:38,000 --> 00:03:45,980
There might be scenarios in which you require only service localization with no need for a domain controller

35
00:03:46,280 --> 00:03:48,180
located within the site.

36
00:03:48,200 --> 00:03:57,430
In this case a nearby domain controller will register it is a a record in the site by using the site

37
00:03:57,440 --> 00:04:05,540
coverage process aside without a domain controller generally is covered by a domain controller in a

38
00:04:05,540 --> 00:04:11,630
site with the lowest site Lynn cost to the site that requires coverage.

39
00:04:11,630 --> 00:04:18,730
You also can configure site coverage and a record priority manually.

40
00:04:19,040 --> 00:04:23,840
If you want to control authentication in sites without domain controllers.