Using the updateoffline.hzn Script for an Offline Upgrade of Omnissa Access

You can use the updateoffline.hzn script to perform an offline upgrade to 23.09 of the existing Omnissa Access virtual appliance. Download the offline upgrade package from the Omnissa Access product download page to use with the script.

The script verifies that the upgrade package matches the product. For example, if you are upgrading the Omnissa Access virtual appliance and you use the connector upgrade package instead of the Omnissa Access upgrade package, the script results in an error.

Prerequisites

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

• Download the Omnissa Access offline upgrade package, identity-manager-23.09.0.0-buildNumber-updaterepo.zip to the Omnissa Access appliance. Go to the Customer Connect page and search for Omnissa Access 23.09. Select the Download option to download Omnissa Access 23.09.

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

• Verify that at least 4 GB of disk space are available on the primary root partition of the virtual appliance after copying identity-manager-23.09.0.0-buildNumber-updaterepo.zip to the appliance.

Procedure

1. Locate the updateoffline.hzn script.

   The script is available at the following path:

   /usr/local/horizon/update/updateoffline.hzn

2. Run the updateoffline.hzn script as the root user.

   /usr/local/horizon/update/updateoffline.hzn [-r] -f upgradeFilePath

   -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

   For example:

   /usr/local/horizon/update/updateoffline.hzn -f /var/tmp/identity-manager-23.09.0.0-buildNumber-updaterepo.zip

3. If the "The product RID matches so continue" prompt appears, press Enter to continue.

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

   reboot

5. 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.