1 00:00:01,040 --> 00:00:05,340 In this demonstration, we'll work with system insights in Windows server. 2 00:00:05,340 --> 00:00:10,040 As I mentioned, the front end for system insights is Windows Admin Center. 3 00:00:10,040 --> 00:00:12,560 So here we are in WAC. 4 00:00:12,560 --> 00:00:15,270 I just happen to be connected to the gateway. 5 00:00:15,270 --> 00:00:17,530 I have mem1 configured as a gateway, 6 00:00:17,530 --> 00:00:22,680 and one of the things that I always evangelize is the update ability here. 7 00:00:22,680 --> 00:00:24,920 A new update is available, go to Settings. 8 00:00:24,920 --> 00:00:26,440 Well that's kind of cool. 9 00:00:26,440 --> 00:00:28,200 So it looks like coincidentally, 10 00:00:28,200 --> 00:00:30,970 there is a new version of Windows Admin Center that 11 00:00:30,970 --> 00:00:34,270 populated just today before I started working. 12 00:00:34,270 --> 00:00:34,670 Well, 13 00:00:34,670 --> 00:00:37,680 I'm not going to update WAC now because I don't want 14 00:00:37,680 --> 00:00:39,620 to throw anything into question. 15 00:00:39,620 --> 00:00:44,620 Instead, let's take a look here at let's go into mem2, 16 00:00:44,620 --> 00:00:49,440 just 1 of my member servers that I've onboarded here into WAC. 17 00:00:49,440 --> 00:00:54,440 And the first thing you'll want to do actually is install the service. 18 00:00:54,440 --> 00:00:58,440 So we'll go to Settings and then we'll go to Extensions, 19 00:00:58,440 --> 00:01:00,840 and I already have it installed. 20 00:01:00,840 --> 00:01:06,140 Come down to system in the Ss, System Insights right here. 21 00:01:06,140 --> 00:01:09,830 And so you just look that up under Available extensions, 22 00:01:09,830 --> 00:01:12,540 you click Install, and you're good to go. 23 00:01:12,540 --> 00:01:14,650 And then you can see here, as I mentioned, 24 00:01:14,650 --> 00:01:19,640 the extensible nature of WAC means that as Microsoft and other vendors 25 00:01:19,640 --> 00:01:23,440 create different capabilities via the extension model, 26 00:01:23,440 --> 00:01:27,210 you can keep them current either automatically or manually what 27 00:01:27,210 --> 00:01:31,040 I just did by clicking the Update button. 28 00:01:31,040 --> 00:01:31,880 Alright, nice. 29 00:01:31,880 --> 00:01:35,490 So let's go back to where we were. 30 00:01:35,490 --> 00:01:37,280 Let's see, I kind of forgot where I was. 31 00:01:37,280 --> 00:01:39,530 So let's go back to All connections. 32 00:01:39,530 --> 00:01:40,920 Oh yes, mem2, right. 33 00:01:40,920 --> 00:01:42,400 So let's go back to mem2, 34 00:01:42,400 --> 00:01:47,340 and I'm going to look up System insights in the Tools list. 35 00:01:47,340 --> 00:01:51,540 When you first come in here, there is a button to install the service. 36 00:01:51,540 --> 00:01:53,870 Remember, all of this is on Windows server. 37 00:01:53,870 --> 00:01:58,410 We're not dealing with any subscriptions in the cloud or anything like that. 38 00:01:58,410 --> 00:02:01,050 And once you've installed the service, 39 00:02:01,050 --> 00:02:04,990 we have this interface that shows your capabilities and these are the 40 00:02:04,990 --> 00:02:08,120 four default capabilities that I told you about. 41 00:02:08,120 --> 00:02:11,220 And what happens here is that for each one of those, 42 00:02:11,220 --> 00:02:14,700 you'll want to enable them and then make sure to invoke 43 00:02:14,700 --> 00:02:17,040 them to actually start it running. 44 00:02:17,040 --> 00:02:20,070 I have invoked all four so they're enabled, 45 00:02:20,070 --> 00:02:21,440 the status is OK, 46 00:02:21,440 --> 00:02:26,900 and we can see when they were last run and what the current description is. 47 00:02:26,900 --> 00:02:30,320 So it looks like I'm good, and I'm not surprised at all that 48 00:02:30,320 --> 00:02:33,450 the forecasting here is going to be within my available 49 00:02:33,450 --> 00:02:35,880 capacity because this is a quiet server, 50 00:02:35,880 --> 00:02:37,950 but on one of your production servers, 51 00:02:37,950 --> 00:02:43,590 the idea is you can get important proactive information regarding any of 52 00:02:43,590 --> 00:02:49,650 these subsystems and that will help you avoid a potential downtime event 53 00:02:49,650 --> 00:02:53,170 in terms of hardware on your server going bad, 54 00:02:53,170 --> 00:02:53,530 you see. 55 00:02:53,530 --> 00:02:59,220 So what we can do is go to Settings, and for each one of those capabilities, 56 00:02:59,220 --> 00:03:02,230 we can set on the schedule whether you want to 57 00:03:02,230 --> 00:03:04,940 enable or disable the predictions. 58 00:03:04,940 --> 00:03:09,380 You can adjust the time grain for measurement minute, hourly, or daily. 59 00:03:09,380 --> 00:03:12,850 I have mine set very aggressively because I wanted to 60 00:03:12,850 --> 00:03:16,840 surface data to you as quickly as I could, 61 00:03:16,840 --> 00:03:20,940 and then we have the days on which an evaluation will take place, 62 00:03:20,940 --> 00:03:23,870 and then we have prediction interval in minutes, 63 00:03:23,870 --> 00:03:26,860 specifies the number of minutes between predictions. 64 00:03:26,860 --> 00:03:30,940 So every 5 minutes, there is a new prediction on this system. 65 00:03:30,940 --> 00:03:32,050 We go to Actions. 66 00:03:32,050 --> 00:03:36,650 This allows us to optionally run PowerShell scripts automatically. 67 00:03:36,650 --> 00:03:42,730 So this ties in a bit with built‑in alerting capabilities in WAC, 68 00:03:42,730 --> 00:03:47,110 and so whenever a particular status were to change, 69 00:03:47,110 --> 00:03:52,840 you could fire off a particular script and pass credentials optionally. 70 00:03:52,840 --> 00:03:55,420 If we click Browse example scripts, 71 00:03:55,420 --> 00:03:59,580 it takes us out to the Microsoft tech community, 72 00:03:59,580 --> 00:04:03,920 this particular blog post, and it looks like, 73 00:04:03,920 --> 00:04:07,850 oh boy, this is an old fashioned page where we could do alerting, 74 00:04:07,850 --> 00:04:09,920 reporting, etc, etc, etc. 75 00:04:09,920 --> 00:04:12,590 That's not as clean of an interface as I was hoping. 76 00:04:12,590 --> 00:04:16,930 As you can see up here, in the WAC global navigation, 77 00:04:16,930 --> 00:04:19,660 there is a View PowerShell scripts button, 78 00:04:19,660 --> 00:04:23,710 and then for each tool, this is where the scripts really should show up. 79 00:04:23,710 --> 00:04:26,720 I think, I'm just making an educated guess, 80 00:04:26,720 --> 00:04:31,240 that this really should invoke this panel and Microsoft, 81 00:04:31,240 --> 00:04:34,060 hopefully by the time you're watching this lesson, 82 00:04:34,060 --> 00:04:38,100 may have some system insights sample scripts that you can work with, 83 00:04:38,100 --> 00:04:40,940 but it looks like that's not the case quite yet. 84 00:04:40,940 --> 00:04:46,790 Okay, so let's back out of here and let's go back to our capability list. 85 00:04:46,790 --> 00:04:50,840 The idea with these capabilities, let me actually go back, 86 00:04:50,840 --> 00:04:55,340 is if we open the menu here, Add and remove capabilities, 87 00:04:55,340 --> 00:04:59,130 I'm thinking that over time we're going to see more, 88 00:04:59,130 --> 00:05:00,840 initially from Microsoft, 89 00:05:00,840 --> 00:05:05,840 but potentially eventually by third‑party independent software vendors. 90 00:05:05,840 --> 00:05:08,220 As a matter of fact, you can see that in my list here, 91 00:05:08,220 --> 00:05:12,840 I have two not installed that are related to physical disk anomalies, 92 00:05:12,840 --> 00:05:16,860 latency and IOPs values, and I can select these, 93 00:05:16,860 --> 00:05:21,080 install them, and bring those extra capabilities into scope, 94 00:05:21,080 --> 00:05:24,750 and that would just simply add more capabilities. 95 00:05:24,750 --> 00:05:27,360 And again, this is on a server‑by‑server basis. 96 00:05:27,360 --> 00:05:33,010 We're looking only on mem2.timw.info in System Insights. 97 00:05:33,010 --> 00:05:35,340 So let's come back to the home page here, 98 00:05:35,340 --> 00:05:37,870 and I haven't done anything with this one yet, 99 00:05:37,870 --> 00:05:42,060 so we can select the new anomaly, we can invoke, 100 00:05:42,060 --> 00:05:46,040 we can go to Settings, which again, allows you to do your schedule, 101 00:05:46,040 --> 00:05:50,660 invoke to actually start a run, failed to make a prediction. 102 00:05:50,660 --> 00:05:52,210 Oh, maybe it's not enabled. 103 00:05:52,210 --> 00:05:54,040 No, it is enabled. 104 00:05:54,040 --> 00:05:55,650 Maybe we need to reboot. 105 00:05:55,650 --> 00:05:56,020 Again, 106 00:05:56,020 --> 00:05:58,300 this speaks to the fact that when you're dealing with 107 00:05:58,300 --> 00:06:01,300 capabilities that are under active development, 108 00:06:01,300 --> 00:06:05,040 you should expect to see bugs from time to time, 109 00:06:05,040 --> 00:06:09,760 but what's especially cool is Microsoft does so much of their work 110 00:06:09,760 --> 00:06:12,270 and their engineering out in the open at GitHub, 111 00:06:12,270 --> 00:06:18,410 you very likely can report issues directly to them and hopefully those reports 112 00:06:18,410 --> 00:06:22,080 will be triaged and acted upon sooner rather than later. 113 00:06:22,080 --> 00:06:25,560 The last thing you probably want to see is what do the actual 114 00:06:25,560 --> 00:06:28,140 recommendations and forecasts look like. 115 00:06:28,140 --> 00:06:33,340 That's where you, in System Insights, click a specific capability, 116 00:06:33,340 --> 00:06:40,000 and we can see over time here that after an initial burst of 75% CPU, 117 00:06:40,000 --> 00:06:43,840 this machine has really been pretty quiet ever since. 118 00:06:43,840 --> 00:06:47,260 And then for each prediction, it's going to let you know, 119 00:06:47,260 --> 00:06:47,660 and again, 120 00:06:47,660 --> 00:06:51,050 I'm not expecting to see anything other than that the 121 00:06:51,050 --> 00:06:54,960 CP usage is forecasted to remain, but if that were to change, 122 00:06:54,960 --> 00:06:59,340 we know that we can be proactively notified via PowerShell, 123 00:06:59,340 --> 00:07:02,450 and the same thing applies here to networking as you can see. 124 00:07:02,450 --> 00:07:09,040 Again, very quiet situation here, and then we've got some storage consumption, 125 00:07:09,040 --> 00:07:12,740 pretty basic, pretty standard. 126 00:07:12,740 --> 00:07:15,080 It might be interesting, this just occurred to me, 127 00:07:15,080 --> 00:07:21,410 to on a lab system use tools like CpuStres from Sysinternals or 128 00:07:21,410 --> 00:07:25,480 just maybe load the virtual hard disk of the machine so it becomes 129 00:07:25,480 --> 00:07:30,590 constrained of space to invoke the movement of a system insights 130 00:07:30,590 --> 00:07:32,730 prediction to another status. 131 00:07:32,730 --> 00:07:37,000 I'll give that to you as a homework assignment. How's that sound?