One additional feature that is available with Windows Server 2003 is the ability to right-click on an application and Go To Process. This will switch to the Processes tab, with the associated process highlighted. It will not, however, display all associated processes.
The Performance tab is used as a quick graphical means of looking at the most important parts of the system. The graphical displays for CPU utilization closely resemble Performance Monitor’s System Monitor. You do not have the ability to add objects and counters, but then again, you don’t have to worry about associated system overhead either, since the Performance tab is always available. The Performance tab can be used as a constant display that will help you identify problems as they occur, such as memory leaks, or high CPU or pagefile usage.

The two new Networking and Users tabs are definitely a must for the quick-and-dirty troubleshooting admin. The Networking tab will display network utilization for all installed network cards. Between this and the Performance tab, you can easily and quickly draw any correlations between network usage and CPU utilization. Although you can’t draw any hard-and-fast conclusions as to what a problem is, this is definitely the quick way to determine if a proverbial ‘the network is slow’ complaint is related to the networking load on the server itself.

The Users tab is a long-overdue method of determining who is currently logged into the system. The capability was available with Windows NT, but it was buried within User Manager for Domains within the Domain Policy. It was made slightly easier with Windows 2000, where user connections could be monitored through Computer Management, which is still around for Windows .NET. The ability to monitor current logons and connections through the Task Manager simply give the administrator a quick way to gauge the user connections on a server, not to mention the ability to disconnect a connection, or force a user to logoff.