$theTitle=wp_title(" - ", false); if($theTitle != "") { ?>
About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like
Beta Release | Part 1 | Part 2 |
This is part 3 of the TSAdminEx Features series. Today I will discuss the Process View. As usual we will start by comparing TSAdmin to TSAdminEx again. So let’s look at TSAdmin Process View:
And the one from TSAdminEx:
As you might notice TSAdminEx shows many more details but also more processes. I ran both tools on the same server with the same account (just a normal user account). TSAdmin is very restricted under non admin accounts, let’s look closer:
TSAdmin shows all processes in my Session and shows for all other sessions the csrss.exe process and the winlogon process. It doesn’t seem to know what user is tied to those processes.
Let’s look at what Task Manager shows us:
Task Manager shows only the processes in my Session but again does not show the user names for wnlogon.exe and csrss.exe.
If we look at TSAdminEx we see that it has no problem showing all user processes and the user who owns the process:
But even TSAdminEx has some limitations under Non Administrative accounts, if we sort on Process Id we can see that we do not see the System Process and the System Idle Process:
So let’s run it as an Administrator now:
Please note that the System and System Idle Process are important because they are needed to calculate CPU Time. Which brings us to that feature of TSAdminEx.
If we select the Auto Update checkbox on the Process View TSAdminEx will automatically update the process information every second (presently this is a fixed interval but this might change to selectable interval).
After an update TSAdminEx calculates the relative CPU time for each process and displays this in the CPU Column:
We can also do this for remote and even multiple (remote) servers at a time:
So this gives us a view we can instantly see relative CPU time on all servers and by sorting on the CPU column we can keep an eye on processes that consume a lot of CPU time.
For even more insight we can look at the CPU Time column which displays the total CPU time that has been allocated to the process since it’s creation in HH:MM:SS. The Process Age column is also helpfull since it’s displays how long ago the process was created in d+HH:MM:SS (d=Days).
By looking at the process with the highest Process Age (sort on this column) we can easily determine the uptime of the server:
It is no coincidence that the oldest process is SMSS.exe as it is one of the first processes launched at boot.
Besides CPU allocation TSAdminEx also presents detailed information on Process Memory Allocation:
With a right-click on a process (or the corresponding Toolbar button) we can end a process:
As you might have noticed TSAdminEx tries to show the process Icon where possible. This only works if this process has an icon and the process can be found on the machine that TSAdminEx runs ons (querying icon remotely over the network would decrease performance too much).
I want to end this post with a remark I forgot to make yesterday: TSAdmin always sorts columns Case Sensitive, this has always annoyed me because it makes searching for a particular user or process difficult. Ofcourse TSAdminEx fixes this and sorts Case Insensitive.
TSAdmin:
TSAdminEx:
Don’t forget, participating in the Beta test is still possible…
One Response for "TSAdminEx Features Part 3"
Hi Remko,
Sorry me again, I had been trying to go through your JwaWinsta unit to obtain details of the structure to get at the bytes in and out, although you reverse engineered _WINSTATION_INFORMATIONW which included it, you then commented that out in favoiur of the documented _WINSTATIONINFORMATIONW structure which doesnt include the bytes information, and is quite different.
I was wondering whether I should be persuing this function in order to get at the bytes.
Anyway just thought I’d mention that, and say hello!
kind regards,
Ross
Leave a reply