Install App Volumes Agent Silently

You can install Omnissa App Volumes agent silently using the Microsoft Windows Installer (MSI).

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

Parameters Used in Silent Installation

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

• 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 or persistent virtual desktop environment.

  The values of this parameter are as follows:

  • 0 indicates that App Volumes agent is installed to work in a persistent virtual machine
  • 1 indicates that App Volumes agent is installed to work in a non-persistent virtual machine.

  By default, the value of this parameter is 1.

  For more information about using App Volumes on a persistent virtual desktop, see Using App Volumes on a Persistent Virtual Desktop.

• DIRECT

  This parameter allows you to install Omnissa App Volumes agent directly on Windows endpoints. You can use this parameter when you want to deliver App Volumes applications to devices such as physical desktops, laptops, and cloud desktops (Windows 365 Cloud PC).

  The values of this parameter are as follows:

  • 1 indicates that App Volumes agent is configured without App Volumes Manager
  • 0 indicates that both App Volumes Manager and App Volumes agent are configured.

  By default, the value of this paramter is 0.

  Note:

  • App Volumes Manager is not required in this scenario. Hence, the following parameters are not required in the command line: MANAGER_ADDR, MANAGER_PORT, and EnforceSSLCertificateValidation.

  • DIRECT and NONPERSISTENT parameters cannot be used together.

  For more information about this delivery scenario, see Deliver App Volumes Applications Using Device Management Tools.

Prerequisites

• Verify that your environment meets System Requirements.

• Verify that your account has local administrator privileges on the target computer.

• Ensure that you are aware of the parameters used during silent installation.

If you want to deliver App Volumes applications to a virtual desktop infrastructure, then ensure that you make note of these prerequisites as well including those mentioned earlier:

• Do not install the agent on the same machine where the App Volumes Manager is installed.

• Ensure that you have installed the App Volumes Manager and you have the host IP address and port number.

• Windows Update

  • For a non-persistent virtual desktop, install the latest Windows Update on the target computer and subsequently deactivate the Update.

    When you have application packages or Writable Volumes and the Windows Update is not deactivated on the target computer, the system volume or the Writable Volumes might get corrupted.

  • For a persistent virtual desktop, you can install the latest Windows Update and keep the Update activated.

• If you intend to use this virtual machine as a packaging computer, create a clean snapshot or take a backup of this machine. Revert to this snapshot or the backup before packaging new application packages.

• Using Omnissa App Volumes on a persistent virtual desktop:

  • Separate base images must be used when upgrading the App Volumes agent for persistent and non-persistent pool deployments.

  • Ensure that you are aware of the rest of the considerations for Using App Volumes on a Persistent Virtual Desktop.

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 install the agent, use the following command:

   Option	Description
   App Volumes 4 Update 1 and later	msiexec.exe /i "App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN/IP> MANAGER_PORT=<port> EnforceSSLCertificateValidation=<0or1> NONPERSISTENT=<0or1> DIRECT=<0or1> Note: EnforceSSLCertificateValidation is an optional parameter. NONPERSISTENT parameter is available only from App Volumes 2406 and later. Examples: Consider an App Volumes Manager with IP address 192.86.10.10 and port 443, then use the following command: msiexec.exe /i "App Volumes Agent.msi" /qn MANAGER_ADDR=192.86.10.10 MANAGER_PORT=443 Consider an App Volumes Manager with FQDN avm.company.com and port 443, then use the following command: msiexec.exe /i "App Volumes Agent.msi" /qn MANAGER_ADDR=avm.company.com MANAGER_PORT=443 To install App Volumes agent directly on the Windows endpoints without App Volumes Manager, use the following command: msiexec.exe /i "App Volumes Agent.msi" /qn DIRECT=1
   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.