Let's have a brief overview of this section content.
But before we begin traditional let's start with several questions.
Question 1 What is the minimum domain functional level in which you should deploy a Windows Server 2016
ADT is domain controller.
We have several options.
Option 1 Windows Server 2003 Option 2 Windows Server 2008 option 3 Windows Server 2008 our 2 option
for Windows Server 2012 R2 and to the last option.
Option 5 is Windows Server 2016.
As usual response here around answer the question and the answer is Option 2 Windows Server.
Two thousand eight hundred thirty two thousand eight is the minimum recommended domain functional level
in which you should deploy a Windows Server 2016 ADT as domain controller Windows Server 2003 is no
longer supported although the Windows Server 2003 a domain and forest functional levels are still supported.
You should be at the Windows Server two thousand eight functional level to ensure that since full Folder
Replication a cure is by using distributed file system replication or the F S replication and not the
deprecated file replication service which is f our race method that Windows Server 2003 and earlier
used you should remove any domain controllers that are still operating on Windows Server 2003 from the
domain prior to introducing a Windows Server 2016 domain controller.
Now let's move on to the next question which is which of the following can use to optimize name resolution
across their nest.
Name spaces and again we have several options we have Option 1 which is conditional forwarders option
to ADT the sites options 3 DNS suffix search order option for DNS stop zone and option 5 global catalogue
servers.
Again press pause here and think about the answer or answers which are correct for these questions and
the answer is option 1.
Conditional forwarders option to general suffix search order and option for DNS stop zones.
The correct answers are conditional forwarders DNS stop zones and DNS suffix are shoulder conditional
forwarders and then no stop zones allow you to create short cards so that name resolution doesn't have
to reverse up and down a domain 3 and across forests by configure in a DNS suffix or shoulder.
Clients do not have to rely on DNS devolution to resolve single label names.
The incorrect answers are aided sites and global catalog servers although aided if sites can help you
optimize the replication of aid it is integrated in a zones they do not inherently make name resolution
more efficient global catalog servers are not involved in DNS name the resolution now to the section
overview the section's name is deploying a distributed aided yes and wire amount.
So some organizations must deploy multiple domains or even multiple forests deploy an active directory
domain controllers.
In this scenario is similar to deploying domain controllers in a single domain environment but you must
consider some special factors in this section you'll learn how to deploy a complex ADT as environment
and you will see how to upgrade from a previous version of a tedious.
After completing this section you'll be able to describe it it is the main functional levels describe
ADT as forest functional levels describe how to deploy new ideas domains.
You'll be able to install a domain controller in a new domain in an existing forest and explain how
to upgrade a previous version of ADT s to Windows Server 2016 or Windows Server 2019.
You'll be able to explain how to migrate to Windows Server 2016 Ada yes from a previous version and
you'll be able to describe the considerations for implementing complex HDD environments.
So let's start.