WEBVTT

1
00:00.000 --> 00:03.300
So our first step is right here to verify our topology.

2
00:03.300 --> 00:06.140
I currently have the Windows Server up and running.

3
00:06.140 --> 00:08.100
Let's verify its IP address.

4
00:08.100 --> 00:10.160
Let's also verify the user accounts

5
00:10.160 --> 00:12.300
currently configured on that server.

6
00:12.300 --> 00:14.000
Here in the vSphere client,

7
00:14.000 --> 00:15.840
here is that server right there.

8
00:15.840 --> 00:18.980
The server itself has VMware Tools running.

9
00:18.980 --> 00:22.220
Let's go ahead and open up a remote console to that Windows Server.

10
00:22.220 --> 00:24.680
Here is that Windows Server right here.

11
00:24.680 --> 00:28.640
Let's just go to a command prompt real quick and verify its IP address.

12
00:28.640 --> 00:30.340
So if we do an IP config,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:28.640 --> 00:30.340
So if we do an IP config,

13
00:30.340 --> 00:33.200
its IP address is 1010, 100 fantastic.

14
00:33.200 --> 00:35.560
It's default gateway is 101.

15
00:35.560 --> 00:37.400
Let's also do a trace route.

16
00:37.400 --> 00:40.740
I'll say don't bother doing the name resolution on the way out to 8888.

17
00:40.740 --> 00:44.520
Just verify we have internet connectivity and that's looking good.

18
00:44.520 --> 00:47.640
That's great. I'll go ahead and do a control C to stop that.

19
00:47.640 --> 00:52.560
Let's also verify name resolution with a ping to www.google.com.

20
00:52.560 --> 00:54.240
All right, that looks great.

21
00:54.240 --> 00:58.420
Before we bring our client up and here's our Windows 11 client.

22
00:58.420 --> 01:00.020
Let me just verify where it's connected.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:58.420 --> 01:00.020
Let me just verify where it's connected.

23
01:00.020 --> 01:03.480
So it shows here that is connected to segment 10 yellow.

24
01:03.480 --> 01:04.420
Fantastic.

25
01:04.420 --> 01:07.520
Shows us disconnected at the moment because it's not powered on.

26
01:07.520 --> 01:08.720
Then if we look up here,

27
01:08.720 --> 01:11.500
it says VMware Tools is not installed.

28
01:11.500 --> 01:12.600
So we want to fix that,

29
01:12.600 --> 01:14.800
make sure we do install VMware Tools.

30
01:14.800 --> 01:16.240
But before we power this up,

31
01:16.240 --> 01:20.520
I also want to make sure that our NSX environment is providing the correct DNS

32
01:20.520 --> 01:21.000
server.

33
01:21.000 --> 01:24.800
By correct, I mean we want this DHCP client when it gets an IP address.

34
01:24.800 --> 01:29.060
To also as one of the options, learn that the DNS server it should be using is

35
01:29.060 --> 01:30.780
right here at dot 100.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:29.060 --> 01:30.780
right here at dot 100.

36
01:30.780 --> 01:34.980
So let's go to this segment and we'll modify the DHCP services here from NSX

37
01:34.980 --> 01:40.020
to say that the DNS server should be the server at 10, 10, 0, 100.

38
01:40.020 --> 01:41.980
And that way when this client gets an IP address,

39
01:41.980 --> 01:45.380
it'll actually be using the correct DNS server here in the domain.

40
01:45.380 --> 01:49.020
So to do that, we'll go to the NSX manager, we'll go to networking.

41
01:49.020 --> 01:52.820
And with the networking tab selected on the left, we'll click on segments.

42
01:52.820 --> 01:56.460
And then we'll go ahead and edit segment 10 right here by clicking on the three

43
01:56.460 --> 01:56.740
dots

44
01:56.740 --> 01:58.880
and then clicking on edit.

45
01:58.880 --> 02:00.540
Then to edit our DHCP services,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
01:58.880 --> 02:00.540
Then to edit our DHCP services,

46
02:00.540 --> 02:03.480
we'll click right here and edit DHCP config right here.

47
02:03.480 --> 02:07.800
And then here we'll specify that for the DNS server instead of using 8888.

48
02:07.800 --> 02:09.760
I'll click on the X to remove that.

49
02:09.760 --> 02:12.820
Let's go ahead and use 10 dot 10 dot 0 dot 100.

50
02:12.820 --> 02:14.320
And then we'll click on apply.

51
02:14.320 --> 02:16.760
And then we'll scroll down and click on save.

52
02:16.760 --> 02:18.660
And then we'll click on close editing.

53
02:18.660 --> 02:22.500
So none of we have for segment 10 or DHCP services that are handing out the

54
02:22.500 --> 02:23.160
correct DNS

55
02:23.160 --> 02:25.020
server that we want that client to use.

56
02:25.020 --> 02:26.020
Let's go ahead and close that.

