PaperCut monitors printing by watching the jobs pass via a print queue. It needs to intercept the print jobs between the workstation and the printer so that it can perform analysis and control jobs for various reasons (e.g. delete it if the user doesn’t have quota available, or hold it if using a release station).
The best solution in a medium to large network is to host your printers and PaperCut on a “print server”. In some cases a print server may be a dedicated server, however on most networks an existing file server or domain server will fill this task. Hosting printers on a centralized server also has a number of administrative advantages over direct printer connection, including:
Automatic printer driver deployment and updates from the server
Centralized access control
Ability to deploy printers via Active Directory and related tools
Consolidated queue management, which allows you to
use Windows/OS level security to secure the printer (e.g. a staff only printer)
view/manage all print jobs in a queue
If you’re a small business or a distributed site organization with a modest numbers of users that are separated by different offices, then it may make more sense to print directly to a printer rather than have your print jobs travel through a print server. PaperCut’s Direct Printing feature may be best for you in this case. This feature gives you a lot more flexibility when choosing whether or not you need a print server at all.
This release contains an updated Java version which no longer supports 32-bit workstations. If you have any 32-bit users launching the User Client or Release Station from a network share, see this Knowledge Base article for more information.