New Pull Delivery print options for PaperCut Hive

Overview

Are you an IT admin struggling to enable Find-Me Printing in a complex or segmented network environment? Our new Pull Delivery print options in PaperCut Hive are designed just for you!

This feature is perfect for organizations that meet one or more of the following criteria:

• Want to avoid requiring a print server or appliance.
• Organizations who want Cloud pull delivery, where the printer pulls the print job directly from the cloud.
• Require secure HTTPS (Port 443) delivery from local client machines to the printer with the added option of maintaining data sovereignty.
• Operate in hybrid environments where no user devices may be online at the time of print release.

The basics: Shift from Push to Pull

Traditional printing workflows rely on the end user’s computer to process and push print jobs directly to the printer, often using protocols such as RAW 9100 or IPP. These methods present challenges:

• RAW 9100 transmits print jobs in plain text.
• Client machines need a line of sight to the printer.
• Reliance on an always-on client or print server where client availability is uncertain adds an infrastructure burden.

PaperCut Hive’s new Pull Delivery print options eliminate these inefficiencies by shifting from a push-based model to a pull-based approach. Multifunction Devices running the PaperCut Hive Full Embedded app (MFDs) retrieve print jobs on demand directly from the configured source:

• Cloud – MFDs pull the print job from the Cloud Node: Ideal for environments where clients do not have a network route to the printers.
• Local – MFDs pull the print job from a local client on the network: Ensures print data remains in the local network for data sovereignty.

Print Job Flow (Pull-Based)

1. A user sends a print job from their device.
2. The job is replicated to the Cloud Node, and locally if the network allows.
3. At the time of release, the MFD securely downloads the print job over a 443 connection, from the Cloud Node or a local client dependent on configuration.
4. The job is processed and printed by the MFD.

Diagram showing the flow after a user has released a print job where the Printer pulls the job from the Cloud Node:

Diagram showing the flow after a user has released a print job where the Printer pulls the job from the local client:

The build and rollout plan

Brand support

Cloud/Local Client Requirements

• Pull job from the cloud: You need to enable the Cloud Node from the PaperCut Hive admin console -> Edge Mesh, for job processing and print release.
• Pull job from the local client: You need to have a local client in the network for job processing and print release.