1
00:00:01,140 --> 00:00:04,550
Let's get this party started. In this demonstration, we'll start with

2
00:00:04,550 --> 00:00:08,420
cluster‑aware updating, and we'll look at failing over, failing back

3
00:00:08,420 --> 00:00:12,150
workloads, and then we'll finish with a flourish by examining Windows

4
00:00:12,150 --> 00:00:15,760
Admin Center cluster administration. It doesn't really matter what

5
00:00:15,760 --> 00:00:16,540
machine we're on.

6
00:00:16,540 --> 00:00:18,280
But as you can see from the title bar,

7
00:00:18,280 --> 00:00:21,930
I am on mem1, one of my domain member servers.

8
00:00:21,930 --> 00:00:25,240
This is a Windows Server 2022 box.

9
00:00:25,240 --> 00:00:28,810
And let me start by opening up Server Manager. And

10
00:00:28,810 --> 00:00:31,160
while we wait for it to initialize,

11
00:00:31,160 --> 00:00:35,880
that's part of the deal, let's open up Tools and see if I can get to, yes,

12
00:00:35,880 --> 00:00:39,370
indeed, we have Cluster‑Aware Updating. And this is

13
00:00:39,370 --> 00:00:42,660
available because I have the failover cluster roles and

14
00:00:42,660 --> 00:00:45,240
RSAT tools installed on this machine.

15
00:00:45,240 --> 00:00:49,750
Let's start by connecting to my AZ‑801 cluster, and it gives us

16
00:00:49,750 --> 00:00:53,630
some potentially scary, but not really scary information. This not

17
00:00:53,630 --> 00:00:57,900
available is never a good thing to say to an administrator, but

18
00:00:57,900 --> 00:01:01,670
that's just saying that we haven't run any cluster or updating jobs

19
00:01:01,670 --> 00:01:03,140
on the cluster yet.

20
00:01:03,140 --> 00:01:06,810
Let's go to Preview updates for this cluster, and then we can see

21
00:01:06,810 --> 00:01:09,490
our available plugins. I'm going to select the

22
00:01:09,490 --> 00:01:13,210
Microsoft.WindowsUpdatePlugin, and then we'll generate an update

23
00:01:13,210 --> 00:01:17,140
preview list by clicking the appropriate button.

24
00:01:17,140 --> 00:01:18,580
Not too much going on here.

25
00:01:18,580 --> 00:01:21,880
It looks like both of my cluster nodes need the same

26
00:01:21,880 --> 00:01:25,070
Microsoft Defender security intelligence update.

27
00:01:25,070 --> 00:01:26,540
That's not too bad.

28
00:01:26,540 --> 00:01:31,130
Now let's see. We can do an interactive apply updates to this cluster run,

29
00:01:31,130 --> 00:01:34,820
we can create or modify an updating run profile,

30
00:01:34,820 --> 00:01:40,240
we can generate a report on past cluster runs, as you can see here.

31
00:01:40,240 --> 00:01:44,640
Not much to see, but once we have something, we can export it.

32
00:01:44,640 --> 00:01:48,480
We can configure cluster self‑updating options, and then we

33
00:01:48,480 --> 00:01:53,240
can analyze cluster updating readiness.

34
00:01:53,240 --> 00:01:55,480
That's actually a really nice step 0.

35
00:01:55,480 --> 00:02:00,340
I'm surprised that that option isn't at the top of the cluster actions list.

36
00:02:00,340 --> 00:02:02,940
So it looks like I have a couple warnings here.

37
00:02:02,940 --> 00:02:05,740
Oh, this last one is actually pretty important.

38
00:02:05,740 --> 00:02:10,230
It says the CAU clustered role should be installed on the failover cluster

39
00:02:10,230 --> 00:02:15,660
to enable self‑updating mode. That's really important, so let's do that

40
00:02:15,660 --> 00:02:19,640
right now, Configure cluster self‑updating options.

41
00:02:19,640 --> 00:02:23,160
And let's see here. It says that after we configure this mode,

42
00:02:23,160 --> 00:02:27,070
we do not need to explicitly initiate update runs anymore.

43
00:02:27,070 --> 00:02:29,530
They'll be initiated automatically on a schedule.

44
00:02:29,530 --> 00:02:32,540
Now does it make sense that the cluster‑aware updating

45
00:02:32,540 --> 00:02:35,270
feature is itself going to be highly available?

46
00:02:35,270 --> 00:02:40,620
That's why we need to create a clustered role specifically for CAU. And

47
00:02:40,620 --> 00:02:43,630
what's cool is that with just a couple clicks of the mouse,

48
00:02:43,630 --> 00:02:48,140
we can instruct this wizard to create that role for us.

49
00:02:48,140 --> 00:02:51,840
So let's add the CAU clustered role, click Next.

50
00:02:51,840 --> 00:02:57,310
This is where we can specify our self‑updating metadata, as you can see, daily,

