Wednesday, April 18, 2012 8:11 PM
I am wondering if anyone has seen this before when running an App-V application. I sequenced an app on a Windows XP machine and then virtualized it using App-V 4.6 for use on Windows 7 - 64 bit machines. I have been running this on many Windows 7 - 64 bit machines without a problem but there are some that must have this application started with 'run as administrator' or it fails to start. I find this really odd as all machines are based off of the same base image and it works properly on most machines but fails to work on a few.
What should I be looking at to find the source of the issue? Most of the threads I have seen are for shimming to force the app to run as an admin but I am not sure this is my solution as it works properly on most machines.
Thanks for any help with this issue, Dennis
Thursday, April 19, 2012 2:22 AM
You shouldn't have to create an actual shim. You could try putting the below in your OSDs
The obvious difference I would think is some sort of difference between your users machines. Perhaps a GPO is set on some machines changing the UAC settings.
<ENVLIST> <ENVIRONMENT VARIABLE="__COMPAT_LAYER">RunAsInvoker</ENVIRONMENT> </ENVLIST>
Friday, April 20, 2012 9:41 PMThank you very much for the information, I will rebuild my package with this change and see if it changes this issue. All of our Windows 7 machines are in the same OU so I would be suprised if this was the issue.
Saturday, April 21, 2012 3:41 AM
You don't need to re-sequence. You just add it into the OSD of the shortcut in question
Example of an OSD: