Before your Workspace ONE Access users can run their ThinApp packages that are registered to them using Workspace ONE Access, those users must have the Workspace ONE Access Desktop application installed and running on their Windows systems.

ThinApp packages are virtualized Windows applications. The ThinApp packages are distributed to Windows systems, and a user logged into the Windows system can launch and run those ThinApp packages that are registered on that Windows system. Workspace ONE Access can distribute and manage ThinApp packages that are compatible with Workspace ONE Access.

To successfully launch and run one of these virtualized applications in the user's logged-in Windows session, the following elements are required:
  • The virtualized application's ThinApp package is registered for that user's use by Workspace ONE Access.
  • A particular DLL is available on that Windows system.
  • The hws-desktop-client.exe process is running.
When a compatible ThinApp package is created, it is configured to load a particular DLL when the logged-in user launches the virtualized application in their logged-in Windows session. At that time, the virtualized application attempts to load the DLL. When the DLL is loaded, it attempts to verify with the locally installed Workspace ONE Access Desktop application whether that ThinApp package is registered on that Windows desktop for that user. The locally installed Workspace ONE Access Desktop application determines whether that application is registered for that user without communicating with Workspace ONE Access. If the application is registered on that Windows desktop for that user, the Workspace ONE Access Desktop application checks to see when it last synced with Workspace ONE Access. If the Workspace ONE Access Desktop application confirms that the time from the last sync is within the offline grace period configured for the installed client, the client allows the application to run.

Because that DLL is available on the Windows system only if the Workspace ONE Access Desktop application is installed, and because the hws-desktop-client.exe process is running if the Workspace ONE Access Desktop application is running on that system, the Workspace ONE Access Desktop application must be installed on the Windows system to run ThinApp packages that are distributed and managed by Workspace ONE Access.

Deploying the Workspace ONE Access Desktop Application To Use ThinApp Packages

The Workspace ONE Access Desktop application can be installed by either double-clicking its installer EXE file, running the executable file using the command-line options, or running a script that uses the command-line options. Local administrator privileges are required to install the application. For information about installing the Workspace ONE Access Desktop application by double-clicking its installer EXE file, see the Workspace ONE Access Desktop User Guide.

The configuration of the installed application determines how a ThinApp package that is distributed by Workspace ONE Access is deployed to that Windows system. By default, when the Workspace ONE Access Desktop application is installed by double-clicking its installer EXE file, the client is configured to deploy ThinApp packages using the COPY_TO_LOCAL deployment mode, with the AUTO_TRY_HTTP option enabled. Those default installer options result in what is called a download deployment mode. With the COPY_TO_LOCAL and AUTO_TRY_HTTP default settings, the client application first tries to download the ThinApp packages by copying them to the Windows system endpoint, and if the first attempt fails, the client application tries to download the ThinApp packages using HTTP.

If Workspace ONE Access is configured for account-based access to your ThinApp repository, the client application can download the ThinApp packages using HTTP. After the ThinApp packages are downloaded to the local Windows system, the user runs the virtualized applications on the local system.

To avoid having the virtualized applications downloaded to the local Windows system and using space on the Windows system, you can have users run the ThinApp packages from the network share by using what is called a streaming deployment mode. To have your users run the ThinApp packages using streaming mode, you must install the Workspace ONE Access Desktop application on the Windows systems using a command-line installation process. The installer has command-line options that you can use to set the runtime deployment mode for the ThinApp packages. To set the runtime deployment mode to stream the ThinApp packages, use the RUN_FROM_SHARE installer option.

One method for installing the Workspace ONE Access Desktop application to multiple Windows systems is to use a script to install the application silently to the Windows systems. You can install the client silently to multiple Windows systems at the same time.
Note: A silent installation does not display messages or windows during the install process.
You set a value in the script to indicate whether the clients installed by that script deploy ThinApp packages using the ThinApp streaming mode, or RUN_FROM_SHARE option, or one of the ThinApp download modes, such as the COPY_TO_LOCAL or HTTP_DOWNLOAD option.

Determining the Appropriate Deployment Mode for ThinApp Packages on Windows Endpoints

The configuration of the Workspace ONE Access Desktop application on the Windows endpoint determines whether a ThinApp package that is distributed using Workspace ONE Access is deployed using ThinApp streaming mode, RUN_FROM_SHARE, or one of the ThinApp download modes, COPY_TO_LOCAL or HTTP_DOWNLOAD. When you create the script to silently install the Workspace ONE Access Desktop application to Windows endpoints, such as desktop and laptop computers, you set the options that set the ThinApp package deployment mode. Choose the deployment mode that best fits the network environment for the selected endpoints, considering details such as network latency.

