Hi there, ´ One thing I find lacking in 2X RAS is the ability to reconnect to existing (seamless application) sessions. Say I'm running Word, and I turn off my computer. Word is still running on the server. How can I get back to it? Sure I can retry running Word again, but either: a) I will see my old Word window a new Word window b) 2X (due to load balancing) will open the new Word window on another terminal server, and I'm never back to my old window. Currently I'm doing is publishing a blank application (one that does nothing and shows no window) on every single terminal server, and let users run the application to try to get back to the applications running. While this somehow works, it has the following shortcoming: a) Users are not aware applications are still running on a terminal server, so they may not reconnect to them b) Users must try every single terminal server until they get back to the one with the application (due to load balancing, they do not know where their running apps are This could be easily fixed by 2X: - As RAS knows what sessions and applications are running on each terminal server, they could send that information to the client when application list is sent - The client would then inform the user of running applications, and allow then to reconnect - The re connection would be simply running a blank application on terminal servers with application running for the current user Hope this gets into the product. All the other "competing" products work like this. See Horizon View (it shows a yellow info bar on the client saying "Application are running; [reconnect]" or Citrix Workspace Control. Regards, Ricardo
