I am currently testing out different gateway clients to access our VM View setup. We went with View initially because of the ease of provisioning and updating a base image to a pool of users. We will also be deploying Wyse R50L's after our testing phase is done to replace desktops at the office. We had 2 choices as far as our remotes. We could setup the VM Secure gateway or try to utilize the 2x Application server we already have in-place to now also access the Virtual Desktops along with the 2 terminal servers that host most of our applications. I setup a test gateway/VDS environment and was able to add a deployed VM View desktop, but was unable to launch it. I cloned the master image and added it to 2x and was able to access it without any problems. The master image contains the View agent, so that isn't preventing access, so I'm assuming that the View server itself is locking down the desktop preventing the 2x agent to be utilized. Is there any way to get the two to live together in peace, so we have the ease of management of pools, the end user at the office can utilize the View connection directly, and remotes can leverage their 2x client to connect to the whole environment?
The vmview client should be publishable I have it here and it seems to work well. (If I understood well yours is failing) . I see no reason why this should not work. If you can describe exactly the error you get ( check your logs in both systems + windows) and give a simplest form to reproduce the error there might be some thing small you are missing.
