You can understand how Writable Volumes can be used with VMware Dynamic Environment Manager, behavior of Writable Volumes in a non-persistent virtual desktop, how Writable Volumes are used in a shared datastore, and how to exclude specific locations of Writable Volumes from being overwritten.
Writable Volumes with User Environment Management Solutions
You can use Writable Volumes to complement a user environment management solution such as VMware Dynamic Environment Manager. Such solutions can manage data in Writable Volumes at a more granular level and enforce policies based on different conditions or events by providing contextual rules. With Writable Volumes, you can use containers for local user profile delivery across systems.
Writable Volumes with Non-Persistent Virtual Desktops
On a non-persistent virtual desktop environment, all applications that the user installs are removed after the user logs out of the desktop. Writable Volumes store the applications and settings of users and make user-specific data persistent and portable across non-persistent virtual desktops. This way, you can address use cases, such as providing development and test machines for users to install custom applications on non-persistent virtual desktops.
Storage Configuration with Writable Volumes
When designing your environment for Writable Volumes, consider that a Writable Volume requires both read and write I/O. The input output operations per second (IOPS) for a Writable Volume might vary for each user depending on how the users consume their data. IOPS might also vary depending on the type of data that the users are allowed to store on their Writable Volume.
You can manage the number of Writable Volumes that can be configured on a single storage LUN by monitoring how the users access their Writable Volumes.
Writable Volumes and Shared Datastores
You can create, import, and attach Writable Volumes from shared datastores. See Support for Shared Datastores.
Writable Volumes Exclusions
Using the Writable Volumes exclusions feature, you can exclude specific locations of user Writable Volumes, such as file paths or registry keys, from being overwritten. Use this feature only if you are an IT administrator or an advanced App Volumes administrator. The exclusions do not affect AppStacks or system volumes. For more information, see Considerations When Specifying Exclusions in a Policy File (snapvol.cfg) and Format for Specifying Writable Volume Exclusions in a Policy File.