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 agent virtual machine must be restarted.

• You cannot upgrade from an existing agent installed in a virtual desktop infrastructure environment to the App Volumes agent which you intend to directly install in the Windows endpoints. For information about why you might want to directly install the agent on the Windows endpoints, see Deliver App Volumes Applications Using Device Management Tools.

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.

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

• Upgrade App Volumes Manager

• When upgrading to a non-persistent virtual desktop, all application packages and Writable Volumes must be unassigned from the target computer where you plan to upgrade the agent.

• If you are upgrading from an earlier version of App Volumes agent which is directly installed on Windows endpoints, you must add an App Volumes production license key to the msiexec.exe command line for the upgrade to be successful.

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

Parameters for silent upgrade

Depending on your requirement, you can use some of the parameters during silent installation:

• LICENSEKEY

  This parameter is required to use a production license for App Volumes. The value of this parameter is a 35 character long license key in this format: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx. This parameter must be added to the msiexec.exe command line.

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

• EnforceSSLCertificateValidation

  This parameter allows App Volumes agent to validate the App Volumes Manager certificate.

  The values of this parameter are as follows:

  • 0 indicates that certificate validation is deactivated
  • 1 indicates that certificate validation is activated.

  By default, the value of this parameter is 1.

• NONPERSISTENT

  This parameter allows you to use Omnissa App Volumes in a non-persistent virtual desktop environment.

  By default, the value of this parameter is 1. As a result, App Volumes works in a non-persistent virtual desktop environment. To use App Volumes in a virtual desktop environment which retains user data and settings on the operating system disk, this parameter value must be set to 0.

• EnablePIILogging and LogLevel

  These optional parameters allow you to obfuscate PII data in App Volumes agent logs and control logging entries in log files and the console. The parameters can be provided as commandline options at the time of upgrade. For more information about these parameters, see Obfuscate PII Data in App Volumes.

Procedure

1. Open a Windows command prompt on your machine.

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

3. To upgrade the agent, use the following command in an elevated command prompt:

   Option	Description
   App Volumes 4 Update 1	Virtual Desktop Environment To upgrade App Volumes agent, use the following command: msiexec.exe /i "App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN/IP> MANAGER_PORT=<port> EnforceSSLCertificateValidation=<0or1> EnablePIILogging=<0or1> LogLevel=<0or1> Note: The following parameters are optional: MANAGER_ADDR, MANAGER_PORT, and EnforceSSLCertificateValidation. When upgrading from versions earlier than App Volumes 4, version 2406, you cannot set the NONPERSISTENT parameter to 0. For information about this parameter, see [Install App Volumes Agent Silently](InstallAppVolumesAgentSilently.md). 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. Windows Endpoints To upgrade App Volumes agent directly on the Windows Endpoints, use the following command: 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.
   App Volumes 4	msiexec.exe /i "App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN/IP> MANAGER_PORT=<port> EnforceSSLCertificateValidation=<0or1> Note: All parameters are mandatory.