Has anyone been able to get this to work? Should I not be using the template in /cloudvolumes/apps_templates/? Should I be modifying one of the writeable disk templates instead?
Yes. The appstack becomes read only after the provisioning process. If you need to have a read write disk you need to create a writable. Change the writable template (i'd suggest changing the UIA only, saves the hassle of removing the profile part ) and create a writable using that template. It will automatically create a writable with the user name in it so you also know what writable is for what user.
If you were to copy it from 1 datastore to another and import it in another Apppvolumes manager it will be attached to that specific user as well.
Thanks Ray....Going to give this another go today by using a copy of the Writable UIA template instead of the AppStack template. Hoping you nailed!
Well....Looks like using a modified version of the writable profile disk got me passed my initial problem of the VM wanting to run like a promising machine. Makes sense since I was using the App template as my initial base. Appears this article needs revised as it does say to use the app writable template. Create a custom writeable volume for specifically the Outlook OST and Search Indexes | Age Roskam
This new configuration (using the profile writable template as the base) does mount the writable and does store the OST and no other drives are seen by the user (like the writable disk) until I assign and mount a application disk from App Volumes. If the user has both an appstack assigned and is using my new writable template, the user will see an new disk (E:) and be able to write to it. If users can see this disk, they will surely move files to it and I don't want that. My guess is that Trojans would love to store data here and have it persisted back.
Again....Does anyone really have something like this working or is it even supported by VMWare? Seems like VMware is strongly recommending getting away from writable profile disks to persist user data and now recommending the UEM instead. But if using the UEM only makes Outlook re-index after every session, how can we get away from this?
I have a support request in now and am waiting on a call. Will see if they can provide a solution.
Thanks for looking
Yes, we are using writable volumes for a few years now. To be honest, one of theings we don't store is the OST file because users have a 10GB mailbox, we would end up with mail being stored in very expensive SSD disks, not really feasible .
Make sure to create the following registry key
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\svdriver\Parameters\DriveLetterSettings=6 (DWORD). This hides the drive letter for the writable but does give it a drive letter name. The driveletter part is mostly done for applications that don't install on a network drive (looking at you google). You could use other values and just disable driveletters for appstacks and writables altogether.
I would also suggest creating this key This shows the free disk space on the writable (and the amount a user can still safe on his writable) instead of the GI.
This was really helpful. I was tasked with setting up non-persistent instant clones for a client but their line of business app required cached mode in outlook. The licensing they got sold on was also 0365 for office and Windows 10 Enterprise (E3 subscription). This created an additional layer of complexity that would cause the writeable to become corrupt after the first login. Testing with a KMS server did not replicate the issue.
The writable profiles in our test environment kept corrupting. After one login it would get stuck at the welcome screen. I would have to remove the desktop in view, then power off manually in vcenter and then delete the writeable (or restore from backup).
When they did work the profiles slowed down login times and were needlessly large. I wish %userprofile% was accepted in snapvol.cfg...
I made a custom snapvol.cfg to only virtualize a custom OST path like in the article you shared and also included the path for windows search. You would need to include a script to enable and start windows search when the writeable mounts or it kills your provisioning time (windows search should be disabled during provisioning). VMware Knowledge Base
I use UEM to capture all other settings and have implemented folder redirection through UEM.
App Volumes 2.16
using direct attach to host
Azure AD SSO (password hash)
Windows 10 Enterpise (E3 subscription).