In addition to Web applications, you can integrate Horizon desktops and applications, Horizon Cloud desktops and applications, Citrix published applications and desktops, and ThinApp packaged applications with Workspace ONE UEM console. These resources are called Virtual Apps in the Workspace ONE UEM console interface and are managed through the Virtual Apps Collections feature.
You can create a single virtual apps collection or multiple collections for any type of resource except ThinApp packages for which you can only create a single collection. For example, to integrate a deployment of 50 Citrix XenApp farms, you can set up 10 virtual apps collections in Workspace ONE UEM console, with five farms in each collection. This allows for easier management of the configuration and faster sync as each collection is synced separately. You can also use different connectors for each collection to distribute the sync load.
The Virtual Apps Collections page, accessed by navigating to Resources > Apps > Virtual Apps > Virtual Apps Collections in the Workspace ONE UEM console, provides a central location for managing all your resources integrations. You can create and edit collections, monitor the sync status of all collections, view alerts, and sync manually from this page.
Note : Integration with ThinApp packaged applications is only supported with the Linux Workspace ONE UEM connector. It is not supported with the Windows connector.
The virtual apps collections feature provides the following benefits:
The virtual apps collection feature has the following requirements:
Workspace ONE UEM configuration requirements :
You can get started with virtual apps collections directly or follow a migration path, depending on your installation scenario. In new installations, you can create new virtual apps collections for Horizon, Horizon Cloud, Citrix, or ThinApp resources directly. If you upgrade to Workspace ONE UEM 1903 and all your connectors are version 2017.12.1.0 or later, you must migrate any existing configurations that were still being managed through the Manage Desktop Applications user interface to virtual apps collections.
If you are upgrading to Workspace ONE UEM 1903 and all your connectors are version 2017.12.1.0 or later, select the Resources > Apps > Virtual Apps > Virtual Apps Collections tab. Review the information on the page and click Get Started to use the Migration wizard.
After you migrate the existing configurations, the new Virtual Apps Collections page is enabled, allowing you to view and edit the migrated configurations and create new ones. To access the page at any time, select the Resources > Apps > Virtual Apps > Virtual Apps Collections tab.
If you are upgrading from an earlier release and you have at least one connector, standalone or embedded, that is older than version 2017.12.1.0, you cannot create new virtual apps collections. Upgrade all connectors to 2017.12.1.0 or later, then use the Migration wizard to migrate your existing configurations to virtual apps collections.
Use the Migration wizard to migrate existing resource configurations from the Manage Desktop Applications user interface available in previous releases to virtual apps collections.
You must migrate all existing resource configurations at the same time. For example, if you have Horizon Cloud and Citrix resources configured, select both in the Migration wizard. The Migration wizard is intended to be used only once to migrate all the resources at the same time. After it is run once, it will no longer be available. In a hosted environment, the migration process might take some time.
The existing resource configurations are migrated. A virtual apps collection is created for each type of configuration. These collections are displayed in the Virtual Apps Collections page that appears after migration is complete. To view or edit a collection, click its name. To access the Virtual Apps Collections page at any time, select the Catalog > Virtual Apps Collections tab.
For troubleshooting information on virtual apps collections, view both the connector log file, connector.log, and the service log file, horizon.log. On Linux virtual appliances, the log files are in the /opt/vmware/horizon/workspace/logs directory. On Windows servers, the log files are in the install_dir\IDMConnector_or_VMwareIdentityManager\opt\vmware\horizon\workspace\logs directory.
You can create one or more virtual apps collections for each type of integration such as Horizon Cloud or Citrix published resources.
Complete the following steps before you create Virtual Apps Collections:
Integration with ThinApp packaged applications is only supported with the Linux Workspace ONE UEM connector. It is not supported with the Windows connector.
In the Workspace ONE UEM console, navigate to Resources > Apps > Virtual Apps > Virtual Apps Collections >New.
Select the Source Type. You can select the type of resource to integrate.You can select Horizon, Horizon Cloud, Citrix published applications, or ThinApp packages as source types.
Note: Integration with ThinApp packaged applications is only supported with the Linux.
Workspace ONE UEMconnector. It is not supported with the Windows connector.
Follow the New Collection wizard to create the collection.The configuration information for each type of integration is different.Some fields, such as the following, appear for all source types.
|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. To rearrange the list, click and drag the rows to the desired position.
Note:After you create the collection, you cannot select a different connector for the collection.
|Sync Frequency||Select when and how frequently you want to sync the resources in the collection. The sync frequency can range from hourly to weekly. If you do not want to set up an automatic sync schedule, select Manual.|
|Activation Policy||Select how you want to make resources in this collection available to users in the Workspace ONE 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 Catalog page. Users can use the resources from the Catalog page or move them to the Bookmarks page. 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.
After you create the collection, you can view and edit the collection from the Virtual Apps Collections page.The resources in the new collection are not synced yet. If you set a sync schedule for the collection, the resources are synced at the next scheduled time. To sync the resources manually, select the collection in the Virtual Apps Collections page and click Sync.
You can edit all the virtual apps collections, for all types of integrations, from the Virtual Apps Collections page in the Workspace ONE UEM console.
Before you edit the Virtual Apps Collections, the following administrator roles are required:
To create, edit, or delete ThinApps collections, use any role that can perform the Manage ThinApps action in the Catalog service.
In the Workspace ONE UEM console, navigate to Resources > Apps > Virtual Apps > Virtual Apps Collections tab.
In the Edit Virtual Apps Collection wizard, edit the collection and save your changes.You can change the following settings:
In a Horizon virtual apps collection, you cannot modify the FQDN of a Horizon pod that was previously added. Remove the pod from the collection and add it again.
As a best practice, sync the collection after editing it. Go to Resources > Apps > Virtual Apps > Virtual Apps Collections page, select the collection, and click Sync.
You can sync a virtual apps collection at any time from the Virtual Apps Collections page, regardless of whether you selected an automatic or manual sync schedule for the collection. Syncing a collection propagates resources and entitlements from the source server to Workspace ONE UEM.
Select the virtual apps collection to sync, and click Sync.Workspace ONE UEM compares resources and assignments between the source and the Workspace ONE UEM catalog and displays the Calculating Sync Actions dialog box.
If the resources and assignments match, the following message appears All resources are up to date. Sync is not needed.
If there are changes in the source that need to be propagated to Workspace ONE UEM, the Calculating Sync Actions dialog box displays the number of applications, desktops, and user assignments that require syncing.
Click Save in the Calculating Sync Actions dialog box.The sync process starts and might take some time to complete, depending on the number of resources and assignments that require syncing. When the sync is completed, the Sync Status in the Virtual Apps Collections page changes from Started to Sync Completed.
You can monitor the sync status of all your resource integrations from the Virtual Apps Collections page. For each virtual apps collection, you can view the time the resources were last synced, whether the sync was successful or not, which resources and assignments were synced, and whether any alerts occurred during the sync.
View the information for each collection.
|The sync schedule that is set for the collection||The Sync Frequency column. If you did not set an automatic sync schedule, the column displays Manual. With a Manual setting, you must sync the virtual apps collection manually each time you want to propagate any changes in resources or entitlements from the source servers toWorkspace ONE UEM .
Workspace ONE UEM.
|The time of the last sync attempt||The Last Sync Attempt column.|
|The status of the last sync||The Sync Status column displays one of the following states:
1. Not yet synced: The virtual apps collection has never been synced.
2. Dry Run Completed: When you click Sync to sync a virtual apps collection manually before it performs a sync,
Workspace ONE UEM calculates the number of applications, desktops, and assignments that require syncing and displays the results in the Calculating Sync Actions dialog box. At this point, the status is Dry Run Completed. The sync task is started after you click Save.
3. Started: The sync process has started.
4. Failed to start sync: The sync process cannot start because the previous sync is in progress.
5. Sync Completed: The sync process is complete.
6. Failed to complete sync: The sync process was not completed. For example, if a network issue prevented the connector from reaching the server from which to sync resources, sync is not completed.
7. Not all resources and entitlements were synced: Some resources and entitlements were not synced because the sync process was not completed.
|Desktops, applications, and entitlements that were added or deleted in the last sync||Click More in the Sync Status column and click the information icon.
The Sync Action Summary dialog box lists the number of applications, desktops, and assignments that were added, deleted, or updated in the last sync.
To view the names of the applications, desktops, or assignments, click the links.
|Alerts||Click More in the Sync Status column and click the alert icon.
The Sync Alerts dialog box displays alert that occurred during sync. For example, if there are assignments for a user that does not exist inWorkspace ONE UEM, an alert appears.
Note: The Sync summary history is visible only if all the connectors are upgraded to the latest. Alerts are not separated by collection or by sync run. All alerts appear in the list, including directory sync alerts.