Print Driver not working as expected V5

[chRMT_042003]

I just bought and registered yesterday.

- Installed on Windows Server 2008 R2, 64 BIT, Service Pack 2
- The file I installed was the PDF-XChange 2012 Setup, version 5.0.268.0
- We purchased PDF-XChange STANDARD

I have two fairly major problems:
When I go to print using the PDF-XChange driver FROM ANY APPLICATION, the "Printing Progress" dialog flashes, but the "Save As" dialog does not appear.
- this does not always happen, occasionally (about 1 out of 10 times) the "Save As" dialog comes up
- I DO have the "SAVE" preferences set to "Show Save As" checked

When I try to choose a specific directory to save to (e.g. if I did NOT want to show the "Save As" dialog and print directly to a file using a predefined macro based filename), the only directories I am able to browse to are under my user profile: desktop, my documents, etc.

[Paul - PDF-XChange]

HI chRMT_042003,

the first thing I would ask is if this is a Terminal Server (Remote Desktop Services) or not. That makes a big difference. If it's not I would ask why you installed the printer on a server. It cannot be set up as a shared printer on a print server if that is your intention.

Regards the locations where you save to - I would suggest that this is related to your server set up. The available locations in that dialogue come from Windows - we call their API and the dialogue you see is theirs. I suspect this is a permissions issue and that is why the server is only allowing you access to files that the user who ran the print process has access to.

The permissions on a server are sometimes handled quite differently to a workstation, can you advise as to your objective in running this on a server?

hth

[chRMT_042003]

Thanks Paul,

- Yes, this box is a Terminal Server machine. I access through RDP.
- I am an admin on the machine, so I do have access to the locations that I want to print to. Is it possible that the print process runs under a different user/profile?

[Paul - PDF-XChange]

Thanks for that chRMT_042003,

OK - so the driver is well supported in this environment. Did you install the driver through a console (not an RDP session) and use change use /install and change user /execute?

[chRMT_042003]

No... I'll uninstall and try doing it that way.

[Paul - PDF-XChange]

I just tested the current build - 269 and it is working correctly in 2008 R2 using /change user /install and change user /execute.

A couple of things to note.

1. Terminal Server's do have fairly rigid default settings for where user's can write to and being restricted to their own profile folders is typical.

2. If you elect to install the Free Viewer with this (it is an option in the Standard Installer - check the box to download...) then you should also run the command line switch to set associations for all users before switching back to change user /execute else the registry settings will not be in place for all users.

To do this, at the command prompt as Administrator, after calling change user /install and running the GUI installer for the Printer+Viewer navigate to C:\Program Files\Tracker Software \PDF Viewer and then run PDFXCview.exe /makeassoc:web=true

Other options here include:
PDFXCview.exe /makeassoc:web=false // disables plugins and makes association for PDF-files
PDFXCview.exe /makeassoc:web=false&webonly=yes // disables plugins only, association for PDF-files not be changed

Another thing that you may want to consider if using the Free Viewer on a Terminal Server is to "Hide Restricted 'PRO' functions in the Free Viewer Version". To do this for all your users at once you again need to run something after install and before switching back to execute mode on your terminal server. Most important of all is that this is done before any of your users attempt to use the Viewer. This is because on your user's first run the Viewer will look for settings in the that user's CURRENT_USER section of the registry, if it doesn't find any it will copy them from the LOCAL_MACHINE hive set up during install and you want this set BEFORE that happens, so again while still in install mode, run the attached reg key file.

Once this is done you can switch back to execute mode with change user /execute and all your users will have the PDF-XChange Viewer as default for both stand alone and web browser files.

hth