Install App Volumes Agent Silently

You can install Omnissa App Volumes agent silently using the Microsoft Windows Installer (MSI). To package an App Volumes application or deliver the application to a Windows endpoint, the App Volumes agent must be installed on the endpoint (packaging computer and target desktops).

You can install the App Volumes agent in a managed mode where the agent connects to App Volumes Manager or install the agent as a standalone component. When installed in the managed mode, App Volumes Manager centrally manages the application lifecycle. Additionally, you can also determine whether to deliver an application to the local cache of a Windows endpoint or place the application on shared storage from where the Windows endpoint accesses the application. In a standalone mode, device management tools manage the application lifecycle.

Install 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 install 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.

Install App Volumes in a non-persistent virtual desktop environment

Non-persistent machines are those that refresh regularly, and user data and settings are not persisted on the operating system disk. These machines are managed centrally by re-imaging the operating system with updates. In the non-persistent virtual desktop environment, any application installed by the end user is removed after the user logs out of the desktop or when the virtual machine is shut down.

To use App Volumes in such an environment, you can select the Non-persistent or multi-session machines option when installing the App Volumes agent.

In a non-persistent virtual desktop environment, to make user-specific data persistent and portable, you can use a Writable Volume. For more information about Writable Volumes, see the Omnissa App Volumes 4 Administration Guide at Omnissa Product Documentation.

Important: Writable Volumes can be used only on a non-persistent virtual desktop.

Prerequisites

Install App Volumes Manager.

Ensure that you have the host IP address and port number handy. This information is required at the time of installing the agent.
Verify that your environment meets System Requirements.
Verify that your account has local administrator privileges on the target computer.
Do not install the agent on the same machine where the App Volumes Manager is installed.
You can install the latest Windows Update and keep the Windows Update activated.

Note: For a non-persistent virtual desktop, install the latest Windows Update on the target computer and subsequently deactivate the Windows 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.
To install App Volumes agent on a non-persistent virtual desktop environment, a separate base image must be used.
If you intend to use this Windows endpoint as a packaging computer, create a clean snapshot or take a backup of this machine. Revert to this snapshot or backup before packaging new application packages.
Ensure that you are aware of the deployment mode options (Managed mode and Standalone mode) in App Volumes. For more information about these options, see Choose Your App Volumes Deployment Model.
- During installation, you can choose how a package can be accessed by a Windows endpoint. For more information about understanding package access modes, see Application Delivery Modes with App Volumes Manager.
- If you choose to install App Volumes agent in the Local Copy package access mode, ensure that you use the Omnissa Apps Essentials License.
If you intend to install App Volumes agent in the Standalone mode, you are required to choose the license configuration. To use a production license, keep your license key handy. For any license related warnings or errors, see the Windows event log. To understand the licensing requirements, see Obtain a License for the Standalone App Volumes Agent Configuration.
Ensure that you are aware of the parameters used during silent installation.

Parameters Used During Silent Installation

A few of these parameters are common to both deployment modes (managed and standalone) whereas a few of them are specific to each mode.

Parameters for Managed mode

MANAGER_ADDR and MANAGER_PORT

Use these mandatory parameters to specify the App Volumes Manager IP address or FQDN value and port number for communication between App Volumes Manager and App Volumes agent respectively. In managed mode, App Volumes agent connects with App Volumes Manager hence these parameters are required.
PACKAGEMODELOCAL

This parameter allows you to install App Volumes agent in the Local Copy package access mode. When the Windows endpoint is in this mode, MSI-wrapped VHD packages are downloaded on the endpoint, locally cached, virtualized, and the application is delivered to the end user. The user can access applications even when the endpoint goes offline. The Windows endpoint connects with App Volumes Manager, which is used for application management.

By default, the value of this parameter is 0.

1 - Local copy package access mode
0 or not used - App Volumes agent is installed in the Shared Storage package access mode.

To install App Volumes agent in the local copy package access mode, this parameter is mandatory and must be set to 1.
NONPERSISTENT

This optional parameter allows you to use Omnissa App Volumes in a non-persistent virtual desktop environment. By default, the value of this parameter is 1.

