App volumes- Anyone have a working profile only snapvol.cfg? (2.13 )

[Poom22]

Hi all

Looking for a snapvol.cfg which only means the profile is saved in the Appvolume, as VMware onlys upply a UIA + Profile template, which bloats my app volumes with huge Windows and program files directories

I have tried

exclude_path=\Program Files exclude_path=\Program Files (x86) exclude_path=\Windows

But doesn't seem to do much

I don't use appstacks and dont want to save anything except the profile, as i update from a golden image to my linked clones in Horizon

[Lakshman]

Please have a look at this KB on "How to save only profile data for writable volumes in App Volumes"

VMware Knowledge Base

[Lakshman]

If you are looking for 'Profile only' snapvol.cfg specifically, please download the App Volumes 2.9 version that had 'Profile only' writable template.

Download VMware App Volumes

[Ray_handels]

Hey Lakshman,

Does that actually still work? When you use that 2.9 snapvol.cfg file?? Cool. I thought the new agent blocked that option from being used..

[Poom22]

Thanks

I did see this, the users dont have admin rights, I am 100% sure of this ,  but i suppose system processes etc still make changes to Windows and program files,

see screenshot , I think the big windows dir is because of windows updates , this my mistake not disabling it on the Golden image properly, but still it also captures large changes on the Program files even if an admin has never logged in on the linked clone ( I made another post about this and someone said it was normal behaviour , which is why im searching for a working snapvol.cfg to change this )

[Poom22]

Thanks, i'll take a look at the 212 -> 2.9 upgrade path

[Lakshman]

Hi Ray, as the support for 'Profile only' writable is stopped, I'm not sure if it will work with the latest versions. I have not tested though.

[Lakshman]

'Profiles only' writable template is not supported after 2.9 release. Since you have 2.12, going back to 2.9 is not recommended due to less features & functionalities. Even if modifying the existing snapvol with that of 2.9 to accommodate 'profiles only' changes works for now, it will not be supported by VMware support if there arise any issues in the future.

Disabling Windows updates in the golden image and recompose the existing desktops is a good idea rather downgrading to 2.9.