In my previous blog we discussed about Appvolumes and benefits, this blog will explain about the VMware Appvolume Components.
VMware Appvolume Components:
- Appvolume Manager
- Appvolume Agent
- Appstack Volumes
- Writable Volumes
AppVol Manager is a core component that is installed on a windows server. It’s a web console for administration and configuration of App Volumes and assignment of AppStacks and Writable Volumes. Web Console is installed as a part of App Volumes Manager.Also its a Broker for App Volumes Agent for the assignment of applications and writable volumes.
It is installed on computers running supported versions operating systems where users receive AppStack and Writable Volume assignments. The agent runs as a service and utilizes a filter driver to handle application calls, and file system redirects to AppStack and writable volume VMDKs.
It is a read only volume containing single or multiple applications. It can map more than one appstack per user or target and deploy applications to VDI or RDSH.
Benefits of AppStacks include:
- Application are installed only once, thereby saving space.
- You can easily update an application, with no impact to end users.
- AppStacks can be assigned by AD User, group, or computer.
- The AppStack is hot added, so there is no network or storage latency.
A writable volume is a read-write VMDK or VHD volume that is attached to a single user or virtual machine.It is used to capture and retains the changes written in the user sessions. By default, App volume provision one writable volume per user and its read and writable for user.
Benefits of Writable Volume :
- They enable persistence with nonpersistent virtual desktops.
- The volumes are attached before GPOs are applied.
There are three templates are available for Writable Volume:
- User Profile Data Only (Template_profile_only)
- User Installed Applications Only (Template_uia_only)
- Both Profile Data and User Installed Applications (Template_uia_plus_profile)
Here is the details about the Templates,
Template_uia_only – Allows for the use of “User Installed Applications” when mounted. Note that users still the appropriate OS permissions to install applications.
Template_profile_only – Leveraging a filter driver in the AppVolumes agent, user profile settings will be be redirected and saved to the Writable Volume.
Template_uia_plus_profile – The best of both worlds listed above. User installed applications and user profile changes are saved and persisted to the writable volume.
I hope this is informative for you. Thanks for Reading!!!. Be Social and share it in social media, if you feel worth sharing it.