Upgrading Omnissa Access Offline

You cannot perform a fresh install of Omnissa Access 24.07.0.0. Instead, you must do an offline upgrade to this version.

You download the 24.07.0.0 upgrade package to the Omnissa Access 22.09.1.0 or 23.09.0.0 appliance to upgrade a Omnissa Access 22.09.1.0 or 23.09.0.0 appliance to version 24.07.0.0.

Prerequisites for a Omnissa Access Offline Upgrade

Before you upgrade to 24.07.0.0 offline, perform these prerequisite tasks.

• Make sure that you have a backup or a snapshot of your virtual appliance. For information about how to take snapshots. see KB article 2032907, Managing snapshots in vSphere Web Client.

• Take a snapshot or backup of the external database.

• If you revoked the db_owner role on the Microsoft SQL database, you must add it back before performing the upgrade, otherwise the upgrade fails. Add the db_owner role to the same user that was used during installation:

  1. Log in to the Microsoft SQL Server Management Studio as a user with sysadmin privileges.

  2. Connect to the database instance for Omnissa Access.

  3. Enter the following commands.

     If you are using Windows Authentication mode, use the following commands:

  USE <saasdb>;
  ALTER ROLE db_owner ADD MEMBER <domain\username>; GO 
  

  Make sure that you replace <saasdb> with your database name and <domain\username> with the relevant domain and user name.

   If you are using SQL Server Authentication mode, use the following commands:
  

  USE <saasdb>;
  ALTER ROLE db_owner ADD MEMBER <loginusername>; GO 
  

  Make sure that you replace *<saasdb> with your database name and *<loginusername> with the relevant user name.

  For information about revoking the database-level role, see Change Database-Level Roles After Upgrade to Omnissa Access

• Verify that Omnissa Access is properly configured.

• Confirm that a Omnissa Access upgrade exists. Check the Omnissa Customer Connect site for upgrades.

• Ensure that following directory space requirements are met.

  Directory	Minimum Available Space
  / partition	5 GB
  /opt//horizon partition	1 GB
  Directory where you download the offline upgrade packages, update-with-zip.hzn and ws1access-24.07.0.0-buildnumber-updaterepo.zip	5 GB

  • If you are upgrading from 22.09.1.0 and the VA-Configuration > Mobile SSO > Android SSO cert proxy settings are enabled in your environment, during the offline upgrade, you are asked to update the following CertProxy settings.

    • Number of load balancers. Enter the number of load balancers that are between the CertProxy service and the Omnissa Access instance or enter 0 if a load balancer is not used.

    • Client IP load balancer header name (Remote IP source). This is the source used to obtain the CertProxy instance IP from the HTTP request. The value can be X-forwarded-For header orX-Real-Ip header. If the number of load balancers is 0, Remote IP source is automatically set to Request remote address.

    • The allowlist of CertProxy instance IP addresses to accept authentication requests from. The current IP addresses configuration is pre-populated. You can make changes or click Enter to keep the current configuration. To change the allowlist, enter IP addresses of CertProxy instances separated by a semicolon, either in CIDR format, subnet format delimited by a space, or as a single IP.

    Important: If the number of load balancers is 0 and the CertProxy destination is set to localhost, you must add the localhost IP to the list of IP addresses in the allowlist. This is usually 127.0.0.1.

  • Before you upgrade, all connectors in your deployment must be at version 22.09.1.0 or an later supported version of the enterprise connector.

    Note: Legacy connectors (version 19.03.0.1 and earlier) are not compatible with Omnissa Access virtual appliance version 24.07.0.0. Before you upgrade, you must migrate your legacy connectors to a 23.09.0.0 (or an earlier compatible version of the enterprise connector) before upgrading your Omnissa Access virtual appliances to 24.07.0.0. After upgrading the virtual appliances to 24.07.0.0, upgrade the connectors to 24.07.0.0.

    See Migrating to Omnissa Access Connector 22.09 or Upgrading to Omnissa Access Connector 22.09.