1
00:00:01,140 --> 00:00:03,020
Next we have Resource Monitor,

2
00:00:03,020 --> 00:00:07,010
which looks like an expanded version of Task Manager,

3
00:00:07,010 --> 00:00:09,430
if you're familiar with that, and it kind of is.

4
00:00:09,430 --> 00:00:12,420
What you can see here across the top are a number of

5
00:00:12,420 --> 00:00:14,950
tabs that first show a roll‑up,

6
00:00:14,950 --> 00:00:18,970
an overview of the entire performance picture of the given machine.

7
00:00:18,970 --> 00:00:22,640
And then you can drill into the four basic compute

8
00:00:22,640 --> 00:00:27,790
subsystems in Windows Server: CPU, or processor; Memory,

9
00:00:27,790 --> 00:00:31,460
that's going to be physical random access memory,

10
00:00:31,460 --> 00:00:37,060
as well as logical memory, page file kind of stuff; that bleeds into Disk,

11
00:00:37,060 --> 00:00:40,190
that's storage utilization and speed; and then we

12
00:00:40,190 --> 00:00:42,630
have Network utilization and speed.

13
00:00:42,630 --> 00:00:47,350
So in sum, you see that Resource Monitor is really a real‑time analysis.

14
00:00:47,350 --> 00:00:50,290
If you have some performance issues in Windows Server,

15
00:00:50,290 --> 00:00:54,400
you just want to get a quick EKG, so to speak, a quick live

16
00:00:54,400 --> 00:00:58,720
picture of what's consuming on this machine, Resource Monitor is a

17
00:00:58,720 --> 00:01:01,270
good tool to know about. Now you might be thinking, well, Tim,

18
00:01:01,270 --> 00:01:03,700
what about the Sysinternals tools?

19
00:01:03,700 --> 00:01:08,170
Those are for Microsoft. And while you're absolutely correct on that,

20
00:01:08,170 --> 00:01:13,650
Sysinternals is not on the AZ‑800 or 801 objective domain, so I'm not going

21
00:01:13,650 --> 00:01:17,060
to cover it, but you definitely should look at those tools. They're all free.

22
00:01:17,060 --> 00:01:21,520
If you're not aware, there's several that are excellent for troubleshooting.

23
00:01:21,520 --> 00:01:25,300
The Reliability Monitor, again, it's been around for a while.

24
00:01:25,300 --> 00:01:28,840
It's part of the old‑fashioned Windows Control Panel, and I like

25
00:01:28,840 --> 00:01:32,940
this because it gives you a wide picture of the historical

26
00:01:32,940 --> 00:01:37,160
availability of your server system. And you can see that if

27
00:01:37,160 --> 00:01:39,620
there's error or warning events,

28
00:01:39,620 --> 00:01:43,600
they show right up very clearly on the graph, and then you

29
00:01:43,600 --> 00:01:48,200
can look below and read in more detail what happened to

30
00:01:48,200 --> 00:01:50,510
cause that failure or that warning.

31
00:01:50,510 --> 00:01:53,320
You see that it's divided into app failures,

32
00:01:53,320 --> 00:01:55,900
Windows failures, miscellaneous failures,

33
00:01:55,900 --> 00:01:59,140
warnings, and then just information notifications.

34
00:01:59,140 --> 00:02:02,920
This can tell you things that may not be entirely obvious.

35
00:02:02,920 --> 00:02:07,440
Maybe there was a transient server reboot over last night, you see. You can

36
00:02:07,440 --> 00:02:11,480
isolate exactly when that took place. If a service stopped,

37
00:02:11,480 --> 00:02:14,350
you can find out when and details around that

38
00:02:14,350 --> 00:02:18,140
situation. Reliability Monitor is fantastic.

39
00:02:18,140 --> 00:02:22,980
The idea with all of these tools is ideally to have nothing left to the

40
00:02:22,980 --> 00:02:26,300
imagination when you're troubleshooting a problem in Windows Server.

41
00:02:26,300 --> 00:02:29,490
And I think you can see that our concern here isn't so

42
00:02:29,490 --> 00:02:31,480
much things like security access,

43
00:02:31,480 --> 00:02:35,610
it's mainly performance troubleshooting and performance optimization,

44
00:02:35,610 --> 00:02:43,000
looking again at those four main subsystems: processor, memory, disk, and network.