Chapter 7. Advanced Printer Management

Table of Contents

Adding and Removing/Deleting/Ignoring Printers
On Windows
On Mac
On Linux
The Template Printer
Copying Printer Settings
Renaming a printer
Disabling printers with time latches
Managing printing using differential charging
Charging modes available
How duplex discounts are calculated
Using filters and restrictions
Reduce printer jams
Controlling documents on slow Inkjets
Automatically deleting duplicate jobs
Force sensible use
Automatically deny documents based on file extension or name
Control who can print in color (Advanced)
Advanced Setups
Managing printer groups
Suggested best practises for naming printer groups
Cost Adjustments
Popup Authentication
Where Popup authentication is used
How does popup authentication work?
Macs and popup authentication
Configuration
Color Detection
Limitations of Page-Level Color Detection
Watermarking/Job Annotation
Typical Uses
Requirements
Enabling Watermarking
Digital Signatures in Detail (Advanced)
Troubleshooting
Behavior on Server Connection Failures
Failure Mode Settings
Toner Levels (for supported printers)
How toner level information is retrieved?
Printer Quick Reference
Refunding Print Jobs
Enabling End-User Refunds
Managing Refunds
Admin Notifications
User Notifications
Custom Printer Fields
Defining Custom Printer Fields

This section covers some of the more advanced printer management tasks. Advanced printer management can be grouped into the following high-level concepts:

This section addresses these management areas and covers tools available in PaperCut MF to assist administrators.

Adding and Removing/Deleting/Ignoring Printers

On Windows

PaperCut MF tracks all print queues local to the system by default. Local print queues are those that have been set up on the server running PaperCut MF with a local port, such as: a TCP/IP connection to a network printer, an LPR connection, or a printer attached locally via USB or LPT. Standard Windows print queues that are hosted on a different system, or “re-shared”, are not tracked (these queues may be tracked by setting up a secondary print server, see Chapter 15, Configuring Secondary Print Servers and Locally Attached Printers).

New print queues added to the system should show up automatically in PaperCut MF, however in some rare situations the printer may only show up after the first print job has been sent.

Under some situations it may not be desirable to track all printers. Some examples of why an administrator may choose not to monitor a printer include:

  • The printer is a “virtual printer” such as a PDF generator, FAX, or document management program.

  • The administrator may wish to offer free printing on a selected printer and not be concerned with monitoring (silent monitoring with a zero page cost will also achieve this).

  • The printer may not be supported by PaperCut MF and may need to be ignored.

The Print Provider component is responsible for locating and tracking the printers. To instruct it to ignore a printer:

  1. Open the file [app_dir]\providers\print\win\print-provider.conf in a text editor such as Notepad.

  2. Locate the line IgnorePrinters= and enter the full name of the printer on the right-hand-side of the equals line. For example:

                IgnorePrinters=Office Printer
                                

    Note: This is the printer's locally assigned name and not the name of its network share.

    If you have multiple printers to ignore, then separate the each printer name with a comma. For example:

                IgnorePrinters=Office Printer,Copy Room Printer
                                

  3. Restart (stop then start) the PaperCut Print Provider component under StartControl PanelAdministrative ToolsServices

  4. If the printer data is no longer required for reporting purposes, log into PaperCut MF's admin interface and select the Printers section, then click on the printer to be removed and select Delete printer from the Actions list.

  5. Test the changes by printing to the deleted printer and ensuring the printer does not re-register itself in the system. It if does, verify the name assigned under the IgnorePrinters= setting is correct.

On Mac

The list of monitored printers is configured when installing PaperCut MF. To change the list of monitored printers, run the script at /Applications/PaperCut MF/Control Printer Monitoring.command. Please read the script's instructions carefully and ensure that the Print Setup Utility is closed/quit when running this script.

After running the script, print a test document (i.e. using a text editor or printing a web page from Safari). The act of printing for the first time will register the printer with the primary server. Log into PaperCut MF as admin and verify that the printers are now listed under the Printers section. Perform a test print on each printer and verify that the jobs are tracked correctly.

Note

At the technical level, Mac systems use the Common UNIX Printing System (CUPS). PaperCut MF tracks printing by integrating with CUPS. (For system administrators familiar with CUPS, PaperCut MF integrates by wrapping or proxying the CUPS backend). The Control Printer Monitoring.command script simply edits the file /etc/cups/printers.conf and prefixes the DeviceURI with papercut:, enabling monitoring on the selected printer.

System administrators experienced with the terminal may prefer to edit the printers.conf file directly with a text editor. See the section called “On Linux” for more details.

To delete a printer:

  1. Double click on the Control Printer Monitoring.command script.

  2. Choose to disable monitoring on the printer(s) to delete.

  3. If the printer data is no longer required for reporting purposes, log into PaperCut MF's admin interface and select the Printers section, then click on the printer to be removed and select Delete printer from the Actions list.

  4. Test the changes by printing to the deleted printer and ensuring the printer does not re-register itself in the system. It if does, verify that it is not being monitored using Control Printer Monitoring.command.

On Linux

PaperCut MF tracks printing by integrating with the Common UNIX Printing System (CUPS), the printing system on Linux. For a printer to be tracked, CUPS needs to be told to route print jobs through PaperCut MF before printing.

To do this, the printers.conf file must be edited. This can either be done manually, or assisted via the configure-cups script.

To use the script, run the script file at [app-path]/providers/print/linux-*/configure-cups. Please read the script's instructions carefully to enable monitoring on the desired printers.

To edit the file manually:

  1. Open your printers.conf in a text editor such as vim. On most Linux distributions printers.conf is located at /etc/cups/printers.conf.

  2. Prepend papercut: to the DeviceURI of the printers you wish to track. After the modification a DeviceURI line might look like:

        DeviceURI papercut:ipp://1.2.3.4/printers/My_Printer
                                

  3. Restart CUPS in the way appropriate to your distribution. E.g.:

        /etc/init.d/cupsys restart
                                

  4. Perform a test print on each printer. This will cause the printers to be registered. This step is not required with the configure-cups script, because the script registers the printers automatically.

  5. The printers should now be registered. Log into PaperCut MF as admin and verify that the printers are now listed under the Printers section. Verify that the test prints sent previously were tracked correctly.

To delete a printer:

  1. Double click on the configure-cups script (or manually edit printers.conf), and choose to disable monitoring on the printer(s) to delete.

  2. If the printer data is no longer required for reporting purposes, log into PaperCut MF's admin interface and select the Printers section, then click on the printer to be removed and select Delete printer from the Actions list.

  3. Test the changes by printing to the deleted printer and ensuring the printer does not re-register itself in the system. If it does, verify that it is not being monitored using configure-cups.