57
02:26.020 --> 02:27.980
And let's go back to the vSphere client.

58
02:27.980 --> 02:31.540
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

58
02:27.980 --> 02:31.540
And let's go to our Windows 11 client here and we'll power it on.

59
02:31.540 --> 02:35.520
And then one of the first things we'll do after powering this on is we'll log

60
02:35.520 --> 02:36.060
on and

61
02:36.060 --> 02:39.490
we'll install VMware tools because without it, we're not going to have the

62
02:39.490 --> 02:40.140
guest intro

63
02:40.140 --> 02:44.330
spectrum, the ability to communicate to the NSX manager about the fact that we

64
02:44.330 --> 02:44.780
just logged

65
02:44.780 --> 02:46.460
on to Active Directory.

66
02:46.460 --> 02:49.560
And NSX needs to know that we logged into Active Directory so we can then

67
02:49.560 --> 02:50.460
further identify

68
02:50.460 --> 02:52.180
what groups were part of.

69
02:52.180 --> 02:55.410
And then based on those 80 groups, if those are nested or part of our NSX

70
02:55.410 --> 02:56.140
groups, then

71
02:56.140 --> 03:00.350
those NSX group memberships can then be used successfully as part of our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
02:56.140 --> 03:00.350
those NSX group memberships can then be used successfully as part of our

72
03:00.350 --> 03:01.460
firewall policy

73
03:01.460 --> 03:02.460
rules.

74
03:02.460 --> 03:05.620
So let's open up a remote console over to our Windows 11 client.

75
03:05.620 --> 03:06.940
So here is that remote console.

76
03:06.940 --> 03:11.460
So I'm going to log on as AD dash NSX dash user to also play the password for

77
03:11.460 --> 03:12.420
that and

78
03:12.420 --> 03:14.700
click on the arrow to log in.

79
03:14.700 --> 03:19.280
So while we're logging in here, we can also verify over at the Windows server

80
03:19.280 --> 03:20.020
in the security

81
03:20.020 --> 03:24.630
logs that we are actually logging in to the domain and not just logging on

82
03:24.630 --> 03:25.460
locally.

83
03:25.460 --> 03:28.520
So if we bring back our server right here, let me go ahead and close the

84
03:28.520 --> 03:29.340
command prompt

85
03:29.340 --> 03:32.690
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

85
03:29.340 --> 03:32.690
and from the server manager, let's click on tools and from the drop down, we'll

86
03:32.690 --> 03:32.980
click

87
03:32.980 --> 03:35.140
on event viewer right there.

88
03:35.140 --> 03:36.980
And let me make this a little bit bigger.

89
03:36.980 --> 03:41.140
So here in event viewer, we'll go to our Windows logs, we'll click on security

90
03:41.140 --> 03:41.260
and it

91
03:41.260 --> 03:43.740
says there's over 9000 new events available.

92
03:43.740 --> 03:46.940
I'm going to go ahead and I'm going to clear the log.

93
03:46.940 --> 03:49.340
So that's in the process of clearing the logs.

94
03:49.340 --> 03:53.020
And then here I'll click on clear and let me go ahead and log in one more time.

95
03:53.020 --> 03:54.860
So go to their client machine right here.

96
03:54.860 --> 03:58.700
I'll go ahead and log out as 80 NSX user to.

97
03:58.700 --> 04:01.940
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

97
03:58.700 --> 04:01.940
So we'll sign out there and then we'll log in once more.

98
04:01.940 --> 04:02.940
All right.

99
04:02.940 --> 04:06.630
So we'll go ahead and log back in and we'll go back to our event viewer and we

100
04:06.630 --> 04:07.180
go ahead

101
04:07.180 --> 04:08.620
and refresh this.

102
04:08.620 --> 04:10.020
So there's our latest log on right there.

103
04:10.020 --> 04:12.700
I'll highlight that and let's take a look at the details.

104
04:12.700 --> 04:16.680
So if we scroll down here in the details and if we scroll down, that wasn't

105
04:16.680 --> 04:17.420
that user.

106
04:17.420 --> 04:19.140
Let me go ahead and find the next one.

107
04:19.140 --> 04:20.620
There's another log on right there.

108
04:20.620 --> 04:25.190
We'll scroll down and sure enough, there we have 80 NSX user to that's logged

109
04:25.190 --> 04:25.700
on to

110
04:25.700 --> 04:26.700
the domain.

111
04:26.700 --> 04:29.340
I just want to confirm that we are really logging on to the domain.

112
04:29.340 --> 04:30.700
So that part looks great.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

112
04:29.340 --> 04:30.700
So that part looks great.

113
04:30.700 --> 04:33.880
So I'm going to minimize our Windows server and our next step would be to

114
04:33.880 --> 04:34.660
install VMware

115
04:34.660 --> 04:35.660
tools.

116
04:35.660 --> 04:39.970
So I'm going to go ahead under actions and click install VMware tools and say

117
04:39.970 --> 04:40.540
mount to

