To configure Workspace ONE Access to provide users access to ThinApp packages, you create a virtual apps collection which contains configuration information such as the path to the storage location of the packages, the connector to use for sync, and the sync schedule.

You can only create a single virtual apps collection for all your ThinApps integrations.

Prerequisites

  • Create a network share with the appropriate configuration and store the ThinApp packages in the appropriate location in that network share. See Create a Network Share for ThinApp Packages That Workspace ONE Access Manages.
  • Verify that you have the UNC path to the network share folder where the ThinApp packages are located.
  • If the connector is not already domain-joined, verify that you have an Active Directory domain name and the username and password of an account in that Active Directory that has the rights to join the domain. Even if you are using account-based access, the Workspace ONE Access console requires the completion of the Join Domain page for legacy Linux connectors before you can use the ThinApp Packages page.

    To enable domain-based access, you must also join the connector to the same Active Directory domain to which the ThinApp package repository is joined. Verify that you have the Active Directory domain name for the domain that the network share uses and the username and password of an account in that Active Directory that has the rights to join the domain. The Active Directory account is used to join the connector to the domain.

  • When enabling account-based access, verify that you have a username and password that has permission to read the network share. See Workspace ONE Access Requirements for ThinApp Packages and the Network Share Repository.
    Note: Unless you want to restrict use of the ThinApp packages to domain-joined Windows systems for all runtime situations, you should enable account-based access in addition to domain-based access. This combination provides the most flexibility for supporting runtime situations where users need to use their entitled ThinApp packages without joining their Windows systems to the domain.
  • You must use an administrator role that can perform the Manage ThinApps action in the Catalog service.

Procedure

  1. (Legacy Linux connector only) If the connector is not already domain-joined, join it to the Active Directory domain.
    Your Workspace ONE Access deployment can have multiple connector instances. The instance that you configure in this procedure will be the instance that synchronizes ThinApp packages with Workspace ONE Access.
    1. Log in to the Workspace ONE Access console.
    2. Select the Identity & Access Management tab.
    3. Click Setup.
    4. In the Connectors page, click Join Domain in the appropriate connector row.
    5. On the Join Domain page, type the information for the Active Directory domain and click Join Domain.
      Important: Do not use non-ASCII characters when you enter the Active Directory (AD) domain name, AD username, or AD password. Non-ASCII characters are not supported in these entry fields in the Workspace ONE Access console.
      Option Description
      AD Domain Type the fully qualified domain name of the Active Directory. An example is HS.TRDOT.COM.
      AD Username Type the username of an account in the Active Directory that has permissions to join systems to that Active Directory domain.
      AD Password

      Type the password associated with the AD Username. This password is not stored by Workspace ONE Access.

    The Join Domain page refreshes and displays a message that you are currently joined to the domain.
  2. Select the Catalog > Virtual Apps Collections tab.
  3. Click New.
  4. Select ThinApp Package as the source type.
  5. In the New ThinApp Collection wizard, enter the following information in the Connector page.
    Option Description
    Name Enter a unique name for the ThinApp collection.
    Connector Select the connector that you want to use to sync this collection. To select the connector, select the directory that is associated with it. If you have set up a cluster of connectors, all the connector instances appear in the Host list and you can arrange them in failover order for this collection.
    Important: After you create the collection, you cannot select a different directory.
  6. Click Next.
  7. In the Configuration page, enter the required information.
    Option Description
    Path The path to the shared folder where the ThinApp packages' folders are located, in the UNC path format \\server\share\subfolder. For example: \\DirectoryHost\ThinAppFileShare. For DirectoryHost, provide the host name, not the IP address.

    For both CIFS and DFS network shares, this path must be a directory under the namespace, and not the namespace itself.

    Enable Account Based Access Account based access is required in the following cases:
    • For NetApp storage systems and other brands of DFS network shares
    • If you are using HTTP download deployment mode
    • If you want users to be able to use their entitled ThinApp packages on non-domain-joined Windows systems
    Share User The username for a user account that has read access to the network share.

    The Share User is required to enable account based access to the stored ThinApp packages.

    Share Password The password associated with the Share User user account.
    Sync Frequency Select how often you want to sync the resources in the collection.

    You can set up an automatic sync schedule or choose to sync manually. To set a schedule, select the interval such as daily or weekly and select the time of day to run the sync. If you select Manual, you must click Sync on the Virtual Apps Collections page after you set up the collection and whenever there is a change in your Horizon Cloud resources or entitlements.

    Activation Policy Select how you want to make resources in this collection available to users in the Workspace ONE Intelligent Hub portal and app. If you intend to set up an approval flow, select User-Activated, otherwise select Automatic.

    With both the User-Activated and Automatic options, the resources are added to the Apps tab. Users can run the resources from the Apps tab or mark them as favorites to run them from the Favorites tab. However, to set up an approval flow for any of the apps, you must select User Activated for that app.

    The activation policy applies to all user entitlements for all the resources in the collection. You can modify the activation policy for individual users or groups per resource, from the user or group page in the Users & Groups tab.

  8. Click Next.
  9. In the Summary page, review your selections, then click Save.
    The collection is created and appears in the Virtual Apps Collections page. The applications are not synced yet.
  10. To sync the applications in the collection, select the collection in the Virtual Apps Collections page and click Sync.
    Each time ThinApp applications change, a sync is required to propagate the changes to Workspace ONE Access.

Results

Workspace ONE Access is now configured so that you can entitle groups and users to ThinApp packages, and those users can run their entitled ThinApp packages using the Workspace ONE Access Desktop application installed on their Windows systems.

What to do next

Entitle groups and users to ThinApp packages.