March 21, 2014 - Sven Huisman

Horizon Workspace ThinApp non-domain joined access

With Horizon Workspace 1.8 it is now possible to allow non-domain joined machines to use ThinApp packages from Horizon Workspace. In previous versions, clients needed to be domain joined to start ThinApp applications from Workspace.

There is a new feature to enable this, called “account-based access“. This feature is enabled on the Connector-va on which the ThinApp synchronization is configured. As in previous versions, the ThinApp packages must reside on a network share, and this network share must be accessible using a Uniform Naming Convention (UNC) path from each system running the Workspace client used to access the ThinApp packages. This means that clients still needs to be connected to the LAN (or through VPN or Direct-Access for example). Once the ThinApp packages are locally cached (through the Workspace client), the ThinApps can also be used outside the LAN.

  • Login to the connector-va (https://connector-va:8443)
  • Go to “Packaged Apps > ThinApp”
  • Check “Enable account based access“:

enable-access

 

 

  • Enter the share user and password and click “Save”:

enable-access2

 

Account based access is now enabled. Users can now access ThinApp applications from Horizon Workspace from a non-domain joined computer with a Horizon Workspace client.

I hope that the next version of Horizon Workspace will enable streaming ThinApps through the Horizon Gateway-va, so user don’t need to be connected to the LAN.

Workspace Management Horizon / Thinapp / Workspace /