Upgrading Omnissa Access Offline

If your Omnissa Access 22.09.X virtual appliance cannot connect to the Internet for upgrade, you can perform an offline upgrade to 23.09.

Two options are available for offline upgrade. You can set up an upgrade repository on a local Web server and configure the appliance to use the local Web server for upgrade. Or you can download the upgrade package to the Omnissa Access 22.09.X server and use the updateoffline.hzn script to upgrade.

Prerequisites for a Omnissa Access Offline Upgrade

Before you upgrade the 22.09.X virtual appliance to 23.09.X offline, perform these prerequisite tasks.

• Take a snapshot of your virtual appliance to back it up. For information about how to take snapshots. See KB article 2032907, Managing snapshots in vSphere Web Client.

• Microsoft SQL server 2014 updated with the Microsoft SQL patch to support TLS 1.2.

• 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 22.09.X

  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

• Take a snapshot or backup of the external database.

• Verify that Omnissa Access is properly configured.

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

• If you are upgrading using the updateoffline.hzn script and your deployment includes a proxy server, deactivate the proxy server.

  Deactivate the proxy server from the Omnissa Access console.

  1. Log in to the Omnissa Access console and navigate to the Monitor > Resiliency page.
  2. Select the appliance and click VA Configuration.
  3. Click Manage Configuration, log in with the admin user password, and click Proxy Configuration.
  4. Deactivate Proxy.
  5. Click Save. After a successful upgrade, enable the proxy server again.

  Ensure that following directory space requirements are met.

  Directory	Minimum Available Space
  /	4 GB
  Directory where you download the offline upgrade package, identity-manager-23.09.0.0-buildNumber-updaterepo.zip	2 GB

• Make sure all connectors in your deployment are version 22.09.x or an earlier, supported version of the enterprise connector.

  Legacy connectors (version 19.03.0.1 and earlier) are not compatible with Omnissa Access virtual appliance version 23.09. Migrate your legacy connectors to 22.09.x (or an earlier, supported version of the enterprise connector) before upgrading your Omnissa Access virtual appliances to 23.09. After upgrading the virtual appliances to 23.09, upgrade the connectors to 23.09.

See Migrating to Omnissa Access Connector 22.09 or Upgrading to Omnissa Access Connector 22.09 at Omnissa Access documenation pages.