Provide CLI/Silent Parameters for Print-to-Fax Driver or Allow Legacy Driver Linking during App Migration
User Story: > As an Enterprise IT Administrator, I want to be able to silently deploy or link the print-to-fax driver remotely (via PDQ/Intune) without requiring local admin credentials at the user endpoint, so that I can scale our app migration without manual workstation interventions.
Problem/Pain Point: > When users switch to the new app, the existing print-to-fax driver is not recognized. The app forces a reinstall of the driver, which triggers a Windows UAC prompt for admin credentials. This completely breaks silent, remote deployments for enterprise customers, forcing IT admins to physically or remotely log into every individual machine.
Requested Solution Options:
Primary Request: Provide a standalone, silent driver installer (MSI or executable with switches like /quiet /norestart) that can be pushed via PDQ Deploy under the System account.
Alternative Request: Update the new app's initialization logic to detect and successfully bind to the registry paths of the previously installed print-to-fax driver.
Customer Impact: High. Affects enterprise deployment velocity and increases IT overhead for migrating accounts.
Mac
shared this idea