Rollout and maintenance

Deploy consistent output profiles and source/destination assignments using your existing endpoint administration tools. Manage policy updates independently of application binaries. Some scanner vendor settings must be configured at the workstation.

Plan your rollout

Start with a workstation or small group, then expand by team or location. Assign someone to manage configuration and someone for operators to contact when they need help. Include scanner drivers, folder permissions, storage capacity, and retention in your deployment plan.

Before wider deployment, scan a few representative documents and follow them into the receiving application. Check readability, page completeness, and filing location with the staff who use them. Keep the working configuration so you can apply it consistently across the fleet.

Update configuration separately

Use -Action Configure -ConfigurationPath ... from the deployment wrapper. Retain the previous administrator-managed policy and record what changed. New policy affects newly acquired jobs; existing jobs retain snapshots. The wrapper's Configure action does not drain the application like an MSI maintenance action.

To restore policy, validate a copy of the known-good previous configuration and deploy it through the same Configure action. Do not edit user manifests or databases to make old jobs appear to use a new profile.

Upgrade, repair, and uninstall

The wrapper creates a protected maintenance marker and waits up to twelve minutes for Paperweight desktop/worker processes to exit. The application finishes the active processing cycle before servicing maintenance and cancels capture into retained incomplete state if needed. It does not force-kill busy processes. Concurrent wrapper operations return 1618.

Use -Action Upgrade, Repair, or Uninstall with the approved MSI and publisher thumbprint. The wrapper normally removes its maintenance marker when it finishes. If an administrative session was terminated unexpectedly, investigate any remaining marker; it keeps processing stopped until the maintenance issue is resolved.

There is no self-updater. Plan how the user will reopen Paperweight after maintenance or at the next logon, then confirm source health and retained work.

Rollback and preserved data

Uninstall preserves ProgramData policy and per-user operational data. Before returning to an older application version, confirm that it can read the data from your installed version. Older software rejects data formats it does not support. The MSI blocks installation of a lower product version through its normal upgrade path.

Never restore an old queue snapshot into live processing without reconciling downstream delivery. It can redeliver documents that were already consumed. Investigate using an isolated protected copy, and test your recovery steps there before applying them to live work.

Support your users