Here's what I found. Its not very much detail.... Application Server and Load Balancer Version 5.1.0 (303) - 24th Aug 2007 Server: Support for Unicode Paths, Usernames and passwords. Support for Japanese Language. Support for Russian Langauge. Improved Log Messages. Support for usernames longer than 21 characters. Support for NonProfit License Keys. Improved Universal Printing. Bug Fix - Modeless minimized widow were not shown. Improved speed when creating windows for misbehaving applications. Fixed Drag and Drop shortcuts for MS Office Applications. Client: Support for Unicode Paths, Usernames and passwords. Support for Japanese Language. Support for Russian Langauge. Improved installation via GPOs. Added option to switch language.
Still missing pasthru authenticating and support for nested groups. sniff...still awesome product ! Cheers Impuls Belgium
singlesignon is coming in version 6 which is due q4 of this year in beta along with a whole host of new and exciting features.
Despite my initial frustrations, I am using 2x successfully in most cases. I am excited about the new changes. The double logon is something that would simplify the use of 2x. I hope that you guys also address the connection issue. Well... the connetion issue is ours, but the 2x client could be more forgiving of it. I have several users who access the server via the internet who cannot use the 2x client because it kicks you out too quickly. The use the remote desktop window instead. I guess 2x needs to get out in front of the impending Terminal Server 2008 which will have the same application tunnelling process.
I use 2x app server to tunnel applications over the internet to various people and clients. We actually like 2x because it is a much better interface than the standard remote desktop that we were using. But, if the user does not have an absolutely perfect internet connection, then you can't use 2x client. After being disconnected for 5 seconds, you are kicked out of the application and then you see the 2x client trying to connect again. It times out after about 30 seconds. If my clients use dsl, which can be flakey, then they get disconnected all the time. Instead, I have to move them back to remote desktop. If they are connectted for up to a minute, you can wiggle the mouse and the session will continue. You can see this by simply removing the network cable from your computer. Remote desktop client is more forgiving than 2x client. I know we need to have the clients fix their networks. But the reality is that we have to deal with them. This is the issue that has stopped me from buying 2x app server for the other 4 servers that we use to publish applications.
I agree with mauricedorris, and there is even a more serious issue when someone's VPN drops out (at least on Vista). The published application (TSClient) will no longer respond, without the 2X app launcher noticing the disconnect. That's probably why the TSClient will hang instead of close. If this one could be addressed, I would be very grateful
I tried to re-produce the problem, but now it seems to detect the link-failure after about 20 sec (with ConnTimeout set to 5) and then tries to reconnect. Somehow it seems to ignore ConnTimeout, I set both HKLM and HKCU values to 5. That one worked before, not sure why it's now falling back to default.. The vpn is btw a dial-in pptp.
