For instance, when you're looking for performance counters related to disk, type the following command to display disk-related performance counters: The list of performance counters is extensive, but using the find command on the output might help narrowing down what you're looking for. To list the performance counters with their instances type: typeperf.exe /qx To find a performance counter to monitor type the following command: typeperf.exe /q This will display a list with (installed) counters without instances. logman.exe however doesn't provide this functionality. To select a counter to monitor using logman.exe you need to know the name of the counter to add.

The two great things logman.exe lacks are the ability to draw graphs and to point-and-click your queries together.

It supports many functions of Performance Monitor from the command line.

It's called logman.exeĮven though logman.exe is a command line tool it's a really impressive monitoring tool, since it can collect counter, trace, alert, configuration and API tracing collectors. Fortunately there is a command line driven version available, which can be used to monitor your Server Core box from the command line. The graphical version of the Performance Monitor is not part of Server Core. This is on full installations of Windows Server where the Performance Monitor comes in.

It doesn't include disk space monitoring.

The Task Manager is perfect, but unfortunately it lacks on a couple of points:

Press the Ctrl, Alt and Esc keys at the same time.

Press the Ctrl, Alt and Del keys at the same time and select Start Task Manager from the list.

The Task Manager is a perfect utility to monitor your Server Core in a way that has been familiar since Windows 95. I've taken a closer look at monitoring Server Core boxes from the command line and want to share my experiences with you on this matter today. Monitoring it gives clues towards this behavior and/or provides insight in why it behaves flaky. A server running a Server Core installation of Windows Server 2008 could behave flaky from time to time.

System monitor sysinternals