Q Why does PaperCut change the printer driver setting from “start printing immediately” to “start printing after last page has spooled” ?
PaperCut needs to analyze the complete document before sending it to the printer. So, when a print job comes PaperCut pauses it until it spools to the server completely and then analyzes it. (E.g. To check if the user has enough credit, page count). Changing this setting is a technical requirement for PaperCut to ensure reliable monitoring. It might have a small impact on the printing performance while the document spools on the server.
The analysis time will vary with the size of the document. But is usually very fast (a few seconds). If a multiple megabyte spool file or the server is heavily loaded, then it might take more time. If page level color detection has been enabled on the printer, then that can slow the analysis time because PaperCut needs to do much more complicated checks on the print job.
As a workaround, you can also configure PaperCut to ignore a specific print queue and then this setting will no longer be applied. However, this does mean that the job will not be tracked by PaperCut.
-–
Articles in this section
- Manually Generating and Installing iOS AirPrint Profiles for Mobility Print (When Auto Setup Fails)
- Common Xerox Issues and how to fix them
- PaperCut NG/MF Security Bulletin (May 2025)
- How to permit users to cancel print jobs at HP MFD
- How to remove a print job from the queue
- Upgrading the PaperCut Hive Ricoh Full Embedded App
- Share ARM64 Drivers from Windows Print Servers
- Printing from Microsoft Edge Browser and other Windows 10 and 11 Store Apps
- Top 10 best practices for implementing Print Quotas in education
- PaperCut Hive and SentinelOne
Comments
0 comments
Please sign in to leave a comment.