1
00:00:01,640 --> 00:00:05,340
How do we install Windows updates on cluster nodes?

2
00:00:05,340 --> 00:00:07,010
Well, you might think, wait a minute now,

3
00:00:07,010 --> 00:00:11,740
didn't we just talk about this? I think what Microsoft is going for with this

4
00:00:11,740 --> 00:00:17,320
AZ‑801 objective is how do you install updates outside of Microsoft Update in

5
00:00:17,320 --> 00:00:21,140
Windows Server update services on your cluster nodes? Maybe you have a

6
00:00:21,140 --> 00:00:24,170
third‑party hotfix that you really need to lay in.

7
00:00:24,170 --> 00:00:29,300
So how can you simulate a rolling upgrade like we see with

8
00:00:29,300 --> 00:00:32,010
CAU? So we can use Windows PowerShell here.

9
00:00:32,010 --> 00:00:35,780
We can manually put the first node into pause or maintenance mode by

10
00:00:35,780 --> 00:00:39,540
using Suspend‑ClusterNode, as you can see here. And we can take

11
00:00:39,540 --> 00:00:43,760
advantage of the PowerShell pipeline to gather up all of the roles

12
00:00:43,760 --> 00:00:48,070
on a machine, or in this case, it's just grabbing one and moving it

13
00:00:48,070 --> 00:00:49,230
to the preferred node.

14
00:00:49,230 --> 00:00:53,270
So we're piping into Move‑ClusterGroup, as you can see. The idea, then

15
00:00:53,270 --> 00:00:57,940
is we would install or patch that first node, restart if we need to,

16
00:00:57,940 --> 00:01:02,720
unpause the node with Resume‑ClusterNode. And then, depending upon

17
00:01:02,720 --> 00:01:04,460
whether we had failback or not,

18
00:01:04,460 --> 00:01:09,550
if not, we could do a Move‑ClusterGroup to bring those roles back to the node,

19
00:01:09,550 --> 00:01:15,740
and then we would just iterate and do a suspend on node2.

20
00:01:15,740 --> 00:01:20,820
Lastly, before our demo, we have a nod to Windows Admin Center. And this is

21
00:01:20,820 --> 00:01:25,170
the latest vanguard in Windows Server Management Tools and, of course, it's

22
00:01:25,170 --> 00:01:29,110
biggest advantage is that it's browser‑based, so accessible on just about

23
00:01:29,110 --> 00:01:34,100
any kind of device, also updatable, as you can see, and there's also a

24
00:01:34,100 --> 00:01:37,330
dedicated cluster UI. You don't want to forget about that. We'll see that

25
00:01:37,330 --> 00:01:38,340
in the demo, too.

26
00:01:38,340 --> 00:01:41,400
But yeah, the extension model is the best feature,

27
00:01:41,400 --> 00:01:46,280
in my opinion, besides its universality where we can get patches to the

28
00:01:46,280 --> 00:01:52,470
capabilities and true extensions to capabilities in WAC in a much faster way

29
00:01:52,470 --> 00:01:58,020
than you can with the old compiled MMCs. We also see heavy emphasis on Azure

30
00:01:58,020 --> 00:02:02,800
integration within Windows Admin Center. It makes sense. And then we have

31
00:02:02,800 --> 00:02:05,000
Settings, and I just want to call out here.

32
00:02:05,000 --> 00:02:09,640
You'll see this yourself before too long that the WAC is not yet

33
00:02:09,640 --> 00:02:13,450
anywhere near in parity with the Microsoft Management Console. It

34
00:02:13,450 --> 00:02:16,140
contains a subset of those capabilities.

35
00:02:16,140 --> 00:02:21,000
So, we look at WAC for what it is. Let's get into that demo.