1
00:00:07,010 --> 00:00:11,470
Every Active Directory Forest includes at least one site.

2
00:00:11,590 --> 00:00:18,460
You should create additional sites when you have the following scenarios a slow link separates part

3
00:00:18,460 --> 00:00:27,340
of the network or a part or a part of the network has enough users to warrant host and domain controllers

4
00:00:27,340 --> 00:00:30,310
or other services in that location.

5
00:00:30,310 --> 00:00:39,070
Or you want to control service location and localization or you want to control replication between

6
00:00:39,070 --> 00:00:40,370
domain controllers.

7
00:00:40,420 --> 00:00:45,970
Let's review each of these scenarios a slow link separates part of the network.

8
00:00:45,970 --> 00:00:56,200
As previously mentioned a site is characterized by a location with fast reliable inexpensive connectivity

9
00:00:56,530 --> 00:01:03,570
if two locations are connected by a slow link you should configure reach location as a separate edit

10
00:01:03,630 --> 00:01:12,330
inside a slow link typically is one that has a connection of less than 512 killer bits per second.

11
00:01:12,370 --> 00:01:20,590
The next scenario is a part of network has enough users to warrant host and domain controllers or other

12
00:01:20,590 --> 00:01:22,540
services in that location.

13
00:01:22,540 --> 00:01:27,800
Concentrations of users also can influence your assigned design.

14
00:01:27,910 --> 00:01:36,070
If a network location has a sufficient number of users for whom the inability to authenticate would

15
00:01:36,070 --> 00:01:43,960
be problematic place a domain controller in the location to support authentication within the location.

16
00:01:43,960 --> 00:01:51,700
After you place a domain controller or other distributed service and allocation that will support those

17
00:01:51,700 --> 00:02:00,970
users you might want to manage a tedious application to the location or localized service by configuring

18
00:02:01,210 --> 00:02:06,480
an active directory site to represent their location.

19
00:02:06,490 --> 00:02:14,320
The next scenario is that you want to control service localization by establish an entity as sites you

20
00:02:14,320 --> 00:02:23,710
can ensure that clients use domain controllers that are nearest to them for authentication which reduces

21
00:02:24,070 --> 00:02:29,860
authentication lent latency and traffic on when connections.

22
00:02:29,860 --> 00:02:34,090
In most scenarios each site will contain a domain controller.

23
00:02:34,090 --> 00:02:44,200
However you might configure sites to a localized services other than authentication such as DFS windows

24
00:02:44,230 --> 00:02:48,490
branch cache and exchange server services.

25
00:02:48,490 --> 00:02:56,410
In this case some sites might be configured without a domain controller and the less Samarra is when

26
00:02:56,410 --> 00:03:03,530
you want to control replication between domain controllers scenarios might exist in which to well-connected

27
00:03:03,610 --> 00:03:10,440
domain controllers are allowed to communicate only at certain times of the day.

28
00:03:10,450 --> 00:03:19,290
Great insights allow you to control how and when replication takes place between domain controllers.