Forum Discussion
WVD grey area
- 1)it seem like you are asking can a profile be shared between two hostpools? yes it can but is not supported. If VM from both hostpool access the same profile there is a race condition only one VM gets read/write the other one gets read.
2)30 GB is the recommended size not the max size,
3)corrupted VHDs cannot be recovered. there are 3rd party tools that can help with that but nothing officially supported. Best practices is to backup the entire VHD or put all user data in onedrive and keep just setting in the user profile so if it gets corupted its no loss to be deleted
Microsoft
Item 1 - Configuring FSLogix to point to the same profile from multiple host pools will work IF a user logs into one hos pool at a time. If a user is signing into multiple host pools simultaneously, as an example accessing remote applications from a remote desktop, then it is recommended that a unique profile is created for each host pool. It is possible to us read-only access to share a profile across host pools, but this is not generally recommended.
https://docs.microsoft.com/azure/virtual-desktop/create-host-pools-user-profile
https://docs.microsoft.com/fslogix/configure-profile-container-tutorial
https://docs.microsoft.com/fslogix/configure-concurrent-multiple-connections-ht
Item 2 - 30 GB is default max size. When using a VHDX the size on disk will dynamically grow to accommodate use.
https://docs.microsoft.com/fslogix/profile-container-configuration-reference#isdynamic
https://docs.microsoft.com/fslogix/profile-container-configuration-reference#sizeinmbs
Item 3 - Corruption of data within the profile may be handled by deleting the VHD(D), this would essentially be the equivalent of deleting the user profile and would come with the implications of doing so. It is also possible for an administrator, with appropriate permissions to the VHD and content to trouble shoot the data within the VHD similar to troubleshooting any issue with data within a standard profile.