From 13th of December 2025, the print protocol option “Printer pulls job from local client”, which has been in beta, will no longer be available under Printers > select printer > Advanced > Print Protocol > Print Delivery Methods > Print protocol.
From January 12 2026, any printers with the option selected will no longer be able to print via this method.
If you have this option already selected, it will continue to work until January 12 2026. However, you should update your print protocols for any printers using “Printer pulls job from local client” before this deadline.
As a reminder, we are currently in beta for Pull Delivery for Lexmark and Kyocera, with more brands supported very soon. Learn more about Pull Delivery (Cloud delivery) in PaperCut Hive and Pocket .
Changing the “Printer pulls job from local client” print protocol on affected printers Note Printers with “Printer pulls job from local client” enabled cannot have any changes to their Advanced settings saved until the print protocol is updated. Any attempt to save without updating the print protocol will cause an error.
If your organization uses “Printer pulls job from local client” as a print protocol on any printers, follow these steps for each affected printer:
In the admin console, go to Printers, then select the printer using “Printer pulls job from local client”. The printer details drawer is displayed. Select Advanced. Scroll down to the Print protocol section, and locate any print delivery methods that display “Printer pulls job from local client”. Select the drop-down, and change the print delivery method(s) to any of the “Push” options: RAW printing: 9100 (note that this option requires a print queue with a manufacturer driver) IPP Local Queue Tip Instead of “Push” delivery options, you can instead use “Printer pulls job from cloud”, which requires the jobs to be replicated to the PaperCut Cloud Node. See here for more information.
Both push from local and pull from local require a direct line of sight between edge nodes and the printers, so this should require minimal changes to your infrastructure. You may need to open Port 9100 or IPP ports (80/443/631), depending on your chosen push method. Learn more about print protocols in PaperCut Hive and Pocket .
Note PaperCut highly recommends you discuss any changes to Print Protocol with your PaperCut Authorized Partner.
Frequently asked questions What was “Printer pulls job from local client”? When PaperCut Hive launched Pull Delivery into Percolator for Lexmark and Kyocera, we offered two Pull options:
Printer pulls job from cloud: The printer pulls the print job directly from the PaperCut Hive Cloud Node.
Printer pulls job from the local client: The printer initiates communication with a local edge node, and attempts to pull the print job from this device.
Why is “Printer pulls job from local client” being deprecated? There are a number of reasons we have made this decision:
Of the two Pull Delivery options, the “Printer pulls job from cloud” option has been used significantly more.
With the addition of Ricoh and Sharp support for Pull Delivery coming in January 2026, we have made some major changes to our infrastructure to create an improved experience for Cloud Pull Delivery. Removing support for local pull has enabled us to focus on improving this experience.
It is not possible to support “Printer pulls job from local client” on some brands at this time. Focusing on Cloud Pull Delivery will allow us to add support for more brands, faster.
Articles in this section
- PaperCut MF - New SSL certificate (macOS)
- New KB article template
- Xerox embedded devices - Incorrect login screen issues
- Handling hidden characters in card numbers
- Scan to multiple email destinations
- PaperCut NG/MF Security Bulletin (March 2026)
- PaperCut Hive and Pocket Compatibility Tool
- Enabling ARM64 support in PaperCut NG/MF Print Deploy
- Incorrect stapling when printing multiple copies via a Find-Me queue using HP PCL drivers
- Resetting the PaperCut Hive or Pocket app (Android & iOS)
Comments
0 comments
Please sign in to leave a comment.