Upgrade App Volumes Agent Silently

You can also upgrade the App Volumes agent silently using the Microsoft Windows Installer (MSI).

You perform a silent upgrade using the command line and you need not use the Omnissa App Volumes installer.

Note: During the upgrade, if a failure occurs or the upgrade is canceled, the installer for App Volumes agent rolls back to the previously installed version of the agent. After the rollback, the Windows endpoint on which the agent is installed must be restarted.

Upgrade App Volumes Agent Through Horizon Agent Auto Upgrade

If you are a Horizon administrator, you can use the Horizon Agent Auto Upgrade process for a silent upgrade of App Volumes agent directly from the Horizon console. Using this feature simplifies agent lifecycle management and ensures consistency across virtual desktop infrastructure without manual intervention or custom scripts.

Note: To use the Horizon Agent Auto Upgrade feature, you must have Horizon 8 version 2312 or later, with an appropriate license that includes access to this feature. For information about the feature and licensing requirements and how to use this feature, see the Auto Upgrade Horizon Agent section in the Omnissa Horizon 8 Installation and Upgrade documentation at Omnissa Product Documentation.

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 use the Omnissa Apps Essentials License.

  • You must have the App Volumes Manager IP address (MANAGER_ADDR) and App Volumes Manager port number (MANAGER_PORT) handy. These details are required as part of the upgrade process. Additionally, you must use the PACKAGEMODELOCAL parameter in the command line.

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

• Ensure that you are aware of the parameters that can be used at the time of upgrade. For more information about the parameters, see Install App Volumes Agent Silently.

Procedure

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

2. Open a Windows command prompt on the endpoint.

3. In the command prompt, access the App Volumes Agent.msi file location.

4. Depending on the mode selected, upgrade the agent as follows:

   Important: If you are upgrading from App Volumes 4.0 to a later version (including App Volumes 4 Update 1), run the following in an elevated command prompt with all these parameters:
   msiexec.exe /i “App Volumes Agent.msi” /qn MANAGER_ADDR=<Manager_FQDN/IP> MANAGER_PORT=<port> EnforceSSLCertificateValidation=<0or1>
   

   Option	Description
   Deploy App Volumes agent in Managed mode	Run the following in an elevated command prompt: msiexec.exe /i "App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN/IP> MANAGER_PORT=<port> PACKAGEMODELOCAL=1 EnforceSSLCertificateValidation=<0or1> EnablePIILogging=<0or1> LogLevel=<0or1> Note: The PACKAGEMODELOCAL parameter is required only if you are migrating from the Standalone mode to the Local Copy package access mode. Additionally, you must also provide the MANAGER_ADDR and MANAGER_PORT. It is optional to use EnforceSSLCertificateValidation. When upgrading from versions earlier than App Volumes 4, version 2406, you cannot set the NONPERSISTENT parameter to 0. When upgrading from App Volumes 4, version 2406 to App Volumes 4, version 2410 and later versions, using this parameter is optional because the parameter value set for upgrade is the same value which is set during installing App Volumes 4, version 2406. If you use the /norestart flag in the command, ensure that you restart the virtual machine after the command runs. This restart is necessary for the upgrade to complete. Note: PACKAGEMODELOCAL and NONPERSISTENT are mutually exclusive.
   Deploy App Volumes agent in Standalone mode	Run the following in an elevated command prompt: msiexec.exe /i "App Volumes Agent.msi" /qn DIRECT=1 LICENSEKEY=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx EnablePIILogging=<0or1> LogLevel=<0or1> Note: LICENSEKEY is mandatory.

What To Do Next

• When using the Local Copy package access mode, ensure that you configure the Omnissa Apps Essentials License key in App Volumes Manager. See the Configure License in App Volumes Manager section in the App Volumes Administration Guide, version 2512 and later, at Omnissa Product Documentation.

• If you want 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.