Enterprise deployment and updates
Farino PDF 1.63.46 introduces Windows Enterprise deployment packages. Sign in as a company administrator and open Enterprise workspace → Deployment to download the MSI and deployment kit. Additional company administrators can also manage deployment. Employees with activation-only accounts cannot access this management page.
Install on managed computers
Choose x64 for 64-bit Windows or x86 for 32-bit Windows. The MSI installs for all users and requires administrator or SYSTEM privileges. Microsoft Edge WebView2 Evergreen Runtime must be installed for all users first. The kit contains a prerequisite-aware installation script, detection and uninstallation scripts, GPO templates in English and Indonesian, and deployment guides.
For Intune, upload the matching .intunewin package as a Windows app (Win32), choose System installation, and use Detect-FarinoPDF.ps1 as the detection rule. The supplied guide includes exact install/uninstall commands, return codes, architecture requirements and staged rollout steps. For GPO, assign the MSI from a protected UNC share and import FarinoPDF.admx with the appropriate language file.
Save documents and close Farino PDF before a managed installation or upgrade. Migrate an existing EXE installation by uninstalling that edition before deploying MSI, preserving documents and profiles. Validate installation, upgrade, uninstallation, activation and document editing on a pilot group before a broad rollout.
Volume licenses and device capacity
Installation alone does not activate the application or increase your license capacity. Buy the required capacity, invite employees, and assign device allowances under Licenses. Employees sign in to the application with the invited email address and their password. A single account can activate several computers if its administrator permits it.
Every activated device uses one purchased slot. A 500-device pool rejects a new device when all 500 slots are active. Release a retired computer in Enterprise workspace or buy more capacity before activating another one. Uninstalling the application does not automatically release a slot. License maintenance and subscription conditions still apply to updates; deployment packages do not bypass entitlement checks.
Signed updates and central policy
Ordinary EXE installations check for updates automatically every 24 hours while the application is running. Background download is optional. Installation waits for a user action and the normal document-save prompts. The application checks the signed release manifest, eligible license maintenance, installer checksum and trusted Certum publisher before starting setup.
Enterprise administrators can configure notification/download mode, check interval, release deferral and a local-time update window through GPO or the supplied policy script. MSI installations always remain managed by IT and receive newer MSI packages through the enterprise deployment channel. The EXE updater does not replace them.
Optional crash reports
Under Preferences → Updates & crash reports, each user can choose whether to share technical crash reports. Reporting is off by default. Administrators can block it, but cannot provide consent for an employee. Reports contain version, Windows build, architecture, error type/code and bounded application method names, without PDF contents, document paths, exception messages or credentials. Reports are retained for up to 30 days. See the Privacy Policy for details.
