Migrating ThinApp Virtual Apps Collections to Omnissa Access Connector 22.09

Omnissa Access connector 22.09 supports integration with ThinApp packaged applications, which were previously supported only by the Linux-based Identity Manager connector version 2018.8.1.0. You can now migrate your ThinApp virtual apps collections from the Linux 2018.8.1.0 connector to the Windows 22.09 connector.

Migrating ThinApp virtual apps collections is a two-step process. You first migrate the Linux 2018.8.1.0 connector to the Windows 19.03.0.1 connector. Then, you migrate from version 19.03.0.1 to version 22.09.

Performing all the stages of the migration in quick succession is recommended.

Prerequisites

• Only ThinApp packages built using ThinApp runtime 2206 can be migrated.
• Before starting the migration, take snapshots of the Omnissa Access service virtual appliances, connectors, and database.
• (Omnissa Access on premises installations) Migrate the Omnissa Access virtual appliance to version 22.09 before beginning the connector migration.
• Prepare a Windows server for the 22.09 connector. See Requirements for Migrating to Omnissa Access Connector 22.09.
• Download Identity Manager Standalone Connector 19.03.0.1 Installer for Windows from the Omnissa Access Connector Download page and copy it to the Windows server.
• Download Omnissa Access Connector 22.09 from the Omnissa Access Connector Download page and copy it to the Windows server.
• Download the cluster-support.tgz file from the Omnissa Access Connector Download page and copy it to the 2018.8.1.0 Linux connector virtual appliance.

Procedure

1. Edit the config-state.json file on the Linux connector.

   1. Log into the Linux connector virtual appliance as the root user.

   2. Open the following file for editing:

      /usr/local/horizon/conf/states/${TENANT_ID}/${ID}/config-state.json

   3. In the appsConfig section, change the enabled flag to false.

   4. Save the file.

2. Migrate the Linux 2018.8.1.0 connector to Windows connector 19.03.0.1.

   The process includes downloading the generateClusterFile.sh script to the Linux connector, running the script to generate a cluster .enc file that contains the Linux connector configuration, then importing the cluster .enc file during the 19.03.0.1 Windows connector installation.

   See the following documentation for information:

   • Saving External Linux-Based Connector-Configuration Information in the Omnissa Access 19.03 upgrade documentation

   • Perform Migration-Related Steps when Configuring the External Windows-Based Connector in the 19.03 upgrade documentation

   • Installing and Configuring Identity Manager Connector 19.03 (Windows) Keep in mind the following considerations and requirements:

   • The 19.03 upgrade documentation states that Identity Manager Windows connector 19.03 does not support ThinApp packages. You can ignore these statements for the purposes of migration from the Linux connector to the 22.09 Windows connector.

   • Use a secure method, such as Secure File Transfer Protocol (SFTP), to transfer the connector configuration file from one server to another as the file contains sensitive information.

     To ensure security, also delete the configuration file from both the old and new servers after migration is finished, and delete old deployments that are no longer needed.

   • When you install the 19.03.0.1 Windows connector, in the Identity Manager Connector Service Account page, select the Would you like to run the Connector service as a domain user account? option and specify the domain user account to use.

   • After you migrate to the 19.03.0.1 connector, you cannot create, save, or sync ThinApp virtual apps collections, or launch ThinApp applications. Migrating to version 19.03.0.1 is only an interim step in the ThinApp migration from the Linux connector to the 22.09 connector. The 19.03.0.1 connector is not intended for use with ThinApp.

3. Verify that the ThinApp virtual apps collection appears on the 19.03.0.1 connector.

   • In the Omnissa Access console, select Integrations > Legacy Connectors and verify that the 19.03.0.1 connector appears.
   • Select Resources > Virtual Apps Collections and verify that the ThinApp virtual apps collection appears.
   • Select Resources > Virtual Apps and verify that the ThinApp packages appear.

4. Migrate from the 19.03.0.1 connector to the 22.09 connector by following the requirements, prerequisites, and procedures listed in this document, Migrating to Omnissa Access Connector 22.09.

   In the Preview stage of the migration, verify that the ThinApp virtual apps collection appears.

   • In the Omnissa Access console, select Resources > Virtual Apps Collections and verify that the ThinApp virtual apps collection appears.
   • Click the ThinApp virtual apps collection, and verify that the 22.09 connector host name appears under Connectors.
   • Select Resources > Virtual Apps and verify that the ThinApp packages appear.

What to do next

After you successfully complete the migration to Omnissa Access connector 22.09, verify that you can sync, create, and save the ThinApp virtual apps collection. Also, verify user assignments and application launch. You can then uninstall the Linux connector.