51
00:02:57,310 --> 00:03:00,140
weekly or monthly cadence.

52
00:03:00,140 --> 00:03:03,940
Here's where we can change just some properties and metadata. We don't need to

53
00:03:03,940 --> 00:03:07,650
get to this level of granularity for the exam. Of course,

54
00:03:07,650 --> 00:03:08,460
in the real world,

55
00:03:08,460 --> 00:03:10,820
you want to go out into the docs and understand the

56
00:03:10,820 --> 00:03:14,240
implication of all of these advanced options.

57
00:03:14,240 --> 00:03:17,160
Additional options, not too much to choose from here.

58
00:03:17,160 --> 00:03:21,540
Give me recommended updates the same way I receive important updates,

59
00:03:21,540 --> 00:03:22,430
Confirmation,

60
00:03:22,430 --> 00:03:27,310
Apply. And at this point, CAU is being made highly available in the

61
00:03:27,310 --> 00:03:32,090
cluster, and every month on that schedule it will do its update

62
00:03:32,090 --> 00:03:35,890
automatically. Now, you can always come back and rerun that wizard if you

63
00:03:35,890 --> 00:03:39,320
decide later that you need to change your schedule. That's not a big

64
00:03:39,320 --> 00:03:43,420
deal, okay? Let me bring up VS Code because I always like to show you

65
00:03:43,420 --> 00:03:45,240
some of the PowerShell as well.

66
00:03:45,240 --> 00:03:50,980
Let me right‑click my line 27 in my script file, and here is the collection of

67
00:03:50,980 --> 00:03:55,790
commands that we have in that module. And then here on 29, this is how you

68
00:03:55,790 --> 00:03:59,840
would configure the cluster role for the cluster.

69
00:03:59,840 --> 00:04:03,790
This does basically the same thing that the wizard does where we're

70
00:04:03,790 --> 00:04:08,930
instructing Windows PowerShell to create that highly available role for

71
00:04:08,930 --> 00:04:14,140
CAU, and then we specify the meta or how we want the update to take place

72
00:04:14,140 --> 00:04:18,210
based on these different parameters, and this is just basic PowerShell.

73
00:04:18,210 --> 00:04:19,900
But if you're a beginner,

74
00:04:19,900 --> 00:04:22,840
I want to throw in just a little bit of stuff from time to time.

75
00:04:22,840 --> 00:04:27,340
As long as you've run update‑help to ensure that your workstation

76
00:04:27,340 --> 00:04:30,240
does have the help files for these commands,

77
00:04:30,240 --> 00:04:33,840
I would recommend you do something like get‑help,

78
00:04:33,840 --> 00:04:40,440
Add‑CauClusterRole, and then throw in the ‑Examples switch parameter.

79
00:04:40,440 --> 00:04:45,050
I use this all the time because it gives us a full run of examples.

80
00:04:45,050 --> 00:04:46,890
And normally the way they're structured,

81
00:04:46,890 --> 00:04:50,520
let me scroll up, they start with the simple case and

82
00:04:50,520 --> 00:04:53,040
then they get gradually more complex.

83
00:04:53,040 --> 00:04:56,060
So it looks like this first example similar to what I

84
00:04:56,060 --> 00:04:58,440
have up in my script file here.

85
00:04:58,440 --> 00:05:00,280
Let me see if there's anything different. Here,

86
00:05:00,280 --> 00:05:03,240
we're passing in a ‑PostUpdateScript.

87
00:05:03,240 --> 00:05:08,440
Let me see. What's the second one, ‑DaysOfWeek, Max, that's not too different.

88
00:05:08,440 --> 00:05:11,240
Third one looks like it's quite a bit more complicated where

89
00:05:11,240 --> 00:05:16,140
we're specifying specific plugins and locations to look for

90
00:05:16,140 --> 00:05:20,040
updates in those custom plugins. Nice.

91
00:05:20,040 --> 00:05:23,840
Yeah, so you can always learn a lot with the PowerShell help, for sure.

92
00:05:23,840 --> 00:05:27,780
I'm going to apply updates to this cluster, and let's just install those

93
00:05:27,780 --> 00:05:33,440
hotfixes right now. Let's click Next and then Update. Notice that it goes into

94
00:05:33,440 --> 00:05:36,230
updating mode in the background, and we can close this.

95
00:05:36,230 --> 00:05:41,240
So let's bring up our cluster manager. Whoops, wrong MMC console.

96
00:05:41,240 --> 00:05:43,560
Now let's take a look. We've got our roles and our

97
00:05:43,560 --> 00:05:47,010
nodes. Go to Nodes. And we also, frankly,

98
00:05:47,010 --> 00:05:49,490
instead of just manually watching the nodes, we

99
00:05:49,490 --> 00:05:55,000
always could go to Cluster Events. This is going to give us a nice filtered view.