App-v 5 File Permissions, any changes on the horizon?

Question

Hello, having now started to use App-v 5 in our test environment I am starting to see the pain that the new file permissions are going to cause us for applications that want to write outside the default install directory. I've followed Dan Gough's solution
to the problem but the fact the user still has to ok the initial error is not really good for user experience.
Are there any plans from Microsoft to look into these limitations?
 

Answer 1

As an FYI, I'm not in love with Dan Gough's solution (although it is extremely
clever), you can overcome the initial error by way of a publishing script.
What you have to remember is that you need to wait until after publishing is finished to implement the fix, but if you just run a standard pub script it won't work as publishing isn't finished yet.  However, you can do this-
import-module AppvClient
$package = Get-AppvClientPackage -name mypackage
$i = 0
#do {Write-Host $i; $i++; sleep(1)}
do {sleep(1)}
while ($package.IsPublishedToUser -eq $False)
#Write-Host $i
#now run what you want, as publishing will now be completed
your deployment XML will Run the above ps1, but it needs to NOT wait.  We use the above script when we want an exe inside the package itself to 'autostart' immediately after being published.  We use a lot of non-persistent VDIs
so something as simple as a reboot isn't possible.
I used this as a test of Dan Gough's solution, and it did work for us.  You will still want the check under StartVE, in case the package is repaired (as an aside, it would be really nice if there were repair scripts).
Also its worth mentioning that App-V knows the folder was copied and original deleted.  If you run the fix, and issue another publishing command of that package, App-V throws an error, but the package is still usable.