Using Omnissa App Volumes on a persistent virtual desktop allows an end user to install and uninstall applications in the presence of App Volumes application packages. These changes continue to exist even if there are no packages assigned to the user or App Volumes is removed from the virtual desktop.
In a persistent virtual desktop environment, end users can install, modify, update and uninstall applications in the base volume but not those which are delivered as application packages.
App Volumes can be configured on a persistent virtual desktop by selecting the appropriate machine type option. This option is available when installing the App Volumes agent.
Note: By default, App Volumes is set up to work in a non-persistent virtual machine.
Machine Type Options
Persistent machines
Machines that retain user data and installed applications on the operating system disk across sessions. Persistent virtual desktops are often managed by a user endpoint management system or the end user themselves.
Non-persistent or multi-session machines
Machines that refresh regularly and user data and settings are not persisted on the operating system disk.
Non-persistent 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. In such an 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.
Considerations When Using App Volumes on a Persistent Virtual Desktop
You must be aware of the following best practices and limitations when using App Volumes on a persistent virtual desktop:
- Separate base images must be used when installing App Volumes agent for persistent and non-persistent pool deployments.
- The virtual machine on which App Volumes agent is installed with persistent desktop enabled cannot be used as a packaging virtual machine.
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. - Writable Volumes must not be used on a persistent virtual desktop.
If a user has a Writable Volume assignment, then such a user must not be assigned to a persistent virtual desktop. - You can install the latest Windows Update and keep the Update activated.
For information about installing App Volumes agent, see Install App Volumes Agent. For more information about upgrading the App Volumes agent, see Upgrade App Volumes Agent.
Install and Upgrade Scenarios for Using App Volumes in a Persistent Pool Deployment in Horizon 8
The following table explains how to install and upgrade App Volumes agent in an existing non-persistent or persistent pool deployment to enable using App Volumes in a persistent pool deployment.
| Existing pool deployment | Is App Volumes installed? | Use App Volumes in a persistent pool deployment |
|---|---|---|
| Non-Persistent | No | To install App Volumes agent on the base (golden) image, follow the Patching an Instant-Clone Desktop Pool procedure. For information about this procedure, see the Patching an Instant-Clone Desktop Pool section in the Desktops and Applications in Horizon 8 documentation at Omnissa Product Documentation. |
| Persistent | No Important: If a system Writable Volume is present, then you cannot install App Volumes agent in a persistent pool deployment. Location of the system Writable Volume is C:\{00000000-0000-0000-0000-000000000000}. | To install App Volumes agent in a persistent pool deployment, follow the Customize Machines by Placing Them in Maintenance Mode After Pool Creation procedure. Note: At step 6 in the procedure, you can use a solution such as SCCM to automate the installation of App Volumes agent on all VMs in the pool. For information about this procedure, see the Customize Machines by Placing Them in Maintenance Mode After Pool Creation section in the Desktops and Applications in Horizon 8 documentation at Omnissa Product Documentation. |
| Persistent | Yes |
|
Was this page helpful?