Author: Nguyen Trong Trung

This section describes various usage scenarios discussing why and how to use a hold/release queue. They provide a good starting point for your own implementations. Saving paper and toner Secure printing Pay per print Expensive printers (approved printing) Delegated Print Release Override/change account selection using Admin web interface Release Station Cancel jobs without accounts using Admin web interface Release Station Unauthenticated printing Saving paper and toner A large source of wasted paper in organizations are documents that were never collected from the printer. Some of these uncollected documents are caused by accidental printing, and others were just forgotten. But the

Schools and colleges commonly allow students to use their personal laptops for printing to campus printers. They also want to allocate/charge printing from these unauthenticated users to the correct person. However, if the systems haven’t authenticated with the network, then user credentials are not provided with the print job (or worse, their personal laptop username is associated with the job). For example, on Windows networks, the jobs might list as guest. Mobility Print offers a solution for this problem by allowing users with unauthenticated laptops to print. For more details, see Mobility Print. Alternatively, PaperCut NG/MF also addresses this problem by providing alternate print authentication options.

“Help! Papercut is tracking jobs under the wrong username! How do I get the user to authenticate when they print the job so that it always tracks properly?” Papercut NG/MF tracks print jobs by retrieving the username from the spool file of the print job which reflects the user that was logged in at the time of printing. But what happens when the user that is logged into the workstation does not match the actual user that is submitting the job? Papercut NG/MF addresses this issue in the form of Unauthenticated Printing (otherwise known as pop-up authentication). For more detail

The User Client is used to display user balances, system notifications, and request information from the users. This is discussed in more detail in User Client. The User Client implements a number of command-line options that change its behavior. Command-line options NOTEThe command-line arguments listed below are usually used in the area/method used to start the client – a login script, shortcut, or the relevant registry key in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\. User Client command-line options OPTION DESCRIPTION –silent The silent option tells the client not to report errors if it has problems connecting to the server. If the server is unavailable at time of startup (e.g.