Upgrade App Volumes Agent

To upgrade your App Volumes agent, download and run the latest version of the Omnissa App Volumes installer.

You can also upgrade the agent silently. See Upgrade App Volumes Agent Silently.

Note: During the upgrade, if a failure occurs or the upgrade is cancelled, the installer for App Volumes agent rolls back to the previously installed version of the agent. After the rollback, the agent virtual machine must be restarted.

Prerequisites

• Upgrade App Volumes Manager

  Note: Ensure that the App Volumes Manager version used is the same version or a later version than the App Volumes agent.

• If you use an unsupported version of App Volumes, ensure that you are aware of this upgrade requirement.

• At the time of upgrade, you can migrate from an existing Standalone mode to the Local Copy package access mode (Managed mode). This is the only change in mode allowed during upgrade. Ensure that you are aware of the deployment options (Managed mode and Standalone mode) in App Volumes. For more information about these options, see Choose Your App Volumes Deployment Model.

  For a successful migration, ensure the following:

  • You must have the App Volumes Manager IP address and App Volumes Manager port number handy. These details are required as part of the upgrade process.

  • If you have delivered applications to entities using device management tools in the Standalone mode, then after migration you must create and assign the applications to these entities in App Volumes Manager.

• To ensure that there is no service degradation during the uninstall and subsequent upgrade process, schedule a maintenance window.

• When upgrading to a non-persistent virtual desktop, note the following:

  • A separate base image must be used
  • All application packages and Writable Volumes must be unassigned from the target computer where you plan to upgrade the agent

  Note: To assign a Writable Volume to a user, non-persistent virtual desktop must be used.

  For more information about using App Volumes in a non-persistent virtual desktop environment, see the Install App Volumes in a non-persistent virtual desktop environment section in Install App Volumes Agent.

• If you are upgrading App Volumes agent in the Standalone mode, you must add an App Volumes production license key to the msiexe.exe command line for the upgrade to be successful.

  For information about the licensing requirements, see Obtain a License for the Standalone App Volumes Agent Configuration.

Procedure

1. On a Windows endpoint, download the latest App Volumes installer from the All Downloads page.

2. Log in as administrator on the endpoint.

3. Locate the App Volumes installer you have downloaded and run setup.msi using an elevated command prompt.

   Optional: To obfuscate PII data or control logging entries in App Volumes agent log files, you can use svservice parameters. These parameters can be provided only as commandline options at the time of upgrade. You can upgrade App Volumes agent using the msiexec command as follows:

   For example:

   msiexec /i path_of_App Volumes agent.msi EnablePIILogging=0 LogLevel=1

   For more information about these parameters, see Obfuscate PII Data in App Volumes.

4. Select the App Volumes agent component in the Installer window and click Install.

5. To begin the installation, click Next.

   The installer backs up the configuration files and services.

6. When you see the confirmation message, click Finish.

What To Do Next

If you have opted to migrate from the Standalone mode to the Local Copy package access mode, then ensure that you do the following:

• Configure App Volumes Manager.
  For more information about configuration, see Omnissa App Volumes Administration Guide.

• Turn on the Generate MSI when creating VHD package setting in App Volumes Manager.
  For more information, see the App Volumes Manager Configuration Settings Page section in Omnissa App Volumes Administration Guide.

• If you already have existing application packages, you can import the files (.vhd and .msi) to App Volumes Manager. For more information, see the Import an Application to App Volumes and Understanding the Behavior of Imported Application Packages sections in the Omnissa App Volumes Administration Guide.

• Assign applications to entities in App Volumes Manager.
  For more information, see Assign an App Volumes Application to an Entity section in the Omnissa App Volumes Administration Guide.

For Omnissa App Volumes documentation, see Omnissa Product Documentation.