Offline Upgrade of Omnissa Access to 24.07

You use the update-with-zip.hzn script to perform an offline upgrade of the existing Omnissa Access virtual appliance to the 24.07.0.0 version.

Important: You cannot perform a fresh install of Omnissa Access 24.07.0.0. Instead, you perform an offline upgrade to Omnissa Access 24.07.0.0.

Prerequisites

• Perform the general offline-upgrade prerequisites. See Prerequisites for a Omnissa Access Offline Upgrade.

• Install the hotfix documented on Omnissa KB: https://kb.omnissa.com/s/article/6000354.

• From a local computer, go to the Omnissa Customer Connect page and select the Download option to search for and download the two Omnissa Access 24.07.0.0 upgrade files update-with-zip.hzn and ws1access-24.07.0.0-buildnumber-updaterepo.zip.

Procedure

1. Log in to the Omnissa Access appliance as the root user.

2. Navigate to directory with enough space to download the files.

   The recommended location for saving the files is /var/tmp.

3. Download the update-with-zip.hzn file.

4. Download the ws1access-24.07.0.0-buildnumber-updaterepo.zip file.

   Verify that at least 5 GB of disk space are available on the primary root partition of the virtual appliance after copying the 24.07.0.0 upgrade files to the appliance.

5. Type chmod +x update-with-zip.hzn to make the update-with-zip.hzn file executable.

6. Run the /var/tmp/update-with-zip.hzn -f /var/tmp/ws1access-24.07.0.0-buildnumber-updaterepo.zip to upgrade to 24.07.0.0

   -f upgradeFilePath	Upgrade the appliance using upgradeFilePath. upgradeFilePath must be an absolute path. When you upgrade nodes in a cluster, in the first node that you upgrade, enter y to reindex the indices. When you upgrade the other nodes in the cluster, enter n. For a single node upgrade, the setting is y by default.	Required
   -r	Reboot after upgrade.	Optional
   -h	Displays the script usage.	Optional

7. If you are upgrading from Omnissa Access 23.09.0.0, continue with step 8.

   When upgrading from Omnissa Access 22.09.1.0, if you enabled the VA-Configuration > Mobile SSO > Android SSO cert proxy settings in your environment, during the upgrade the following settings must be updated.

   1. Please provide number of load balancers between CertProxy and Access instance:

   Note: If you do not use a load balancer, enter 0 as the value. When you enter 0, the next CertProxy question does not display.

   2. Please provide client IP load balancer header name (x-forwarded-for/x-real-ip):

   3. Please provide list of CertProxy instance IP addresses, 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.

8. If you did not use the -r option with the script, restart the virtual appliance after the upgrade is complete.

   reboot

   If the appliance is in a cluster, upgrade the other nodes one at a time.

9. After you upgrade all the nodes in your Omnissa Access deployment, use the diagnostics dashboard to monitor system information health.

   1. Log in to the Omnissa Access console.

   2. Select Monitor > Resiliency.

   3. If your deployment consists of more than one Omnissa Access appliance, select the appliance you want to monitor.

   4. Check the status of the various services.