App-V and Adobe Reader: Access Denied when opening a PDF file
In many cases virtual applications will talk to physical ones. That’s one of the reasons to keep Adobe Reader installed locally.
But we’ve got an issue with the Reader again.
Launching a PDF file from within the bubble gave an Access Denied error (using a physical Adobe Reader 10.1):
There was an error opening the document. Access Denied
This issue exits only when the PDF file is stored on a “personal folder”, like the Desktop-folder for example. (local User NTFS permissions?).
This isn’t an App-V issue but a Reader X feature called Protected Mode that gave this error.
It can be solved with some basic OSD scripting, but the first step is here to stay: “Know your application”. As Reader X gave this error, we can disable this feature with a registry key. Most of the work is to find out what registry key to set. To keep this short, here is my OSD script that disables Adobe Reader Protected Mode when opening Reader from within a App-V application:
<REGISTRY>
<REGKEY HIVE=”HKCU” KEY=”SOFTWARE\Adobe\Acrobat Reader\10.0\Privileged” NOREDIR=”FALSE”>
<REGVALUE REGTYPE=”REG_DWORD” NAME=”bProtectedMode”>00000000</REGVALUE>
</REGKEY>
</REGISTRY>
This goes into the VIRTUALENV-tag.
Happy sequencing!
We are experiencing the exact same issue in our environment and are attempting to implement the fix.
So far users have only seen this from outlook so we attempted to update that OSD file with the registry entries by itself but it does not appear to solve the issue.
Would this need to be applied to every OSD file for the entire office package or am I missing something?
Is Outlook delivered through App-V, and Adobe Reader 10 installed locally?
I found the same problem today with a sequenced version of Firefox. Unfortunately I did not find this article until I spent a few hours arriving at the same solution! Additionally though, you need to configure Firefox to always open PDFs in the external Reader application for this to to work.