Command-Line Installer Options for Omnissa Access Desktop

In silent mode, no messages, dialog boxes, or prompts are displayed during installation You typically use this option when creating a deployment script to run the installer.

If you don't specify a log file, a default log in %TEMP% is used.

Use the following format:

WORKSPACE_SERVER="https://WorkspaceONEAccessFQDN"

or

WORKSPACE_SERVER="WorkspaceONEAccessHostName"

For example:

WORKSPACE_SERVER="https://myserver.example.com" WORKSPACE_SERVER="myserver"

• COPY_TO_LOCAL: The user's entitled packages are downloaded to the client Windows system using a file copy. When the user launches a ThinApp package, the virtualized application runs locally on that system. Before the user's first download and use of an entitled ThinApp package and to continue synchronizing the packages to the client Windows system, the client Windows system must join the same Active Directory domain to which the ThinApp packages' network share is joined. The user account used to log in to the Windows system is the account that 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.
  
  

  Important: COPY_TO_LOCAL mode requires the ThinApp share to be reachable from the user's Windows system.

• HTTP_DOWNLOAD: The user's entitled packages are downloaded to the client Windows system using the HTTP protocol. When the user launches a ThinApp package, the virtualized application runs locally on that system. The Omnissa Access Desktop application uses the user's Omnissa Access system account to authenticate to Omnissa Access to obtain the list of the user's entitled packages to download. The share user account provided in the Omnissa Access console is the account used by Omnissa Access to access the ThinApp packages from the repository. That share user account for Omnissa Access needs read permission on the network share. The account that the user used to log in to the client Windows system and the user's Omnissa Access system account do not need to have any permissions on the network share. The client Windows system does not have to join the same domain to which the ThinApp packages' network share is joined. This download method is typically slower than using the other modes. The benefit to this mode is that the client Windows system does not have to join the Active Directory domain to obtain and run the virtualized application.
  
  

  Important: HTTP_DOWNLOAD mode requires the Base Download URL, which you set in the ThinApp virtual apps collection, to be reachable from the user's Windows system.

• RUN_FROM_SHARE: The virtualized application is streamed to the client Windows system from the network share when the user launches the ThinApp package. The RUN_FROM_SHARE option is best suited for Windows systems that will always have connectivity to the network share where the ThinApp packages reside, because the ThinApp packages are not present on the Windows system and the virtualized applications only run if the Windows system can connect to the network share. The client Windows system must join the same Active Directory domain to which the ThinApp packages' network share is joined. The user account used to log in to the Windows system is the account that 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.
  
  

  Important: RUN_FROM_SHARE mode requires the ThinApp share to be reachable from the user's Windows machine.

For all of the modes, the network share must have the appropriate file and sharing permissions configured.

Important: When installing Omnissa Access Desktop in floating Horizon desktops, use the RUN_FROM_SHARE option to avoid copying the ThinApp packages into those stateless Horizon desktop systems.

When the Omnissa Access Desktop application is installed with one of the following configurations, the user account that logs into the Windows system must have the appropriate file and sharing permissions on the network share to be able to obtain the ThinApp packages:

• The RUN_FROM_SHARE option
• The COPY_TO_LOCAL option, without also having the AUTO_TRY_HTTP option enabled

For example:

POLLING_INTERVAL=600

Set the value of this variable to 0 to turn off automatic update. If unspecified, the default value of 1 applies. Installation of automatic updates requires administrator privileges.

If unspecified, the default value of 0 applies, and each Windows user account gets its own cache.

Note: If you specify a shared cache, the Omnissa Access Desktop application does not automatically delete ThinApp packages from this shared cache. Because SHARED_CACHE=1 indicates that all user accounts on the Windows system share the same location, the packages must remain in the shared location so that entitled users can use them, even when you unentitle one user. When you unentitle a user from a ThinApp package, the Omnissa Access Desktop application unregisters that package for that user. Other entitled users on that Windows system can continue to use the ThinApp package. You can delete the common cache manually to reclaim the space if no user accounts on that Windows system are entitled to use the ThinApp packages. Each ThinApp package has its own folder under the cache location.