1
00:00:01,040 --> 00:00:05,800
I'll select mem2, and we'll shift that over, and we could do the same

2
00:00:05,800 --> 00:00:10,220
thing with some other roles like this. File Server over here, I'll do

3
00:00:10,220 --> 00:00:15,200
the same thing. But we can manually balance the cluster, and we can

4
00:00:15,200 --> 00:00:21,050
review cluster events as we normally do. Now as far as the Windows Admin

5
00:00:21,050 --> 00:00:24,060
Center stuff that I was talking about, actually we're driving by

6
00:00:24,060 --> 00:00:28,840
cluster‑aware updating, it looks like the run succeeded, so let's do a

7
00:00:28,840 --> 00:00:31,640
Generate report.

8
00:00:31,640 --> 00:00:34,950
The reason I wanted to do this is not to view the reports

9
00:00:34,950 --> 00:00:38,660
in the GUI, but I like a deliverable.

10
00:00:38,660 --> 00:00:44,320
I'll call this cau‑report. It looks like it's an HTML file.

11
00:00:44,320 --> 00:00:49,270
That's not bad, just a self‑contained static HTML file that

12
00:00:49,270 --> 00:00:50,940
you can share or whatever.

13
00:00:50,940 --> 00:00:54,660
So let's check out that port 6516 on my server.

14
00:00:54,660 --> 00:00:58,950
And what I want you to see here is that we've got that dedicated Cluster

15
00:00:58,950 --> 00:01:02,450
Manager view. And if you don't have a connection to your cluster,

16
00:01:02,450 --> 00:01:06,920
you click Add. Type the DNS name of your cluster. You might need to put

17
00:01:06,920 --> 00:01:10,820
in credentials, and then you've got a persistent connection through the

18
00:01:10,820 --> 00:01:14,950
browser in WAC. So let's take a look at what we can do in the cluster

19
00:01:14,950 --> 00:01:18,740
manager WAC. While this is loading,

20
00:01:18,740 --> 00:01:22,510
it takes a little while. It looks like we can get to our highly available VMs.

21
00:01:22,510 --> 00:01:28,350
We can look at our nodes. We can look at our storage subsystem. If we're doing

22
00:01:28,350 --> 00:01:31,250
software‑defined networking with multiple switches,

23
00:01:31,250 --> 00:01:33,140
we can get to that layer.

24
00:01:33,140 --> 00:01:37,940
So this is going to presume that through WAC, we can get to those

25
00:01:37,940 --> 00:01:45,460
cluster hosts. Now, some warts with WAC are occasional bugs you just

26
00:01:45,460 --> 00:01:48,540
saw probably up in the notification area.

27
00:01:48,540 --> 00:01:50,000
It looks like it kind of bombed.

28
00:01:50,000 --> 00:01:51,160
Let me try that again.

29
00:01:51,160 --> 00:01:52,940
It's kind of annoying when that happens.

30
00:01:52,940 --> 00:01:56,740
It was working just fine, of course, before I started this demo,

31
00:01:56,740 --> 00:01:58,360
but sometimes you'll find it slow.

32
00:01:58,360 --> 00:02:03,120
And what's especially disappointing is that I have just updated this

33
00:02:03,120 --> 00:02:07,590
extension too, so I thought you can do that under Settings. Well,

34
00:02:07,590 --> 00:02:11,330
let me see if I try to browse directly to a blade within Cluster

35
00:02:11,330 --> 00:02:15,440
Manager that's better. Hopefully, fingers crossed.

36
00:02:15,440 --> 00:02:20,290
So this view is going to show our highly available VMs. And so another

37
00:02:20,290 --> 00:02:26,720
feature/wart of WAC, and I've mentioned this before, is that your surfaced‑only

38
00:02:26,720 --> 00:02:31,540
selected things to do or selected administration commands,

39
00:02:31,540 --> 00:02:35,160
we can select the VM. We can connect to it.

40
00:02:35,160 --> 00:02:37,620
We can, in fact, move it to another node.

41
00:02:37,620 --> 00:02:41,240
So, in a pinch, if you were called into action,

42
00:02:41,240 --> 00:02:43,840
you could maybe VPN into Corpnet,

43
00:02:43,840 --> 00:02:48,050
get your WAC console up and running that way without having to get a full

44
00:02:48,050 --> 00:02:51,650
desktop where you have your PowerShell and you have your Microsoft

45
00:02:51,650 --> 00:02:54,710
Management Console. And as I had mentioned before,

46
00:02:54,710 --> 00:02:58,760
there's lots of integration with Azure, and Azure works great in a

47
00:02:58,760 --> 00:03:03,410
hybrid cloud. Ideally, we would have our cluster hosts loaded up with

48
00:03:03,410 --> 00:03:06,860
Azure Arc extension or the connected machine agent, as it's formally

49
00:03:06,860 --> 00:03:12,070
called, and this makes it very easy to surface diagnostics and metrics

50
00:03:12,070 --> 00:03:15,950
data in Azure Monitor, deliver updates centrally from the cloud

51
00:03:15,950 --> 00:03:18,340
diagnostics, etc, etc.

52
00:03:18,340 --> 00:03:18,870
So anyway,

53
00:03:18,870 --> 00:03:26,000
that's kind of a nonstarter with Windows Admin Center. Let me clean up the desktop, and we'll call this demo done.