Remote Desktop Services (RDS), formerly known as Terminal Services, is one of the components of Microsoft Windows (both server and client versions) that allows a user to access applications and data on a remote computer over a network, using the Remote Desktop Protocol (RDP).
It is generally known that RDS accelerates and extends desktop and application deployments to any device, improving remote worker efficiency, while helping to keep critical intellectual property secure and simplify regulatory compliance. RDS enables both a virtual desktop infrastructure (VDI) and session-based desktops, allowing users to work anywhere.
It lets you efficiently deploy and maintain software in an enterprise environment. You can easily deploy programs from a central location. Because you install the programs on the RD Session Host server and not on the client computer, programs are easier to upgrade and to maintain.
This is enough as a very brief description of RDS. More about it you can always get from the Microsoft’s official site.
Monitor it !!!
The importance of monitoring was discussed in previous articles many times.
Whether you use Microsoft Windows Terminal Services purely as a network management tool or as a platform for hosting user terminal sessions, you need a method for managing and monitoring it.
Now let’s think about how it is possible to monitor Terminal Services easily?
When creating a monitor for any system you should follow the basic steps described below:
Identify components to monitor.
Select metrics for those components.
Monitor the server.
Analyze the data.
Windows Management Instrumentation (WMI) which is an implementation of Web-Based Enterprise Management (WBEM) allows to provide both management and monitoring almost all Windows objects. Thus, a monitor that use WMI can capture a lot of information which are very useful for diagnosing any problems including also performance.
The Monitis WMI monitoring tool let you monitor also Terminal Services performance using WMI counters.
WMI Counters allow you a method to measure current performance. Identifying the metrics you like to use to measure Terminal Services performance gives you a quick and easy way to identify Terminal Services problems, as well as graph your performance trend over time.
Thanks to made researches we chose nine suitable counters of Terminal Services which are important and preferable to monitor.
Available Licenses: Total number of available licenses in the Remote Desktop Services license key pack.
AvailableMBytes: Amount of physical memory available to processes running on the computer, in megabytes. It is calculated by summing space on the Zeroed, Free, and Standby memory lists. Free memory is ready for use; Zeroed memory contains memory pages filled with zeros to prevent later processes from seeing data used by a previous process. Standby memory is memory removed from a process’ working set (its physical memory), but is still available to be recalled. This property displays the last observed value only; it is not an average.
TotalSessions: The total number of sessions on the current server. This includes both connected and disconnected sessions.
DisconnectedSessions: The number of disconnected sessions on the current server. These sessions may still be actively consuming server resources, however they currently have no network connection with a client.
InputAsyncOverflow: Number of input async overflow errors. These can be caused by a insufficient buffer size available on the host.
VirtualBytes: Current size, in bytes, of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite and, by using too much, the process can limit its ability to load libraries.
ThreadCount: Number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.
Make sure you have a valid account on www.monitis.com.
Download your copy of WMI Monitor from github and install. After it follow the instructions below.
Voila! You are ready to get data now!
We have started our monitor on Windows server 2008R2. The graphics below are the results of 2 hours tests.
As the result values can be very different (it’s impossible to see both total connections’ value with available mbytes’ value in the same graphic, because the difference is very large, ex: 10 connections vs 13294 mbytes ) we put graphics separated.
This is all about terminal services monitoring with monitis for now.
As you can see, monitoring is not only easy with Monitis, but also is a nice process . So, do not forget to visit Monitis.com next time you’ll think about monitoring.