How the Print Scout Auto Updater works

This guide is for IT administrators managing Print Scout on Windows workstations enrolled in the Print Scout Auto Updater preview. It explains how the Auto Updater works, the two supported package delivery methods, and how to review, publish, and monitor updates using the Print Scout API.

ImportantThe Print Scout Auto Updater replaces the manual Print Scout upgrade process with a cloud-managed update workflow. Published updates are automatically detected and installed during the Print Scout check-in cycle. Existing customers using older EXE-based installations must manually upgrade to a supported MSI-based version before Auto Updater can be used.

How the Auto Updater Works

HP Insights manages the Print Scout update process. Administrators publish updates through the Print Scout API, and Print Scouts automatically download and install applicable updates during their normal check-in cycle.

Swagger route notationSwagger displays /updates as a relative route because /print-scouts is already included in the server base URL. The full endpoint path is /print-scouts/updates.
  1. An administrator publishes an update. Updates can be targeted to all Print Scouts in a customer organization or limited by Print Scout ID and applies-to version.
  2. Print Scouts check in with HP Insights during their normal reporting cycle.
  3. HP Insights determines whether the published update applies to each Print Scout based on the customer ID, Print Scout ID, and applies-to version specified when the update was published.
  4. If an applicable update is available, Print Scout receives the update details.
  5. Print Scout downloads the MSI package from either a HP-hosted or customer-hosted location.
  6. Before installation, Print Scout verifies the package's HP digital signature. Unsigned or modified packages are rejected.
  7. Print Scout installs the update silently. Depending on the update, a workstation restart or Print Scout service restart may be required.
NotePublishing an update makes it available for download. Print Scouts detect and install applicable updates during their next check-in cycle.

Supported Workflows

Print Scout updates can be delivered using one of the following workflows:

  • HP-hosted download (recommended): After an update is published, Print Scouts download the package from a HP-managed location. No additional infrastructure is required.
  • Customer-hosted download: Use this workflow when your organization requires internal validation or approval before deploying software. Download the MSI package, complete your review process, and host the approved package on an HTTPS server. When publishing the update, provide the package URL so targeted Print Scouts download the package from your server instead of the HP-hosted location.

Both workflows use the same update management process. The only difference is where the package is downloaded from. In all cases, Print Scout verifies the package's HP digital signature before installing the update.

Known Preview Limitations

  • Available only to customers enrolled in the preview and enabled through a feature flag. To request access, contact HP Support.
  • Windows only. macOS Auto Updater support is planned separately.
  • Requires Print Scout 8.1 or later. Earlier EXE-based versions must be upgraded manually before Auto Updater can be used.
  • Targeting, batching, and rollout controls may change before general availability.

Related topics