118
04:40.540 --> 04:45.380
mount the CD on that VM and then we'll go install VMware tools on that VM.

119
04:45.380 --> 04:49.230
So back to the Windows client here, we'll simply go to the file system by

120
04:49.230 --> 04:49.660
clicking on

121
04:49.660 --> 04:54.930
explore, then I'll click on the DVD drive that just got mounted by vSphere and

122
04:54.930 --> 04:55.460
I'll run

123
04:55.460 --> 04:58.780
setup 64 to install the VMware tools.

124
04:58.780 --> 05:01.500
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

124
04:58.780 --> 05:01.500
And we also center this and make it a little bit bigger as well.

125
05:01.500 --> 05:02.500
All right.

126
05:02.500 --> 05:04.700
So we'll confirm that we want to do the installation.

127
05:04.700 --> 05:07.860
So here in the wizard for the install, we'll go ahead and click on next to

128
05:07.860 --> 05:08.500
continue.

129
05:08.500 --> 05:11.900
And now it's asking us to go to typical complete or custom.

130
05:11.900 --> 05:15.590
So if we want all the bells and whistles, including the ones that provide guest

131
05:15.590 --> 05:16.980
introspection

132
05:16.980 --> 05:20.470
that NSX needs, we could choose complete or we could use custom and then make

133
05:20.470 --> 05:20.820
sure we

134
05:20.820 --> 05:21.820
choose the right option.

135
05:21.820 --> 05:25.420
So if we use custom here and click on next everywhere there's an X, those are

136
05:25.420 --> 05:26.020
not being

137
05:26.020 --> 05:27.020
installed.

138
05:27.020 --> 05:31.350
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

138
05:27.020 --> 05:31.350
So if we scroll down here to the VMCI driver, notice here that we do not have

139
05:31.350 --> 05:32.060
by default

140
05:32.060 --> 05:35.780
the NSX network introspection driver that's going to be installed.

141
05:35.780 --> 05:40.050
And we want that to be installed so that NSX can be aware of this VM as it's

142
05:40.050 --> 05:40.620
logging

143
05:40.620 --> 05:41.620
onto a domain.

144
05:41.620 --> 05:44.560
So I'm going to click on back and I'm going to do the complete install, which

145
05:44.560 --> 05:45.180
will include

146
05:45.180 --> 05:46.420
all those options.

147
05:46.420 --> 05:50.160
So we'll go ahead and choose complete, click on next, click on install and then

148
05:50.160 --> 05:50.620
give that

149
05:50.620 --> 05:54.920
a few minutes for it to complete and it's going to ask us to reboot this VM,

150
05:54.920 --> 05:55.180
which we

151
05:55.180 --> 05:56.500
will also do.

152
05:56.500 --> 05:59.490
And through the magic of editing, this is going to be the fastest complete

153
05:59.490 --> 06:00.100
install of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

153
05:59.490 --> 06:00.100
install of

154
06:00.100 --> 06:01.940
VMware tools on the planet.

155
06:01.940 --> 06:02.940
All right.

156
06:02.940 --> 06:08.140
So on here it says VMware tools updated, including the introspection component.

157
06:08.140 --> 06:10.720
And it also mentioned that in order to have that take effect, we need to go

158
06:10.720 --> 06:11.180
ahead and

159
06:11.180 --> 06:12.180
reboot.

160
06:12.180 --> 06:15.080
So I'll click on finish here and then we'll go ahead and click on yes and

161
06:15.080 --> 06:15.620
reboot this

162
06:15.620 --> 06:16.620
VM.

163
06:16.620 --> 06:18.940
So we'll get that a moment to go ahead and reboot.

164
06:18.940 --> 06:22.210
So once it comes back up and fully initializes, we'll have this version of

165
06:22.210 --> 06:23.300
VMware tools running

166
06:23.300 --> 06:28.220
on that VM, which includes the components for this VM to report to the NSX

167
06:28.220 --> 06:28.880
manager

168
06:28.880 --> 06:31.480
about it logging on to active directory.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
06:28.880 --> 06:31.480
about it logging on to active directory.

169
06:31.480 --> 06:36.940
So based on our game plan, we have verified that our DHCP client is good to go.

170
06:36.940 --> 06:39.000
We've got VMware tools installed on it.

171
06:39.000 --> 06:41.540
It's logging into the active directory correctly.

172
06:41.540 --> 06:43.840
So our next logical step then is right here.

173
06:43.840 --> 06:49.150
And that is to train NSX on how to interact and work with this Windows active

174
06:49.150 --> 06:50.020
directory

175
06:50.020 --> 06:52.240
server, which is also supporting LDAP.

176
06:52.240 --> 06:55.650
So we'll do that integration between NSX and our active directory environment

177
06:55.650 --> 06:56.020
in the

178
06:56.020 --> 06:57.420
very next video.

179
06:57.420 --> 06:59.020
I'll see you there in just a moment.