So our first step is right here to verify our topology.
I currently have the Windows Server up and running.
Let's verify its IP address.
Let's also verify the user accounts
currently configured on that server.
Here in the vSphere client,
here is that server right there.
The server itself has VMware Tools running.
Let's go ahead and open up a remote console to that Windows Server.
Here is that Windows Server right here.
Let's just go to a command prompt real quick and verify its IP address.
So if we do an IP config, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we do an IP config,
its IP address is 1010, 100 fantastic.
It's default gateway is 101.
Let's also do a trace route.
I'll say don't bother doing the name resolution on the way out to 8888.
Just verify we have internet connectivity and that's looking good.
That's great. I'll go ahead and do a control C to stop that.
Let's also verify name resolution with a ping to www.google.com.
All right, that looks great.
Before we bring our client up and here's our Windows 11 client.
Let me just verify where it's connected. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let me just verify where it's connected.
So it shows here that is connected to segment 10 yellow.
Fantastic.
Shows us disconnected at the moment because it's not powered on.
Then if we look up here,
it says VMware Tools is not installed.
So we want to fix that,
make sure we do install VMware Tools.
But before we power this up,
I also want to make sure that our NSX environment is providing the correct DNS
server.
By correct, I mean we want this DHCP client when it gets an IP address.
To also as one of the options, learn that the DNS server it should be using is
right here at dot 100. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
right here at dot 100.
So let's go to this segment and we'll modify the DHCP services here from NSX
to say that the DNS server should be the server at 10, 10, 0, 100.
And that way when this client gets an IP address,
it'll actually be using the correct DNS server here in the domain.
So to do that, we'll go to the NSX manager, we'll go to networking.
And with the networking tab selected on the left, we'll click on segments.
And then we'll go ahead and edit segment 10 right here by clicking on the three
dots
and then clicking on edit.
Then to edit our DHCP services, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Then to edit our DHCP services,
we'll click right here and edit DHCP config right here.
And then here we'll specify that for the DNS server instead of using 8888.
I'll click on the X to remove that.
Let's go ahead and use 10 dot 10 dot 0 dot 100.
And then we'll click on apply.
And then we'll scroll down and click on save.
And then we'll click on close editing.
So none of we have for segment 10 or DHCP services that are handing out the
correct DNS
server that we want that client to use.
Let's go ahead and close that.
And let's go back to the vSphere client.
And let's go to our Windows 11 client here and we'll power it on. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's go to our Windows 11 client here and we'll power it on.
And then one of the first things we'll do after powering this on is we'll log
on and
we'll install VMware tools because without it, we're not going to have the
guest intro
spectrum, the ability to communicate to the NSX manager about the fact that we
just logged
on to Active Directory.
And NSX needs to know that we logged into Active Directory so we can then
further identify
what groups were part of.
And then based on those 80 groups, if those are nested or part of our NSX
groups, then
those NSX group memberships can then be used successfully as part of our WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
those NSX group memberships can then be used successfully as part of our
firewall policy
rules.
So let's open up a remote console over to our Windows 11 client.
So here is that remote console.
So I'm going to log on as AD dash NSX dash user to also play the password for
that and
click on the arrow to log in.
So while we're logging in here, we can also verify over at the Windows server
in the security
logs that we are actually logging in to the domain and not just logging on
locally.
So if we bring back our server right here, let me go ahead and close the
command prompt
and from the server manager, let's click on tools and from the drop down, we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and from the server manager, let's click on tools and from the drop down, we'll
click
on event viewer right there.
And let me make this a little bit bigger.
So here in event viewer, we'll go to our Windows logs, we'll click on security
and it
says there's over 9000 new events available.
I'm going to go ahead and I'm going to clear the log.
So that's in the process of clearing the logs.
And then here I'll click on clear and let me go ahead and log in one more time.
So go to their client machine right here.
I'll go ahead and log out as 80 NSX user to.
So we'll sign out there and then we'll log in once more. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll sign out there and then we'll log in once more.
All right.
So we'll go ahead and log back in and we'll go back to our event viewer and we
go ahead
and refresh this.
So there's our latest log on right there.
I'll highlight that and let's take a look at the details.
So if we scroll down here in the details and if we scroll down, that wasn't
that user.
Let me go ahead and find the next one.
There's another log on right there.
We'll scroll down and sure enough, there we have 80 NSX user to that's logged
on to
the domain.
I just want to confirm that we are really logging on to the domain.
So that part looks great. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So that part looks great.
So I'm going to minimize our Windows server and our next step would be to
install VMware
tools.
So I'm going to go ahead under actions and click install VMware tools and say
mount to
mount the CD on that VM and then we'll go install VMware tools on that VM.
So back to the Windows client here, we'll simply go to the file system by
clicking on
explore, then I'll click on the DVD drive that just got mounted by vSphere and
I'll run
setup 64 to install the VMware tools.
And we also center this and make it a little bit bigger as well. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we also center this and make it a little bit bigger as well.
All right.
So we'll confirm that we want to do the installation.
So here in the wizard for the install, we'll go ahead and click on next to
continue.
And now it's asking us to go to typical complete or custom.
So if we want all the bells and whistles, including the ones that provide guest
introspection
that NSX needs, we could choose complete or we could use custom and then make
sure we
choose the right option.
So if we use custom here and click on next everywhere there's an X, those are
not being
installed.
So if we scroll down here to the VMCI driver, notice here that we do not have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we scroll down here to the VMCI driver, notice here that we do not have
by default
the NSX network introspection driver that's going to be installed.
And we want that to be installed so that NSX can be aware of this VM as it's
logging
onto a domain.
So I'm going to click on back and I'm going to do the complete install, which
will include
all those options.
So we'll go ahead and choose complete, click on next, click on install and then
give that
a few minutes for it to complete and it's going to ask us to reboot this VM,
which we
will also do.
And through the magic of editing, this is going to be the fastest complete
install of WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
install of
VMware tools on the planet.
All right.
So on here it says VMware tools updated, including the introspection component.
And it also mentioned that in order to have that take effect, we need to go
ahead and
reboot.
So I'll click on finish here and then we'll go ahead and click on yes and
reboot this
VM.
So we'll get that a moment to go ahead and reboot.
So once it comes back up and fully initializes, we'll have this version of
VMware tools running
on that VM, which includes the components for this VM to report to the NSX
manager
about it logging on to active directory. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
about it logging on to active directory.
So based on our game plan, we have verified that our DHCP client is good to go.
We've got VMware tools installed on it.
It's logging into the active directory correctly.
So our next logical step then is right here.
And that is to train NSX on how to interact and work with this Windows active
directory
server, which is also supporting LDAP.
So we'll do that integration between NSX and our active directory environment
in the
very next video.
I'll see you there in just a moment.