Within PaperCut Hive and Pocket there are 5 methods to deliver jobs to a printer:
- Local queue delivery
- IPP (Internet Printing Protocol)
- RAW printing: 9100
- Printer pulls jobs from cloud (PaperCut Hive only)
- Printer pulls jobs from local client (PaperCut Hive only)
Let’s take a look at how print delivery protocols work in PaperCut Hive and Pocket, including what protocols are available, and when you might want to change from the default settings. If you already know all about print delivery protocols, jump to the scenarios at the base of this article to find some custom setup recommendations that work for organizations like yours.
About the Default print protocol
When the organization is first set up and printers are first discovered, PaperCut sets the delivery method to “Default”. The “Default” setting defines 3 print delivery methods:
- Primary delivery method = RAW printing: 9100
- Secondary delivery method = Local queue delivery
- Tertiary delivery method = IPP (Internet Printing Protocol)
PaperCut Hive and Pocket will attempt to use these protocols in this order to deliver an end-user’s print job to the printer.
About Custom print protocols
Sometimes, the “Default” setting’s preset delivery method priorities may not give an organization the most efficient or reliable means of print job delivery for their specific environment and needs. In this situation, administrators have the ability to define a “Custom” print job delivery setup for each printer that users will release their jobs to.
Within those 5 methods, an admin may choose 1, 2, or a combination of 3 methods.
Read on to learn about the individual strengths of those 5 methods so you can configure your print delivery methods for optimal print job performance and reliability.
Let’s examine each method more closely.
Local queue delivery
Local queue delivery in PaperCut Hive and Pocket is used when a print queue on a user’s computer acts as a bridge between the client and the printer. Once a user releases the print job, if this method is chosen, it will check for any computer with a local print queue and then send the print job to the printer.
Benefits
- Consistent print performance for “multi-job” release (batch job release).
- Uses a combination of printer drivers on user’s computers where the client is installed.
- If you create a Print Delivery Profile with dedicated clients and queues, it’s a predictable print path for a printer.
Considerations
- Requires dedicated clients with verified working queues to provide a reliable print experience.
- Requires Windows Spooler or CUPS (macOS) in good working order.
- Works best with OEM “Type 3” drivers. Type 4 drivers are not recommended.
- If setting up print queues in Windows or Mac OS, it is recommended to use RAW or Line Printer Remote as the protocols.
- Windows only: recommended that “SNMP Monitoring” is disabled on the Windows Print Queues Port tab.
- Windows only: recommended that “Advanced Printing Features” is disabled on the Advanced tab.
IPP (Internet Printing Protocol)
IPP is an acronym, like everything else in the print world. It stands for Internet Printing Protocol. It’s basically a protocol for printing documents over a network – usually the internet. IPP has more robust features than LPD, which makes it generally better for modern, complex print environments. Admins and users can quickly check job attributes, status queries and error reporting. The downside is that IPP is a bit more complex to implement, and some older printers won’t support full IPP capabilities.
Benefits
A good fit for:
- small offices where printer queues and drivers are not maintained or managed (IPP does not use printer drivers but employs a “ticket” automatically created by PaperCut Pocket/Hive during job release)
- where a dedicated client is not a feasible option
- organizations with a moderate print volume and minimal “multi-job” release.
- Near universal support for many makes and models of A3/A4 printers.
- Printers supporting IPPS enable PaperCut Pocket/Hive to provide “end-to-end” print job encryption.
Considerations
- Many OEM printers are not suited to a “high” volume of print jobs via IPP.
- High print volumes might see performance degradation and multiple attempts to print the same job.
- Batch Printing might see performance degradation and retries.
- OEM printer drivers are not supported via IPP.
- Supported PDLs are PDF, URF, and Image.
- PCL and Postscript PDLs are not supported across most makes and models.
- The stapling option is supported via Mobile Job Release.
- Requires Port 631 and Port 443 to be available between the printing edge node and the printer.
RAW printing/Port 9100
The most common use of Port 9100 is for RAW printing, where print jobs are transmitted to the printer in their raw form without additional processing. This simple, efficient method of communication reduces overhead and streamlines printing, making it ideal for IT departments managing multiple printers in an environment.
Benefits
- Excellent print performance for high volume and batch printing.
- OEM printer drivers are organically supported without the need for local queues or dedicated client nodes.
Considerations
- Port 9100 should be available through routers and firewalls.
- Raw printing: 9100 requires deployed drivers using Queues & Drivers. If using OEM printer drivers (manufacturer drivers), these can be deployed via Queues & Drivers as well.
Printer pulls jobs from cloud (PaperCut Hive only)
With “Printer pulls job from cloud” (aka Cloud Delivery), the PaperCut Hive embedded app can pull the print job directly from the cloud, without the need for a local client.
Cloud delivery removes reliance on on-premises infrastructure, facilitating a Zero Trust network environment where direct client-to-printer communication is not required.
Benefits
- Allows customers to print using Zero Trust network architecture.
- Eliminates the need for print clients in the network for print release.
- Allow customers to achieve client network isolation.
Considerations
- This protocol is currently available for Lexmark and Kyocera only. (Ricoh to follow next.)
- If there are PaperCut Hive local clients available in the network, consider setting secondary and tertiary protocols for boosted print reliability. Note that adding fallback options will not be a completely Zero Trust network approach.
- The speed of the printing depends on the speed and reliability of the internet available in the organization.
Printer pulls jobs from local client (PaperCut Hive only)
With “Printer pulls job from local client”, the PaperCut Hive embedded app can pull the print job directly from a PaperCut Hive local client. This allows organizations to print securely without using IPP or RAW Printing/Port 9100 protocols.
Benefits
- Excellent print performance for high volume printing.
- Suggested option for printing large size print jobs.
- Allows customers to keep the print data local (within their network) allowing for control over data sovereignty.
Considerations
- This protocol is currently available for Lexmark and Kyocera only. (Ricoh to follow next.)
- Needs PaperCut Hive local clients for printing.
- If a Print Delivery Profile with specified local clients applies to this printer, these clients will be used for job delivery via this protocol choice.
Scenarios for enabling custom delivery protocols
With each print delivery method offering different benefits, how do you know which to choose? Let’s look at environments where “Custom” delivery methods would enhance the end-user experience — as well as some best practice tips for setting them up.
Scenario 1: Medium-sized office with manufacturer (OEM) printer drivers
Environment
- Medium-sized office where an always-available client is not a feasible option.
- Users like to submit jobs to be held for release at a later time (batch release).
- The office has a mix of MFP manufacturer brands.
- The office sysadmin wants to use the PaperCut Printer (Find-Me printing) and push out a manufacturer driver using a Universal Driver to their users (who need finishing options and tray calls).
Recommended setup
- Install and deploy manufacturer drivers: using Queues & Drivers in the PaperCut Hive or Pocket admin console, the sysadmin installs and deploys the printer manufacturer’s Universal Print Drivers (UPDs). Learn how to deploy a manufacturer driver.
- Select the following “Custom” print protocol options:
- Primary delivery: RAW printing: 9100
- Secondary delivery: IPP (Internet Printing Protocol)/IPPS
- Tertiary delivery: none
Benefits of this setup
In this configuration, manufacturer drivers deployed via PaperCut Hive and Pocket always use RAW printing: 9100 first, then fall back to IPP. This is a great option since most manufacturer’s UPDs cover entire families of models and negate the need for “model-specific” drivers. Then the administrator can deploy the manufacturer driver to all users who are running the PaperCut Hive/Pocket Client.
This provides all deployed users with a PaperCut Printer for basic print job features like simplex/duplex and color/grayscale prints, but also access to manufacturer drivers with full-featured finishing options including tray calls, color controls, and media types.
However, when users select the “PaperCut Printer” (default Find-Me print queue), PaperCut Hive/Pocket will automatically use the secondary protocol, IPP.
Scenario 2: Multi-site environment with WAN interconnectivity
Environment
- Always-available clients are strategically positioned at each location with queues servicing those locations’ printers.
- Users frequently print large job sizes, and also require finishing options on their MFPs.
- The sysadmin has deployed manufacturer (OEM) universal drivers and expects end users to use a combination of those and the PaperCut Printer (default Find-Me print queue).
Recommended setup
In this scenario, the best delivery setup is:
- Primary delivery: Local queue via clients selected in the printer’s associated Print Delivery Profile
- Secondary delivery: RAW printing: 9100 via clients selected in the Print Delivery Profile
- Tertiary delivery: IPP (Internet Printing Protocol)/IPPS
Benefits of this setup
With this configuration, both OEM print queues are deployed and the PaperCut Printer will use the super node/print queue at each location. This provides efficient “locational” based queue delivery and provides good support for heavy print volumes and batch job release.
If, for some reason, the clients specified in the printer’s Print Delivery Profile are offline, or the print queue is in error, the manufacturer driver jobs will automatically use RAW printing: 9100. If this doesn’t work, the final fallback option is IPP/IPPS.
Scenario 3: Hybrid working places with no always-available clients for print release
Environment
Customer uses a network client isolation setup (where no end-user device is being able to talk to other device in the network directly) as part of their organization’s Zero Trust strategy. No dedicated infrastructure is available for inter-network printing
Recommended setup
In this scenario, the best delivery setup is:
- Primary delivery: Printer pulls jobs from Cloud
- Secondary delivery: None*
- Tertiary delivery: None*
*Note: if end-users very frequently print large size (>500MB) jobs, Secondary/Tertiary delivery protocols based on local network such as IPP or RAW printing: 9100 delivery, are recommended. If using these additional protocols, the setup is no longer Zero Trust.
For a completely infrastructureless environment, also set up mobile release and/or job submission via the Chrome extension (for Chromebook users).
In the chance of a print release failure, the job will automatically appear to the end-user for re-release. When printing very large documents (>500MB), printing speed depends on available internet speed.
Benefits of this setup
With this configuration, organizations can have a print management system that is compatible with their Zero Trust network architecture. No end-user device needs to talk to any other device in the network for secure print release.
Scenario 4: School with segmented network
Environment
- The school segments their networks to distinguish between teachers and students.
- A school does not want student devices to communicate directly with printers, other faculty devices etc.
Recommended setup
In this scenario, the best delivery setup is:
- Primary delivery: Printer pulls jobs from cloud
- Secondary delivery: IPP (Internet Printing Protocol)/IPPS
- Tertiary delivery: RAW printing: 9100
For a completely infrastructureless environment, also set up mobile release and/or job submission via the Chrome extension (for Chromebook users). It is recommended to bulk deploy the print clients to end-users.
If users are prone to printing very large documents (> 500 MB), the printing speed will depend on internet speed availability. If some end-users (for exampe, teachers, faculty) need to print large volume jobs constantly, we recommend adding secondary or tertiary delivery methods based on local network protocols to maximise print performance.
In the chance of the print release failure, jobs will automatically appear to end-users for re-release.
Benefits of this setup
- This minimizes the risk of a printer or port being accessible to outsiders for network attacks.
- This setup works with the customer’s pre-existing network client isolation providing the print delivery configuration that fits right in!
Scenario 5: Private network with extensive privacy and data sovereignty policies
Environment
- A hospital or government office with extensive privacy and data sovereignty policies.
- They have internal networks to keep all data local. They do not want to adopt cloud storage and cloud job processing.
Recommended setup
In this scenario, the best delivery setup is:
- Primary delivery: Printer pulls jobs from local client
- Secondary delivery: IPP (Internet Printing Protocol)/IPPS
- Tertiary delivery: Local queue via clients selected in the printer’s associated Print Delivery Profile
For organizations that prioritize the data being kept local — and still want enhanced security for print delivery — the “Printer pulls jobs from local client” protocol is the best option.
If the organization also has multiple local clients (edge nodes) available, consider setting secondary and tertiary delivery protocols based on the local network (such as Local queue delivery or IPP).
Benefits of this setup
- This approach respects the preferred client settings in the custom print delivery profile associated with the printers.
- It also minimises dependency on the Cloud Node for processing or delivering the jobs directly to the printer.
Comments