Once root DC1 comes back from its reboot, it will be a
fully functional domain controller.
I've configured DHCP, or Dynamic Host Configuration Protocol, so that all
machines in the domain now have connectivity to that DNS server.
I'm on a Windows 11 workstation right now,
and if we look at my IP config output,
we can see that for DNS servers I'm pointed to 10.1.0.10; that is root DC2.
So let's join the domain on this Windows 11 box.
I'm going to open up Search, and I just go the long way around, honestly.
I'm going to open up good old‑fashioned Control Panel.
This is just my curmudgeonly behavior showing up.
I'll do a search for join and we'll join the domain.
I like to do it the good old‑fashioned way.
We'll go to Change in the System Properties control panel, and for the
computer name it's cli1, but the domain is timw.info.
Because we have DNS connectivity, we now are asked
for a domain administrator account, which I will provide.
Let me get rid of this control panel here.
Welcome to the domain.
This is all familiar to you, I'm quite sure.
Then we're going to reboot this client, and when we come
back, we'll sign in using a domain account.
And now that I'm signed into the domain on that Windows 11 client machine,
I'm going to show you how to install the RSAT tools.
Again, I'll open up Start and do a search for optional and grab Optional
features from System settings and then add an optional feature.
We're going to do View features.
And if I do a search for RSAT,
we've got a whole bunch of Remote Server Administration Tools.
Now in Windows 10, you still have to install these separately
from the Microsoft Download Center, but Windows 11 has them baked
right into the operating system here.
And I'm going to grab them all. Even though I may not necessarily need them all,
at least I've got them.
So let me select them and click Next.
I'm also going to install Windows Admin Center on this Windows 11 box.
Now,
some things to keep in mind. That is on the exam objectives, so
it's important that you know some stuff about it.
And as you can see, all those RSAT tools are installing.
Download the Windows Admin Center installer from the Microsoft Eval Center.
When you install WAC on a server,
it gets installed as a service, and then you
centrally can connect to that gateway.
I'm installing WAC locally on this machine because you cannot
install Windows Admin Center on domain controllers.
So I'm just going to install it here, just basically doing a Next, Next, Finish.
I am going to choose to update WAC with Microsoft Update.
WAC, by the way, is a browser‑based administration tool.
And as you can see here, it listens on 6516 as the default site on a workstation.
On a server, it would be 443.
Notice that we can modify the machine's trusted hosts list.
I'm going to do Install here.
And this will give us a nice, centralized point of administration
from our client machine throughout the domain,
as long as we have proper credentials.
And specifically, what I'm going to do is make a connection
to my other domain controller, root DC2,
and we're going to install Active Directory Domain Services through WAC.
Then we'll connect to the server and finish the promotion.
Now by default, Windows Admin Center is going to use a self‑signed certificate.
This is an important point and an exam alert to consider.
When you're installing WAC as a gateway service on a server,
on a domain member server, you'll not want to use the self‑signed certificates.
So the way that you do that is that you can start using the
self‑signed certificate, and then when you're ready to use
your production SSL/TLS certificate,
you rerun the installer and you choose Change as an option.
That's what we've got.
So for here, let me click Finish. And as mentioned here,
we're just using the self‑signed certificate for SSL. We're just on the local machine anyway, so it's not that big of a deal.