1
00:00:07,010 --> 00:00:09,820
Let's have a brief overview of this section content.

2
00:00:10,180 --> 00:00:14,640
But before we begin traditional let's start with several questions.

3
00:00:14,650 --> 00:00:22,600
Question 1 What is the minimum domain functional level in which you should deploy a Windows Server 2016

4
00:00:22,720 --> 00:00:24,960
ADT is domain controller.

5
00:00:25,000 --> 00:00:26,490
We have several options.

6
00:00:26,500 --> 00:00:37,630
Option 1 Windows Server 2003 Option 2 Windows Server 2008 option 3 Windows Server 2008 our 2 option

7
00:00:37,630 --> 00:00:43,540
for Windows Server 2012 R2 and to the last option.

8
00:00:43,540 --> 00:00:47,230
Option 5 is Windows Server 2016.

9
00:00:47,410 --> 00:00:54,990
As usual response here around answer the question and the answer is Option 2 Windows Server.

10
00:00:55,000 --> 00:01:02,980
Two thousand eight hundred thirty two thousand eight is the minimum recommended domain functional level

11
00:01:02,980 --> 00:01:12,190
in which you should deploy a Windows Server 2016 ADT as domain controller Windows Server 2003 is no

12
00:01:12,190 --> 00:01:21,340
longer supported although the Windows Server 2003 a domain and forest functional levels are still supported.

13
00:01:21,520 --> 00:01:28,930
You should be at the Windows Server two thousand eight functional level to ensure that since full Folder

14
00:01:28,930 --> 00:01:39,040
Replication a cure is by using distributed file system replication or the F S replication and not the

15
00:01:39,310 --> 00:01:48,070
deprecated file replication service which is f our race method that Windows Server 2003 and earlier

16
00:01:48,160 --> 00:01:56,500
used you should remove any domain controllers that are still operating on Windows Server 2003 from the

17
00:01:56,500 --> 00:02:03,320
domain prior to introducing a Windows Server 2016 domain controller.

18
00:02:03,340 --> 00:02:11,140
Now let's move on to the next question which is which of the following can use to optimize name resolution

19
00:02:11,230 --> 00:02:12,370
across their nest.

20
00:02:12,380 --> 00:02:20,650
Name spaces and again we have several options we have Option 1 which is conditional forwarders option

21
00:02:20,650 --> 00:02:31,660
to ADT the sites options 3 DNS suffix search order option for DNS stop zone and option 5 global catalogue

22
00:02:31,660 --> 00:02:32,490
servers.

23
00:02:32,650 --> 00:02:40,810
Again press pause here and think about the answer or answers which are correct for these questions and

24
00:02:40,810 --> 00:02:43,210
the answer is option 1.

25
00:02:43,210 --> 00:02:51,150
Conditional forwarders option to general suffix search order and option for DNS stop zones.

26
00:02:51,190 --> 00:02:58,840
The correct answers are conditional forwarders DNS stop zones and DNS suffix are shoulder conditional

27
00:02:58,850 --> 00:03:07,450
forwarders and then no stop zones allow you to create short cards so that name resolution doesn't have

28
00:03:07,450 --> 00:03:16,340
to reverse up and down a domain 3 and across forests by configure in a DNS suffix or shoulder.

29
00:03:16,390 --> 00:03:23,150
Clients do not have to rely on DNS devolution to resolve single label names.

30
00:03:23,260 --> 00:03:31,660
The incorrect answers are aided sites and global catalog servers although aided if sites can help you

31
00:03:31,750 --> 00:03:40,480
optimize the replication of aid it is integrated in a zones they do not inherently make name resolution

32
00:03:40,480 --> 00:03:48,310
more efficient global catalog servers are not involved in DNS name the resolution now to the section

33
00:03:48,430 --> 00:03:54,010
overview the section's name is deploying a distributed aided yes and wire amount.

34
00:03:54,310 --> 00:04:03,040
So some organizations must deploy multiple domains or even multiple forests deploy an active directory

35
00:04:03,040 --> 00:04:04,270
domain controllers.

36
00:04:04,270 --> 00:04:12,580
In this scenario is similar to deploying domain controllers in a single domain environment but you must

37
00:04:12,580 --> 00:04:20,170
consider some special factors in this section you'll learn how to deploy a complex ADT as environment

38
00:04:20,530 --> 00:04:25,920
and you will see how to upgrade from a previous version of a tedious.

39
00:04:25,990 --> 00:04:33,130
After completing this section you'll be able to describe it it is the main functional levels describe

40
00:04:33,250 --> 00:04:39,640
ADT as forest functional levels describe how to deploy new ideas domains.

41
00:04:39,640 --> 00:04:47,110
You'll be able to install a domain controller in a new domain in an existing forest and explain how

42
00:04:47,110 --> 00:04:56,920
to upgrade a previous version of ADT s to Windows Server 2016 or Windows Server 2019.

43
00:04:57,010 --> 00:05:05,950
You'll be able to explain how to migrate to Windows Server 2016 Ada yes from a previous version and

44
00:05:06,190 --> 00:05:13,150
you'll be able to describe the considerations for implementing complex HDD environments.

45
00:05:13,330 --> 00:05:14,340
So let's start.