In this blog , I will explain you about Writable volume – About Writable volume , Create and assign Writable Vol.
A writable volume is a read-write VMDK or VHD volume that is attached to a single user or virtual machine.
• The user can store data and install applications on the volume, which is retained.
• Users can have more than one writable volumes assigned to them, however, a user can use only one writable volume at any given time.
The benefits of writable volumes include:
• They enable persistence with non-persistent 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)
Let me explain 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.
Creating Writable Volumes :
- Login to Appvolume Manager.
- Select the Volumes menu and click on the Writables tab.
- Click on the Create Writable button.
- Enter the user name or a group that you want to create Writable volume and Click on Search.
- Select a Datastore and the default destination path to hold the Writable Volume.
- Finally , Pick a Writable volume template from the drop down under source Template.
- Click on “Create”
- During the creation process , go to the vCenter connection and you will see a tasks to create the new VMDK’s finished. Browsing the Datastore you can see the four unique VMDK’s created per use (notice the VMDK file names). One other thing to point out, each of the VMDK’s are Thin-Provisioned and configured with a maximum size of 10GB per VMDK by default.But you can customize the template your own.
- Go back in the AppVolumes Manager dashboard and you can see the new volumes that were created.
Note: If you select a group, then individual writable volumes are be created for each member of that group. This can be delayed until the first time they login by using the delay check box. Group membership is discovered with recursion, meaning that users/computers in subgroups will also receive volumes. However, when creating writable for Organization Units, groups are not recursed.
I hope this is informative for you. Thanks for Reading!!!. Be Social and share it in social media, if you feel worth sharing it.
VMware App Volumes – How to Create a New App Stack?