Running Permission Scripts for App-V packages in VDI environment

Question

Hi
We use App-V 5.0 SP1 in VDI environment.
We have a major problem with packages' permissions
Our users don't have administrative privileges on their machines.
As the option for "Security Descriptors" is discontinued, the only way to give permissions to a folder in a package is to use the VFSCACLS.vbs as a startup script of a package.
This way the first time users launch an application they're prompt to reopen it, and the second time they can use the application with the needed permissions.
The problem:
The script saves those permission changes under LOCALAPPDATA\AppV...
Therefore, everytime the users logoff the folder is deleted (VDI...) and again, they must run the script for the first  again to get the permissions back after logon!
We cannot roam the LOCALAPPDATA\AppV folder as its size can be dozens of GBs...
Folder permissions with group policy is also not a solution, as the folder name changes everytime we upgrade a package and it's impossible to follow with hundreds of packages.
So it's either we're missing something critical in the architecture with VDI environment or there's a normal solution for these situations.
Would love to get some help
Thanks
Tamir Levy

Answer 1

Hi Nicke
that's what I did! the problem is that I find my self over and over again want to sequence packages in App-V 5.0 and forced to sequence it in App-V 4.6.
I really hope that it wasn't App-V team's goal. announcing App-V 5.0 and tell us it doesn't support many things so we will still need App-V 4.6 forever.
I have to maintain 2 different App-V environments with 4 different servers , 4 different sequencers and 2 clients on each computer. it doesn't make any sense for me to forced to stay with both of the versions forever.
correct me if I'm wrong but App-V 4.6 is a legacy application. the new versions cover only support on newer operating systems and nothing more. I won't be surprised if in the next version of MDOP won't come with App-V 4.6 anymore and Microsoft will announced
it's unsupported very soon.
Every time I open a ticket with MS Support the best thing I get is "It's a known issue, we can't tell when it will be fixed"
can you help me more ? move it forward to other people from the inside? at least agree with me that something is not as expected in App-V 5.0... :(
I love the technology, I believe in it, I'm kinda depend on it and I only want it to be better
Tamir Levy