1 - App Volumes works in a non-persistent virtual desktop environment.
0 - To use App Volumes in a virtual desktop environment which retains user data and settings on the operating system disk.

Note: PACKAGEMODELOCAL and NONPERSISTENT are mutually exclusive.

Parameters for Standalone mode

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

By default, the value of this parameter is 0.

1 - App Volumes agent operates independently (without App Volumes Manager).
0 or not used - App Volumes agent connects with App Volumes Manager.
LICENSEKEY

This parameter is required when you want 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. If you intend to use trial mode, no license key is necessary; hence, this parameter need not be specified in the command line. A production license can be added at any time after installation using the svservice command line.

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

Parameters common to both modes

EnforceSSLCertificateValidation

This optional 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.
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 install. For more information about these parameters, see Obfuscate PII Data in App Volumes.

Procedure

Download the Omnissa App Volumes ISO.
1. Go to the Customer Connect page.
2. Click Downloads.
3. In the Products A-Z listing, search for App Volumes and click Download Product.
4. In the Download App Volumes page, navigate to the desired edition, and click GO TO DOWNLOADS.
5. In the Download Product page, download the files.
Mount the ISO and navigate to the Installaion > Agent folder.

Install App Volumes Agent.msi using an elevated command prompt.

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 "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN or Manager_IP> MANAGER_PORT=<port> EnforceSSLCertificateValidation=<0or1>

Deploy in Managed mode (connects with App Volumes Manager)

Note: NONPERSISTENT parameter is available only from App Volumes 2406 and later.

Package Access Mode Command Used

Shared Storage

Package Access Mode	Command Used
Shared Storage	Run the following command in an elevated prompt: `msiexec.exe /i "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN or Manager_IP> MANAGER_PORT=<port> EnforceSSLCertificateValidation=<0 or 1> NONPERSISTENT=<0 or 1> EnablePIILogging=<0 or 1> LogLevel=<0 or 1>` Examples: `msiexec.exe /i "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=192.86.10.10 MANAGER_PORT=443 LogLevel=1 EnablePIILogging=0` `msiexec.exe /i “path_of_App Volumes Agent.msi” /qn MANAGER_ADDR=avm.company.com MANAGER_PORT=443 NONPERSISTENT=0 LogLevel=0`
Local Copy	Run the following command in an elevated prompt: `msiexec.exe /i "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN or Manager_IP> MANAGER_PORT=<port> PACKAGEMODELOCAL=1 EnforceSSLCertificateValidation=<0or1> EnablePIILogging=<0 or 1> LogLevel=<0 or 1>` Examples: `msiexec.exe /i "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=192.86.10.10 MANAGER_PORT=443 LogLevel=1 EnablePIILogging=0 PACKAGEMODELOCAL=1` `msiexec.exe /i “path_of_App Volumes Agent.msi” /qn MANAGER_ADDR=avm.company.com MANAGER_PORT=443 LogLevel=0 PACKAGEMODELOCAL=1`

Run the following command in an elevated prompt:

msiexec.exe /i "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN or Manager_IP> MANAGER_PORT=<port> EnforceSSLCertificateValidation=<0 or 1> NONPERSISTENT=<0 or 1> EnablePIILogging=<0 or 1> LogLevel=<0 or 1>

Examples:

msiexec.exe /i "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=192.86.10.10 MANAGER_PORT=443 LogLevel=1 EnablePIILogging=0

msiexec.exe /i “path_of_App Volumes Agent.msi” /qn MANAGER_ADDR=avm.company.com MANAGER_PORT=443 NONPERSISTENT=0 LogLevel=0

Local Copy

Run the following command in an elevated prompt:

msiexec.exe /i "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=<Manager_FQDN or Manager_IP> MANAGER_PORT=<port> PACKAGEMODELOCAL=1 EnforceSSLCertificateValidation=<0or1> EnablePIILogging=<0 or 1> LogLevel=<0 or 1>

Examples:

msiexec.exe /i "path_of_App Volumes Agent.msi" /qn MANAGER_ADDR=192.86.10.10 MANAGER_PORT=443 LogLevel=1 EnablePIILogging=0 PACKAGEMODELOCAL=1

