Migrating to Omnissa Access Connector 22.09

Omnissa Access provides a migration path from Omnissa Access connector versions 19.03 and 19.03.0.1 to version 22.09. The migration process includes installing new 22.09 connectors and migrating your existing directories and virtual apps collections to the new connectors. You cannot directly upgrade connector version 19.03 or 19.03.0.1 to version 22.09.

To migrate to the 22.09 connector, you migrate all your directories and supported virtual apps collections. When you migrate the directories, all data, including authentication methods and identity providers, is migrated. When you migrate virtual apps collections, the virtual apps configurations are migrated. Migration is a one-time process, and you must migrate directories and virtual apps collections together.

Note: You can upgrade Omnissa Access connector versions 22.05, 21.08.x, 20.10.x, and 20.01.x to version 22.09. See the Upgrading to Omnissa Access Connector 22.09 guide.

About Omnissa Access Connector 22.09

Omnissa Access connector 22.09 is a collection of enterprise services that can be installed individually or together on Windows servers. It includes the following services:

• Directory Sync service: Syncs users from Active Directory or LDAP directories to the Omnissa Access service

• User Auth service: Provides connector-based authentication methods including Password (cloud deployment), RSA SecurID (cloud deployment), and RADIUS (cloud deployment)

• Kerberos Auth service: Provides Kerberos authentication for internal users

• Virtual App service: Syncs virtual apps from Omnissa Horizon®, Omnissa Horizon® Cloud Service on Microsoft Azure with Single-Pod Broker or Horizon Cloud Service on IBM Cloud, Citrix®, and Omnissa ThinApp deployments to the Omnissa Access service

  Note: Integration with Horizon Cloud Service on Microsoft Azure with Universal Broker is configured from the Horizon Cloud administration console and does not require the Virtual App service.

Compatibility with the Omnissa Access Service and Appliance

Omnissa Access connector 22.09 is compatible with the Omnissa Access Cloud service and with Omnissa Access virtual appliance version 22.09 and later versions only.

Federal Information Processing Standard (FIPS) Mode

Omnissa Access connector 22.09 can perform cryptographic operations using FIPS 140-2 compliant algorithms. FIPS mode is not supported when you migrate to the 22.09 connector.

Important: During the migration process, when you install the new 22.09 connector, the option to enable FIPS mode appears on the Specify Configuration File page of the installer. Make sure that you do not select the Enable FIPS option.

See Omnissa Access Connector and FIPS Mode in Installing Omnissa Access Connector 22.09 for more information about FIPS mode.

Note: The Omnissa Access connector in FIPS mode is only supported with Omnissa Access FedRAMP tenants. Other types of tenants and on-premises Omnissa Access installations do not support the connector in FIPS mode.

Use Cases for Migration to Connector 22.09

Migration from Omnissa Access connector version 19.03 or 19.03.0.1 to version 22.09 is applicable for certain use cases. Follow these guidelines to determine whether to migrate to version 22.09.

• If your deployment includes Horizon virtual apps, you can migrate to Omnissa Access connector 22.09. The 22.09 connector supports integration with Horizon 8 and Horizon 7.

  Caution: If you are using an earlier version of Horizon, do not migrate to the 22.09 connector.

• If your deployment includes Citrix virtual apps, you can migrate to Omnissa Access connector 22.09 if:

  • You are using one of the following Citrix versions: Citrix Virtual Apps and Desktops 7 2203 Long Term Service Release (LTSR), Citrix Virtual Apps and Desktops 7 1912 LTSR, XenApp and XenDesktop 7.15 LTSR, or XenApp and XenDesktop 7.6 LTSR.
  • You are using Citrix StoreFront.

  Caution: If you are using an earlier version of Citrix or you are using the Citrix Web Interface SDK, do not migrate to the 22.09 connector.

• If your deployment includes Horizon Cloud Service virtual apps, follow these guidelines:

  • If your current installation includes a virtual apps collection for Horizon Cloud Service on Microsoft Azure with Single-Pod Broker or Horizon Cloud Service on IBM Cloud, you can migrate to Omnissa Access 22.09. The 22.09 connector supports this integration.

  • However, if you plan to transition your Horizon Cloud environment to Horizon Cloud Service on Microsoft Azure with Universal Broker, you do not need to migrate your virtual apps collection in Omnissa Access. Omnissa Access integration with a Universal Broker environment does not require virtual apps collections. Nor does it require the Virtual App service component of the Omnissa Access connector. You must delete your existing virtual apps collection in Omnissa Access when you set up the integration with a Universal Broker environment.

    For information about setting up the integration with a Universal Broker environment, see the Horizon Cloud Service documentation.

• If your deployment includes ThinApp packaged applications, you can migrate to Omnissa Access connector 22.09. See Migrating ThinApp Virtual Apps Collections to Omnissa Access Connector 22.09.