Silent Install PDF-XChange: Deploying PDF-XChange Pro via SCCM

Deploying PDF-XChange Silently for an Unattended Install

PDF-XChange’s installers support a silent/unattended mode, which is handy if you’re pushing it out via SCCM, Group Policy software installation, or any other deployment tool rather than having users click through the wizard themselves. The general pattern for the MSI-based installers is a standard quiet msiexec call:

msiexec /i "PDFXEditor.msi" /qn /norestart

Older EXE-based PDF-XChange installers typically accept an /S (silent) switch instead, sometimes combined with a response/answer file for licensing details. Because Tracker Software has changed installer packaging and switch names across different PDF-XChange product versions (Editor vs. Viewer, and various release lines) over the years, the exact flags for the build you’re deploying can differ from the above — always confirm the current silent-install switches for your specific installer against Tracker Software’s own deployment documentation before rolling it out at scale, so you don’t end up baking an outdated switch into a production deployment package.

Which Product Are You Actually Deploying? (2026)

Worth confirming before you package anything: Tracker Software’s current lineup is PDF-XChange Editor (the standard edition) and PDF-XChange Editor Plus, which adds enhanced OCR, form creation/identification tools, dynamic stamps, and document comparison on top of the standard edition. PDF-XChange Viewer — an older, separate product some longtime readers may remember — has been discontinued for some time and is a distinct product from the current Editor line, not an earlier version of it. If you’re deploying from an installer or documentation reference that still says “Viewer,” double-check you’re not working from outdated internal packaging material, since the silent-install switches and licensing model differ between the two product lines. Both current editions ship with a free tier that runs with roughly 70% of the full feature set available (some advanced editing/OCR features require a paid licence), which is worth factoring into your deployment plan if you’re rolling this out broadly and need to know upfront which users need a licence key applied as part of the silent install versus which can run on the free tier.