Deploying in an enterprise environment

[Alpenblick]

Hi all

I'm wondering if those who deploy PDF XChange Editor Plus/Pro to enterprise environments could share some good practices, valuable experiences and do's and dont's?

I.e. we'd like to disable a bunch of configuration options: The obvious things like auto update, registration, serial key dialogs, ...but also JS execution or some of the cloud storage targets or the ability to set the timestamp service for signing. Now, while (some of) these configuration items can be set in the registry, it seems the all go to the HKCU, which means, it can be changed by the user. That's a least a problem if not a killer in an enterprise env. How do you deal with this?

What have been the challenges you had been facing in an enterprice env?

[Paul - PDF-XChange]

Hi, Alpenblick

take a look at the system administration manual here: https://help.pdf-xchange.com/sysadmin/

Two approaches for the things you mention, some are Group Policies so outside the registry where users can affect change. https://help.pdf-xchange.com/sysadmin/e ... lates.html

Other things are better handled by the installer, like not installing unwanted features such as the Updater. This is stypically am MSI option https://help.pdf-xchange.com/pdfxp11/sw ... ers_p.html like NOUPDATER

Code: Select all

NOUPDATER

If this property is unspecified, or specified with a value of "0", then the PDF-XChange Updater will be installed. If specified with a value of "1" then the updater will not be installed. (Available from build 310).

Syntax

NOUPDATER=<0>

Maybe take a look at thar admin manual and let us know if you have specific questions?