AppVolumes Writable - FSlogix Office/Profile Container - Cloud Volumes - YES You can!

[vmguru]

For those who use Omnissa Horizon with Hashtag#AppVolumes Writable Volumes and FSLogix, Inc. Office or Profile Containers leveraging CloudCache Mode. There is a nasty Showstopper mentioned in the Known Issues Section of the actual (2406) Release Notes of Hashtag#AppVolumes:

https://docs.omnissa.com/bundle/AppVolumesReleaseNotesV2406/page/AppVolumes-ReleaseNotes.html

"When a Writable Volume and FSLogix Office Container are deployed together in a VDI, the FSLogix Office Container VHD is not created on an SMB file share. This issue occurs only when the Cloud Cache feature is enabled. [2791414]"

Workaround: Deactivate the Cloud Cache feature of FSLogix Office Container.

I'm happy to introduce you to a better workaround to get things working!
Let's go:

1. Turn on the Instant Clone template/full clone of the desktop where you want to get the feature mentioned above be enabled (AppVolumes Agent and FSlogix Agent should be installed)

2. Go to C:\Program Files (x86)\CloudVolumes\Agent\Config\Default in File Explorer

3. Open the corresponding (or modify all) Snapvol.cfg File in the Subfolder for the Type of Writable used in your Environment:
uia = User installed Applications
uia_plus_profile = User installed Applications with profile
profile = User Profile
Hint: Think about it again - Do you really want to use fslogix in the last 2 scenarios (uia_plus_profile and profile) 😉 ?

4. In the File system Section in the Snapvol.cfg File add these two lines to prevent the Overlay interference between FSLogix and AppVolumes writable Volumes(after virtualize=\):

exclude_path=\ProgramData\FSLogix
exclude_process_name=\Program Files\FSLogix\Apps

5. Save File

6. Reboot the Full Clone or make Snapshot of the Template and schdeule a secondary image for the Instant Clone Pool.

7. Enjoy AppVolumes Writables with FSLogix Office/Profile Containers with CloudCache enabled

Edited October 11 by vmguru