msiexec.exe /i “path_of_App Volumes Agent.msi” /qn MANAGER_ADDR=avm.company.com MANAGER_PORT=443 LogLevel=0 PACKAGEMODELOCAL=1

Deploy in Standalone mode (Device Management Tools are used)

To install App Volumes agent directly on a Windows endpoint, run the following in an elevated command prompt:

msiexec.exe /i “path_of_App Volumes Agent.msi” /qn DIRECT=1 LICENSEKEY=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx EnablePIILogging=<0or1> LogLevel=<0or1>

Note:

In the standalone mode, App Volumes Manager is not used. Hence, the following parameters are not required in the command line: MANAGER_ADDR, MANAGER_PORT, and EnforceSSLCertificateValidation.
For trial mode, LICENSEKEY is an optional parameter.

What to do next

App Volumes Deployment Model Procedure

Managed mode

App Volumes Deployment Model	Procedure
Managed mode	Configure SSL certificates for the agent. You can also deactivate SSL communication and certificate validation between App Volumes Manager and agent. For more information, see the Omnissa App Volumes Administration Guide on Omnissa Product Documentation. If you have selected the Local Copy package access mode during installation, ensure the following: Configure the Omnissa Apps Essentials License key. For more information about the configuration, see the Configure License in App Volumes Manager section in the App Volumes Administration Guide, version 2512 and later, at Omnissa Product Documentation. Turn on the Generate MSI when creating VHD package setting in App Volumes Manager. For more information about this setting, see App Volumes Manager Configuration Settings Page section in the Omnissa App Volumes Administration Guide.
Standalone mode	On a clean virtual machine, Install App Volumes Application Capture Command-Line Program. Capture an App Volumes application package into the `.msi` format using the App Volumes Application Capture Command-Line Program on a Windows virtual machine. For more information about using the Capture Command-Line program, see Using the App Volumes Application Capture Command-Line Program chapter in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation. If you have selected trial mode at the time of install, at a later time, you can upgrade to a production license by adding a license key using the `svservice` command with administrator privileges. `svservice.exe setlicensekey license_key` where `license_key` is 35 characters long in this format `xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx`. Note: The production license gets updated only on the Windows endpoint where the `svservice` command is run. Hence, this update must be performed on every Windows endpoint which has App Volumes agent installed. When upgrading to later versions of App Volumes, using a production license is mandatory in the following scenarios: Trial mode has expired in the source version of the upgrade. Production license has expired in the source version of the upgrade and the target version of the upgrade is not an App Volumes patch release.

Configure SSL certificates for the agent. You can also deactivate SSL communication and certificate validation between App Volumes Manager and agent.
For more information, see the Omnissa App Volumes Administration Guide on Omnissa Product Documentation.

If you have selected the Local Copy package access mode during installation, ensure the following:
- Configure the Omnissa Apps Essentials License key.
  For more information about the configuration, see the Configure License in App Volumes Manager section in the App Volumes Administration Guide, version 2512 and later, at Omnissa Product Documentation.
- Turn on the Generate MSI when creating VHD package setting in App Volumes Manager.
  For more information about this setting, see App Volumes Manager Configuration Settings Page section in the Omnissa App Volumes Administration Guide.

Standalone mode

On a clean virtual machine, Install App Volumes Application Capture Command-Line Program.

Capture an App Volumes application package into the .msi format using the App Volumes Application Capture Command-Line Program on a Windows virtual machine.

For more information about using the Capture Command-Line program, see Using the App Volumes Application Capture Command-Line Program chapter in the Omnissa App Volumes Administration Guide at Omnissa Product Documentation.

If you have selected trial mode at the time of install, at a later time, you can upgrade to a production license by adding a license key using the svservice command with administrator privileges.

svservice.exe setlicensekey license_key

where license_key is 35 characters long in this format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx.

Note: The production license gets updated only on the Windows endpoint where the svservice command is run. Hence, this update must be performed on every Windows endpoint which has App Volumes agent installed.

When upgrading to later versions of App Volumes, using a production license is mandatory in the following scenarios:

Trial mode has expired in the source version of the upgrade.
Production license has expired in the source version of the upgrade and the target version of the upgrade is not an App Volumes patch release.

Was this page helpful?