About Virtualization, VDI, SBC, Application Compatibility and anything else I feel like
A while ago I included a new undocumented API into my JwaWinsta unit which is called WinStationServerPing. This API “pings” a Terminal or Citrix server and verifies that Terminal Server is up and running. It is not the same as a regular networking ping! This API actually makes a connection to a (remote) Terminal Server and verifies that Terminal Server runs and accepts connections.
I wrote a small cmdline tool that uses this API to ping a Terminal Server which can be used to quickly determine if a Terminal Server is up and running. I named it WTSPing.
So how does it work? Open up a command prompt (Start -> Run -> cmd) and type WTSPing /? to see the help:
WTSPing (c) Remko Weijnen 2008, www.remkoweijnen.nl
Pings a Terminal Server with the WinStationServerPing API.
WTSPing [/SERVER:servername] [-n count]
/SERVER:servername Specifies the Terminal server (default is current).
-n count Number of echo requests to send (default is 3).
If you just type WTSPing it will ping the local Terminal Server 3 times:
You can specify the number of pings with the -n parameter (eg -n 5). If you want to ping a remote server specify the server name with the /SERVER: parameter (eg /SERVER:MYSERVER).
Please note that Vista and Server 2008 do not support this API call from or to remote systems.
Have fun with it and let me know if you like it!
Download: WTSPing (1880)
.NET .NET FrameWork Active Directory Altiris Apple Automation Manager Citrix Dell Delphi Excel Exchange Exchange2003 Exchange2010 Hack HP iOS Java LinkedIn Linux Lync MSI Office Office 2010 Passat Password PowerPoint PowerShell RES RNS510 SasLibEx SCOM Security Terminal Server ThinApp TSAdminEx VBS VCDS Visual Basic Visual Studio VMWare Volkswagen VW Windows PE Wordpress XenApp