When delivering App Volumes applications to a virtual desktop infrastructure, App Volumes agent must be installed on the packaging computer and target desktops. App Volumes agent can be directly installed on Windows endpoints using device management tools. This installation allows you to deliver applications to Windows endpoints.
When using App Volumes agent in the virtual desktop environment, for improved security, deactivate weak ciphers in SSL and TLS to ensure that Windows-based machines running the agent do not use weak ciphers when they communicate using SSL/TLS protocol. See Disable Weak Ciphers in SSL and TLS in the Horizon 7 documentation.
Important: Do not install the agent on the same machine where the App Volumes Manager is installed.
You can also install the agent silently using the Microsoft Windows Installer (MSI). See Install App Volumes Agent Silently for more information.
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
-
Verify that your environment meets System Requirements.
-
Verify that your account has local administrator privileges on the target computer.
Virtual Desktop Environment
If you want to deliver App Volumes applications to a virtual desktop infrastructure, then ensure that you make note of these prerequisites including the ones mentioned earlier:
-
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.
Windows Endpoints
-
Ensure that you are aware of the information present in Deliver App Volumes Applications Using Device Management Tools.
-
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.
Procedure
-
Go to the Customer Connect page.
- Click Downloads.
- In the Products A-Z listing, search for App Volumes and click Download Product.
- In the Download App Volumes page, navigate to the desired edition, and click GO TO DOWNLOADS.
- In the Download Product page, download the files.
-
Run the App Volumes installer.
The same installer is used to install App Volumes Manager and the agent.
-
Read and accept the End User License Agreement and click Next.
-
Select Install App Volumes Agent and click Next.
-
Select the deployment type for App Volumes agent:
Options Procedure Virtual desktop environment - Select Connect to App Volumes Manager
- Enter the IP address and port number.
Note: The default port number for App Volumes Manager is 443. Enter 80 for the port number if you have configured App Volumes Manager to listen on an HTTP port. - (Optional) If you do not want the agent to validate the App Volumes Manager certificate, check the Disable Certificate Validation with App Volumes Manager box.
Certificate validation is enabled by default. - If you want to use App Volumes in a virtual desktop environment that retains user data and settings on the operating system disk, clear the Non-persistent or multi-session machines checkbox.
- Click Install.
Directly to a Windows endpoint - Select Standalone Agent Configuration.
- Select the desired option for the license configuration.
- Review the Operational Data Collection information.
Note: Omnissa may collect operational data. This means that Omnissa may monitor and collect configuration, performance, usage, and consumption data relating to customers and their users’ use of the software to facilitate the delivery and operation of the products and services (collectively, referred to operational data) as described in the Omnissa Privacy Notice. You can deactivate the collection of operational data by contacting Omnissa support. - Follow the on-screen instructions.
-
To exit the wizard after the installation is complete, click Finish.
-
To complete the agent installation, restart your packaging virtual machine.
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 35 characters long in this format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxxNote: 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?