With streaming mode, when the Workspace ONE Access Desktop application synchronizes with Workspace ONE Access, the client downloads application shortcuts for the ThinApp packages' virtualized Windows applications to the Windows desktop, and when the user launches the ThinApp packages, the virtualized Windows applications run from the file share on which the ThinApp packages reside.

Therefore, streaming mode is appropriate for systems that will always be connected to the network share, such as Horizon desktops.

With download mode, at the first use or update of a ThinApp package, the user must wait for the ThinApp package to download to the Windows system first, and shortcuts to be created. After the initial download, the user launches and runs the virtualized Windows application on the local Windows system.

Important: For non-persistent Horizon desktops, also known as floating or stateless Horizon desktops, you are expected to set the client to use ThinApp streaming mode by using the command-line installer option /v INSTALL_MODE=RUN_FROM_SHARE when installing the client. The RUN_FROM_SHARE option provides the most optimal runtime experience for using ThinApp packages in floating Horizon desktops. See Command-Line Installer Options for Workspace ONE Access Desktop.
Important: HTTP_DOWNLOAD mode requires the IDP URL to be reachable from the user's Windows machine. RUN_FROM_SHARE and COPY_TO_LOCAL modes require the ThinApp share to be reachable from the user's Windows machine.
Table 1. ThinApp Deployment Mode for the Virtualized Applications Captured as ThinApp Packages
Mode Description
ThinApp streaming mode In ThinApp streaming mode, the virtualized applications are streamed each time they are started. This method avoids using disk space in the desktop that would be used when copying the virtualized applications to the desktop. The desktop must be connected to the ThinApp packages' network share for the applications to run.

The following environments might provide the consistency and stability required:

  • Horizon desktops, either stateless or persistent, with excellent connectivity to the file share on which the ThinApp packages reside.
  • Users with Windows desktops that are not Horizon desktops, that are shared by multiple users. This situation avoids the accumulation on disk of downloaded user-specific applications and also provides quick access to applications without causing a delay for downloads specific to a user.

The account that the user uses to log in to the Windows system is used to obtain the ThinApp packages from the network share. That account must have the appropriate permissions on the network share to read and execute files on the network share.

ThinApp download mode In ThinApp download mode, applications are downloaded to the Windows endpoint. The user runs the virtualized application locally on the endpoint. You might prefer ThinApp download mode for the following situations:
  • Persistent Horizon desktops
  • LAN-connected desktops that are periodically offline
  • A LAN with poor network latency

Workspace ONE Access provides two flavors of the ThinApp download mode: COPY_TO_LOCAL and HTTP_DOWNLOAD. If the client is configured for COPY_TO_LOCAL, the Windows endpoint must be joined to the same domain as the file share unless the AUTO_TRY_HTTP option is enabled and Workspace ONE Access is configured for account-based access to the ThinApp packages' network share.

When the AUTO_TRY_HTTP option is enabled and Workspace ONE Access is configured for account-based access, if the Windows endpoint is not joined to the same domain and the first attempt to download the ThinApp packages fails, the Workspace ONE Access Desktop application will automatically try to download the ThinApp packages using the HTTP protocol as for the HTTP_DOWNLOAD mode. With HTTP_DOWNLOAD, the Windows endpoint does not have to be joined to the same domain as the file share. However, the copy and sync times when using HTTP_DOWNLOAD are significantly longer than when using COPY_TO_LOCAL.

Important: If Workspace ONE Access is not enabled for account-based access, downloading using the HTTP protocol does not work, even if AUTO_TRY_HTTP is enabled or the client is configured with the HTTP_DOWNLOAD option.

When using COPY_TO_LOCAL, the account that the user uses to log in to the Windows system is used to obtain the ThinApp packages from the network share. That account must have the appropriate permissions on the network share to read and copy files from the network share. When using HTTP_DOWNLOAD, the share user account that you enter in the Workspace ONE Access console when you configure access from Workspace ONE Access to the ThinApp packages' network share is the account that is used to download the ThinApp packages. That share user account needs to have read permission on the ThinApp packages' network share to copy the files from the network share.

The ThinApp packages' network share must meet the appropriate requirements for the deployment mode that you set for the Windows endpoints. See Workspace ONE Access Installation and Configuration.