[Autogenerated] today vocalizations king.
And if we're running with virtualized to
being controllers, we can take advantage
of domain controller Cloning Domain
controller Cloning allows us to rapidly
deploy demand controllers. Essentially,
we're gonna take a copy of an existing
turbine controller and use that cop It
create new demand controls where they're
needed. You will use the existing very
excite domain controller as part of your
job in control of cloning. Once you've
created the clone, the demand control
you've copied can retake its place on the
network. But we won't. There is downtime
here during the final steps of domain
controller Cloning your virtualized been
control. We need to be shut down. Export
and import uses part the cloning process
we export from the sauce D C. We then take
those exploit files and copy them to a new
hyper visor host and use them to impart to
create a brand new voting machine.
Throughout this process, there are no need
to use tools like six prep or any of a
generalization tools a few pre records
after he met. First of all, the demand
control. Your clowning must be a member of
a group called the KD Laudable Demand
controllers group. It's not a member of
that group. The cloning process will not
work. We have power Shell to create the
clone, and it's important to know the P D
simulator will must be on the Windows 2012
hour higher demand control backing. Seven.
Manager on my management desktop We're
gonna create a remote desktop connection
to D. C. On D. C. I have a powershell
script called D. C Clone that I'm going to
right Click Han SE at it. This will open
up this script in Power Shell. I see now
the D C machine is a member off the
Clinical Demand Controls group on the PDC,
Emilia eats on the 2012 R hire machine. In
fact, it's on our 2019 machine. There's
three commands here that we can use to
create a clone. The first is they get Dash
A D. D. C. Cloning excluded application
list. What this command is going to do is
look at the installed applications of
service, is on this computer and generate
a list off. Any service is that are not
supported by the cloning process. So if I
put my Custer in the line, but then used
the button to generate this list. This is
quite a long list that it's created. This
is a list of service is that might not
survive the cloning process. We have two
options at this point. We can even remove.
These. Service is so they don't interfere.
The cloning process. Oh, if he's a Customs
service is that you know will survive the
cloning process. Then you can run Line
five. Lying five is the same command with
this generate ex Mel at the end. If we
were in this line, he creates XML file,
but it places in the same folder that
contains your auntie desk dot dit
database. Now this generate, expel fouled.
The complete list of those service is this
is a signal to the cloning process to say
anything that's in this file. Just ignore.
We know so by the process. So you don't
have to worry about if you don't end with
this file and you have a list of service
is that the cloning process doesn't
support it will prevent the cloning
process from taking place. If you're happy
with your list of service is if you're
happy that they will survive or you've
removed service is that won't survive.
Then the next command is line eight New A.
D D. C. Clone comfort file. This command
could be run as is, and this will create a
clone configuration file that's pretty
empty. What we can do is use various
prominence at this point to add i p
addresses from the machine. New names for
new machines, Theoneste service Vending
machine, the weather we're rolling out. If
you don't include any other properties,
then it will just create this generic file
that comm used over and over again on
things like computer names. I P addresses
will then be run to the generated obtained
from service like th E P service. Where
you going? Quite empty file. So 51 Line
eight. It forms a series of check if I'll
create in my clone complete file. If we
met the screen little bit bigger and then
scroll up. First of all, we can see it.
Look the P D. Similar role and verified
that that world was on 2012 or later
server. Then check to make sure this
server was a member off the clinical
demand controls group, and then it looked
for exclude applications on exclude
application list Once all those checks are
being passed, then generate the clone
conflict file called D. C Clone Conflict X
amount. And again it placed in the same
folder that contained your Auntie
Destructive Davis. At this point, we're
almost there. What we need to do now is
shook DC down. If you don't shut d C down,
then the cloning process won't work. Shut
the machine down there. We need to go to
the management to your particular
virtualization platform. For me, that's
hyper V. So Aaron, like three manager with
our three d C's in D. C, is shut down.
Readyto finalize the cloning process so
I'll need to do now is right with the D.
C. On choose export ones. Exploit these
files become our clone configuration. In
this model, you have learned how to deploy
distant event controllers Using stall for
media, we used a cell for media to deploy
a read on domain controller. The redone
domain controller was running Windows
Server car. We've also discussed them in
control of cloning and the benefit of
being able to wrap up the deploy demand
control issue environment and our next
model will discuss active directory sites
and service is on active dirt replication,
General. So join me. Next module on, we'll
continue our active directory domain service, his journey.