You can install Omnissa App Volumes agent silently using the Microsoft Windows Installer (MSI).
Prerequisites
-
Verify that your environment meets System Requirements.
-
Verify that your account has local administrator privileges on the target computer.
-
To understand the licensing requirements, see Obtain a License for the Standalone App Volumes Agent Configuration.
- At the time of install, 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.
-
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.
-
You can install the latest Windows Update and keep the Update activated.
Note: 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.
-
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 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. -
To assign a Writable Volume to a user, only a non-persistent virtual desktop must be used.
Parameters Used in Silent Installation
Depending on your requirement, you can use some of these parameters during silent installation:
-
LICENSEKEYThis 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 themsiexec.execommand 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 any time after installation using thesvservicecommand line.For information about the licensing requirements, see Obtain a License for the Standalone App Volumes Agent Configuration.
-
EnforceSSLCertificateValidationThis parameter allows App Volumes agent to validate the App Volumes Manager certificate.
The values of this parameter are as follows:
0indicates that certificate validation is deactivated1indicates that certificate validation is activated.
By default, the value of this parameter is
1. -
NONPERSISTENTThis 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 to0. -
DIRECTThis 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:
1indicates that App Volumes agent is configured without App Volumes Manager0indicates 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, andEnforceSSLCertificateValidation. -
DIRECTandNONPERSISTENTparameters cannot be used together.
For more information about this delivery scenario, see Deliver App Volumes Applications Using Device Management Tools.
Procedure
-
Open a Windows command prompt on your machine.
-
In the command prompt, access the
App Volumes Agent.msifile location. -
To install the agent, use the following command:
Option Description App Volumes 4 Update 1 and later Virtual Desktop Environment To install 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> NONPERSISTENT=<0or1>
Note:EnforceSSLCertificateValidationis an optional parameter.NONPERSISTENTparameter is available only from App Volumes 2406 and later.
Examples:- Consider an App Volumes Manager with IP address
192.86.10.10and port443, 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.comand port443, then use the following command:msiexec.exe /i "App Volumes Agent.msi" /qn MANAGER_ADDR=avm.company.com MANAGER_PORT=443
Windows EndpointsTo install App Volumes agent directly on a Windows endpoint, use the following command:
msiexec.exe /i "App Volumes Agent.msi" /qn DIRECT=1 LICENSEKEY=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
For trial mode,LICENSEKEYis an optional parameter.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.
What to do next
| Options | Procedure |
|---|---|
| Deliver the applications to a virtual desktop infrastructure environment | 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. |
| Deliver the applications directly to a Windows endpoint |
svservice command with administrator privileges. svservice.exe setlicensekey license_keywhere license_key is a 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 :
|
Was this page helpful?