App-V 5.0 SP2 with Mandatory Profiles

Question

Hi,
We are having some issues with App-V 5.0 SP2 with HFX2 and HFX4 on our Windows 7 x64 Clients
We use mandatory profiles and delete the local profile on logoff,
HFX2 Issue:
The AppData\Local\Microsoft\AppV\Client\VFS\<GUID> is only created once, subsequent logins don't have the folder structure created for the package VFS and all folders have read/write access for the user, when they should follow the base OS folder permissions
We have found that a registry entry is created in HKLM\Software\Microsoft\AppV\MAV\Configuration\Packages\<GUID>\UserConfigEx\<USER-GUID>
if we manually delete this registry key then appv will re-create the VFS folders in local app data
AppV seems to be setting key's saying its created those folders and expects them to be there on the next login, is there a way to tell AppV that we are using mandatory profiles and to re-create the folders?
HFX4 Issue:
Hotfix 4 is a bigger problem in that a registry entry for <USER-GUID> is created in HKLM\SOFTWARE\Microsoft\AppV\Client\Virtualzation\LocalVFSSecuredUser
The first time appv is used for that user, it works, all subsequent times appv packages fail to load unless that registry string is manually deleted.
Is there any way to fix App-V 5 to work with mandatory profiles which are deleted on logoff?
Thanks!

Answer 1

Hi Nicke,
The registry key's are located in HKLM, which causes permission problems as our uses are all standard users
the HFX2 issue sort of works, the
UserConfigEx key is created with the logged on user having read/write permissions, so as long as that user successfully runs a logoff script then the key is deleted, if the desktop crashes without running the logoff script and a new user logs in, then they
don't have the rights to delete the sub keys and all future app-v localappdata VFS permissions are broken on that client,
The HFX4 issue registry keys are all write protected from standard users,
I'm not 100% sure these are the only area's which are causing problems (they are just the ones I've found!) and that just deleting the registry entries completely fixes the problem.  I didn't go down the path of deleting HKLM keys as a user as it seemed
a bit of a brute force hack to me which I was trying to avoid :)
If I give users rights to delete HKLM\Software\Microsoft\AppV\MAV\Configuration\Packages subkeys
then I think they could break published applications if the <GUID> folders are somehow deleted?
I was actually pretty surprised to find out that App-V 5.0 stores permanent information about user's in the HKLM hive, I would have thought all of this should live in the HKCU hive!
I've not been able to find any documentation on how App-V uses HKLM keys to keep track of processes its already performed on a user and doesn't want to do again,
Thanks!