October 26, 2003
Terminal Server Monitor v0.1
So, our production environment at work has three servers with SQL Enterprise Manager installed. Each of those three servers has two available Terminal Server connections. We have 7 developers and/or admin who may need access to those Terminal Server connections at any given time. When I was working from the office it wasn't difficult to login, since there are only two machines in the building with the production VPN installed, it was easy enough to see if the machines were being used, and if not, it was easy enough to walk over and see if they were already connected. However, now that I'm working remotely, I find myself searching for a server with an available connection whenever I need to access the database in our production environment. So I did what anyone would do in that situation, I built a C# app to monitor the different Terminal Servers I access on a daily basis so I don't have to hunt and peck for one with an available connection. Without further ado, I give you the aptly named, Terminal Server Monitor.
Details:
C# Windows Form application
Features:
Monitor Available Connections to Terminal Servers
Disconnect existing Connections to Terminal Servers
Requirements:
Windows 2000/XP Professional
.NET Framework 1.1
Download the executable: Terminal Server Monitor v0.1. Just unzip anywhere you like and run.
Download the source (licensed under the GPL for now): Terminal Server Monitor Source v0.1.
Fine print:
This application is supplied as-is and without warranty. If for some reason it blows up your machine, I'm sorry, but it's not my fault. It has only been tested on my machine (Win2K SP4, running .NET Framework 1.1) and I make no guarantees that it currently does, or will ever run anywhere else. If you'd like to see something added, changed, or fixed, feel free to leave a comment here and i'll take it under advisement, but the chances of it being done are highly dependent on my mood. Why not download the source and try and change it yourself?