1 00:00:01,040 --> 00:00:06,440 I also want you to see that in Windows Admin Center in the global navigation, 2 00:00:06,440 --> 00:00:09,440 we have the ability to browse our server connections 3 00:00:09,440 --> 00:00:12,430 both on‑prem and cloud‑based hosts, 4 00:00:12,430 --> 00:00:15,820 but we also have a separate node here for Cluster Manager, 5 00:00:15,820 --> 00:00:19,070 and this is going to allow us to make a connection to the cluster 6 00:00:19,070 --> 00:00:22,210 once it's created and do some basic management. 7 00:00:22,210 --> 00:00:26,010 I do want to reiterate that concept that management here in Windows 8 00:00:26,010 --> 00:00:29,140 Admin Center I think you'll find is pretty basic. 9 00:00:29,140 --> 00:00:32,350 The great advantage of WAC is that it's a browser‑based 10 00:00:32,350 --> 00:00:35,820 environment so you're not limited to a Windows environment like 11 00:00:35,820 --> 00:00:39,140 you are with the Microsoft Management consoles. 12 00:00:39,140 --> 00:00:40,070 On the other hand, 13 00:00:40,070 --> 00:00:44,700 you'll find that there is not the surface area as it were in WAC 14 00:00:44,700 --> 00:00:48,740 that you can find with those MMC consoles. 15 00:00:48,740 --> 00:00:52,540 So it looks like we've got our cluster az801cluster, 16 00:00:52,540 --> 00:00:53,650 and let's see here, 17 00:00:53,650 --> 00:00:58,370 I can take a look now at the DNS Management console 18 00:00:58,370 --> 00:01:08,440 now that I've installed that, and DNS is actually running on dc1.timw.info, 19 00:01:08,440 --> 00:01:12,940 and if I go to my timw.info Forward Lookup Zone, 20 00:01:12,940 --> 00:01:18,440 I've got a host record here for az801cluster with that static private address. 21 00:01:18,440 --> 00:01:19,680 So far so good. 22 00:01:19,680 --> 00:01:20,820 Now, nope, 23 00:01:20,820 --> 00:01:25,780 I didn't install the graphical tools here for failover clustering so I 24 00:01:25,780 --> 00:01:28,110 guess maybe we can try something different this time. 25 00:01:28,110 --> 00:01:31,740 Again, I just want to go through these different admin tools. 26 00:01:31,740 --> 00:01:33,660 As I said, I just want to show you, 27 00:01:33,660 --> 00:01:37,560 even if we're driving by these different management tools because they do 28 00:01:37,560 --> 00:01:40,920 come into play here as a hybrid cloud administrator. 29 00:01:40,920 --> 00:01:45,250 So I'm going to step through here making sure to select mem1 in the server list. 30 00:01:45,250 --> 00:01:48,940 And again, I want to go past roles into features, 31 00:01:48,940 --> 00:01:53,040 and we're going to do Remote Server Administration Tools, 32 00:01:53,040 --> 00:01:57,940 and I want to bring in here the Failover Cluster Management Tools. 33 00:01:57,940 --> 00:02:01,060 I also will bring in the command interface while I'm at it. 34 00:02:01,060 --> 00:02:05,240 Basically, I'm looking for the GUI console. 35 00:02:05,240 --> 00:02:08,540 Alright, so that completed so let me open up Tools, 36 00:02:08,540 --> 00:02:11,140 go to Failover Cluster Manager. 37 00:02:11,140 --> 00:02:15,540 This is just an advertisement saying that we can do the same thing in WAC. 38 00:02:15,540 --> 00:02:19,480 This is a tool you should absolutely master if you're going to work 39 00:02:19,480 --> 00:02:23,040 with failover clusters in Windows Server for sure. 40 00:02:23,040 --> 00:02:25,710 I just want to briefly walk you through the UI here. 41 00:02:25,710 --> 00:02:31,340 We've got our root level cluster node which has just some quick links on it. 42 00:02:31,340 --> 00:02:33,050 We've got our roles, 43 00:02:33,050 --> 00:02:37,720 which is 0 right now because we haven't deployed any highly available roles. 44 00:02:37,720 --> 00:02:40,640 If you right‑click and go to Configure Role, 45 00:02:40,640 --> 00:02:44,670 you can see a list via this wizard of all of the possible 46 00:02:44,670 --> 00:02:47,690 built‑in role types that are supported. 47 00:02:47,690 --> 00:02:49,140 We have our nodes, 48 00:02:49,140 --> 00:02:52,900 which allows you to see at a glance the availability of your nodes, 49 00:02:52,900 --> 00:02:56,140 how many votes each one currently has, 50 00:02:56,140 --> 00:03:00,440 and you can get to a lot of controls just via the right‑click, 51 00:03:00,440 --> 00:03:02,940 the context menu, as you can see. 52 00:03:02,940 --> 00:03:05,840 For our storage, we've got links to disks, 53 00:03:05,840 --> 00:03:11,090 pools, and enclosures, this would be for our external SAN enclosures, 54 00:03:11,090 --> 00:03:16,340 and then we have Storage Spaces Direct with storage pools and virtual disks. 55 00:03:16,340 --> 00:03:20,240 Here we have our cluster network option here. 56 00:03:20,240 --> 00:03:23,500 Take a look at our properties and this just shows 57 00:03:23,500 --> 00:03:26,320 our different network connections, 58 00:03:26,320 --> 00:03:29,730 particularly important if you have multiple path I/O. 59 00:03:29,730 --> 00:03:34,750 And then we have a filtered view of event log here looking at cluster events. 60 00:03:34,750 --> 00:03:38,540 Fortunately, there is nothing yet here, but it's a brand‑new cluster. 61 00:03:38,540 --> 00:03:39,680 What are some other options? 62 00:03:39,680 --> 00:03:42,740 Well, like I said, let's go back to the script file. 63 00:03:42,740 --> 00:03:46,840 You can use the old cluster.exe command. 64 00:03:46,840 --> 00:03:48,840 This is convenient, I suppose, 65 00:03:48,840 --> 00:03:52,520 but it's not very useful in terms of it's all text‑based output, 66 00:03:52,520 --> 00:03:53,800 it's not object based, 67 00:03:53,800 --> 00:03:56,130 so you're not really going to have the notion of a 68 00:03:56,130 --> 00:03:58,290 pipeline like you do with PowerShell. 69 00:03:58,290 --> 00:04:02,860 Cluster/quorum gives you the current quorum configuration. 70 00:04:02,860 --> 00:04:06,240 We just have simple node majority with no witness yet. 71 00:04:06,240 --> 00:04:10,440 And then using PowerShell, using some of those cluster commands here, 72 00:04:10,440 --> 00:04:14,750 we can run Get‑Cluster to get a list of all of the properties 73 00:04:14,750 --> 00:04:17,540 that are currently set for that cluster. 74 00:04:17,540 --> 00:04:23,760 We can again replicate the cluster/quorum with Get‑ClusterQuorum. 75 00:04:23,760 --> 00:04:28,240 Let me just try running Get‑ClusterQuorum with nothing else. 76 00:04:28,240 --> 00:04:31,540 Yeah, that's that output is not particularly useful. 77 00:04:31,540 --> 00:04:34,860 And then with all things PowerShell, don't forget about Get‑Help. 78 00:04:34,860 --> 00:04:38,440 I haven't updated my help yet so it won't return anything, 79 00:04:38,440 --> 00:04:41,470 but if we were going to set cluster quorum programmatically, 80 00:04:41,470 --> 00:04:44,340 we'd probably want the command Set‑ClusterQuorum, 81 00:04:44,340 --> 00:04:48,540 and I find doing Get‑Help with the Examples switch parameter 82 00:04:48,540 --> 00:04:51,920 is excellent because you can get some guidance and get 83 00:04:51,920 --> 00:04:54,240 productive with the command immediately. 84 00:04:54,240 --> 00:04:55,640 Alright, awesome. 85 00:04:55,640 --> 00:04:58,740 Well, let's go back to WAC one more time. 86 00:04:58,740 --> 00:05:02,710 We are going to be on Cluster Manager and let's go Cluster Connections, 87 00:05:02,710 --> 00:05:07,840 Add, the name of the cluster is az801cluster. 88 00:05:07,840 --> 00:05:10,880 I don't need to manage software‑defined networking 89 00:05:10,880 --> 00:05:12,940 because I don't have that set up. 90 00:05:12,940 --> 00:05:15,450 Also add server as well we already have, 91 00:05:15,450 --> 00:05:18,940 so WAC should be smart enough to see that. 92 00:05:18,940 --> 00:05:21,810 So now we have a separate entry for cluster connections, 93 00:05:21,810 --> 00:05:24,060 so let's click into that cluster, 94 00:05:24,060 --> 00:05:27,040 and what I want you to see is up here on this bar, 95 00:05:27,040 --> 00:05:32,820 this is a great benefit that we don't have access to with the old MMC consoles. 96 00:05:32,820 --> 00:05:36,300 I mean, other than something like Windows update or WSUS, 97 00:05:36,300 --> 00:05:38,340 you might get an update that way. 98 00:05:38,340 --> 00:05:41,870 But notice that WAC works on the basis of extension. 99 00:05:41,870 --> 00:05:44,600 So Cluster Manager is actually an extension, 100 00:05:44,600 --> 00:05:47,540 so that means that when the Microsoft engineers fix 101 00:05:47,540 --> 00:05:53,660 bugs and add new capabilities, you can then update those extensions very easily, 102 00:05:53,660 --> 00:05:55,500 just as easily actually, 103 00:05:55,500 --> 00:05:59,970 as you would update extensions in your web browser itself or in 104 00:05:59,970 --> 00:06:03,540 Visual Studio Code or Visual Studio itself. 105 00:06:03,540 --> 00:06:10,000 Alright, I think that's all we need to do in this lesson, so we'll just call this demo done and continue.