I'm currently testing TSClient with a home brew extension for SSL-Explorer to publish 2X apps through their secured gateway. This work really well, the apps get launched seamlessly and work faster than using 2X's build-in SSL function. There is just one "but". After closing the last application of a session, i've to wait for about 30 secs before the TSClient.exe will close itself. If you immediately logout of SSL-Explorer, the client will try to reconnect the disconnected session, which, of course, won't work. SSL-Explorer has an option to wait x secs before closing down the tunnel, but somehow the TSClient will stay alive while the session has been logged off. Long story short: A command line parameter to specify how long a session should be kept alive would probably solve this. Then I could say it should logoff after 1 second, so TSClient.exe will exit fast enough. If there is already some trick to do this, please let me know! Thanks.
In version 6 (already available in beta), the administrator can set this timeout value. Server properties -> Publishing session timeout. Nixu
