Best Practices for print job delivery in PaperCut Hive and Pocket

Within PaperCut Hive and Pocket there are 3 methods for delivering jobs to a printer: Local Queue IPP/IPPS RAW/Port 9100 When the organization is first set up and printers are first discovered, PaperCut sets the delivery method to “Auto” as default. The “Auto” setting defines 3 print delivery methods: Primary Delivery = RAW/Port Secondary Delivery = Local Queue Tertiary Delivery = IPP/IPPS However, the “Auto” setting with those preset defaults might not give the organization the most efficient or reliable means of print job delivery. Because of that, we offer the administrator the ability to define a “Custom” mode of print job delivery for each printer that users will release their jobs to. Within those 3 methods, an admin may choose 1, 2, or a combination of all 3 methods. Read on to learn about the individual strengths of the 3 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 print delivery method Strengths 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. Recommend queues using RAW/LPR. Recommend “SNMP Monitoring” to be disabled on the Windows Print Queues Port tab. Recommend “Advanced Printing Features” to be disabled on the Advanced tab. IPP print delivery method Strengths 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” created by PaperCut Hive and Pocket automatically during job release.) where a dedicated client is not a feasible option moderate print volume and minimal “multi-job” release. Near ubiquitous 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 for a “high” volume of print jobs via IPP. High print volumes might see performance degradation and retries. 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 Ports 631/443 to be available between the printing edge node and the printer. RAW/Port 9100 print delivery method Strengths Excellent print performance for high-volume and batch printing. OEM printer drivers are organically supported without the need for local queues or dedicated clients nodes. Considerations Port 9100 should be available through routers and firewalls. OEM printer drivers has to be deployed via Queues & Drivers in the admin console. Raw 9100 will only work if you have deployed drivers using Queues & Drivers. Custom delivery methods Now we know the benefits of each print delivery method, let’s look at 3 environments where “Custom” delivery methods would enhance the end-user experience. Scenario 1: Medium-sized office with OEM printer drivers Environment: Medium-sized office where a super node 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 MFPs and the sysadmin wants to use the PaperCut Printer and push out Universal Drivers for their users who need finishing and tray calls. Using Queues & Drivers in the PaperCut Hive and Pocket admin console, the administrator loads the printer manufacturer’s Universal Print Drivers (UPDs). 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 OEM UPD 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 plus, OEM drivers with full-featured finishing, tray calls, color controls, and media types. The best printer delivery setup would be a “Custom” setup as: Primary Delivery - RAW/9100 via ”Any active node” Secondary Delivery - IPP/IPPS via “Any active node” Tertiary - None In this configuration, OEM drivers deployed via PaperCut Hive and Pocket always use RAW/9100. When users select the “PaperCut Printer”, PaperCut Hive/Pocket will automatically select the Secondary Method of IPP. Scenario 2: Multi-site environment with WAN interconnectivity Environment: Super nodes are strategically positioned at each location with queues servicing printers at those respective locations. Printing can be fairly heavy with large job sizes, plus users require finishing options on their MFPs. The administrator has deployed OEM Universal Drivers and expects end users to use a combination of those and the PaperCut Printer created by default. In this scenario, the best delivery setup recommended would be: Primary Delivery - Local queue via super node Secondary Delivery - RAW/9100 via super node Tertiary Delivery - IPP/IPPS In 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 volume and batch job release. If for some reason the super node is offline or the print queue is in error, the OEM driver jobs will automatically use RAW/9100. The PaperCut Printer will also use the Super Node/Queue as its primary, however, if the super node is offline or the print queue is in error, it will automatically use the Tertiary method set for IPP/IPPS.