Piszki Lab | EN

My case study in the clouds…

Horizon Workspace: ThinApp applications on computer that is not a member of AD

| 0 comments

An absolute novelty that appeared in the Horizon Workspace 1.8 is the ability to use ThinApp application on computers that are not members of an Active Directory domain. This means, that you can connect from the Internet, from any computer to our Workspace website and run ThinApp. With little restriction, in this version, you can run only “full” applications, there is no the possibility of streaming applications over the Internet. It is also necessary to install an client of VMware Horizon Workspace (ThinApp applications need to act HorizonPlugin.dll). After a quick install we can collide with the following error (Failed to copy file: The network path was not found):

work0

work1

This is due to the fact that the default installation of Horizon Workspace 1.8.1 does not have enabled the option “Enable account based access“. To enable it, we need to log in to configurator-va and go to the Packaged Apps – ThinApp:

work2

The account used to access the application must be a domain account with permission to read the contents of the UNC path with the applications.

work3

In the next step, we carry out synchronization ThinApp applications and check alerts if everything is ok (we should see a new path /mnt/ThinApp).

work4

 

work5

At this stage, everything is prepared and working properly. We can go back to the Horizon Workspace client (our quick installation we withdraw). Following the documentation, you must install the client from the command line with the parameter set INSTALL_MODE = HTTP_DOWNLOAD.

work7

If you plan to use 64-bit applications (which support appeared only in version 1.8), we need to perform some additional steps . After installing the Workspace client, HorizonPlugin.dll need to be moved from the directory c:\windows to the directory c:\windows\SysWOW64 and then download the 64-bit dll version from the connector-va (/opt/vmware/thinapp-plugin-x64) and upload to c:\windows\system32 (a bit strange but true).

Was this information is helpful? Tell me, please leave a comment!

Source

Rate this article:
[Total: 0    Average: 0/5]

Author: Piotr Pisz

Computer always, since I got a Commodore 64 at the end of primary school, through his beloved Amiga and Linux infinite number of consoles, until today, fully virtual day. Since 2001, Unix/Linux Systems Administrator, for seven years a faithful companion and protector of Solaris system, until his sad end. In the year 2011 came in the depths of virtualization, then smoothly ascended into the clouds and continues there today. Professionally working as Systems Architect in the Polish Security Printing Works.

Leave a Reply

Required fields are marked *.


.

Enjoyed the post? Support Piszki Lab | EN, click on the AD! :-)

.