Quantcast
Viewing all articles
Browse latest Browse all 6566

Adobe X prints to network printer using shell extension, while Adobe XI does not.

OS: Windows 7 64 bit

I use an ActiveX control in IE10 to print a pdf using a windows shell command.

 

The command line seen by the AcroRd32.exe is similar to the following:

"C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe" /t  “<Full path to PDF file.pdf>" "<network print queue name>" “winspool” “NE03:”

 

Where "NE03:" is the port reported by printer properties.

 

If I deinstall Adobe Reader XI, and reinstall Adobe Reader X, the same scenario works like a champ.

 

I have done some research and I have found like many out there, that turning off "Protected Mode" in Preferences, allows the shell command to succeed.

 

Unfortunately, this is not an option for my customers.

 

Further reading provided more details about possibly using a trust setting that disables the protection for just the specific resource needed might be a way to go.  So the question is - has anyone else needed to do this and found the trust setting that works?

 

The file being printed exists in the default temp directory, and we have confirmed the user has access to the directory and the file itself.

 

I saw in other searches a few Windows trust settings set by policy that look promising, but if this is something that is already known, I'd rather not use trial and error if I can avoid it.

 

One promising setting I see is this one:  %Windir%\System32\Spool\Printers  What do you think - in protected mode, does Adobe XI not have access to this directory - I ask because that is where the printer driver I am using is coming from?

 

I want to use the new security features, but I have to get my customers printing again.  Am I reallly supposed to tell them the main reason they are deploying Adobe XI must be disabled for them to keep printing?

 

-- PK_Developer


Viewing all articles
Browse latest Browse all 6566

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>