Requirements for job redirection (load balancing or Find-Me printing)
When redirecting a job from one queue to another, the job is rendered by the source queue's driver, and printed by the destination queue's printer. It is therefore vital that the destination printer is compatible with the source driver.
To be compatible, the source (or virtual) print queueA print queue displays information about documents that are waiting to be printed, such as, the printing status, document owner, and number of pages to print. You can use the print queue to view, pause, resume, restart, and cancel print jobs. and the destination print queue must at least use drivers that produce the same print language (e.g. PostScript to PostScript or PCL5 to PCL5). However, due to the differences in the way each manufacturer uses a print language, and even differences between models from the same manufacturer, compatibility can be limited to printers of the same or similar models.
The ideal setup for job redirectionJob redirection is transferring a print job from one print queue to another. Both Find-Me printing and load balancing involve job redirection. is when all target printers are of the same model. If this is not the case, select a driver for the virtual queue that gives the best result across your fleet of destination printers.
A great way to achieve compatibility with a wide range of PostScript printers on Windows is to use PaperCut's Global Print Driver on the virtual (source) print queue.
If instead you want to use a manufacturer driver for the virtual (source) print queue, pick a simple lowest common denominator driver and test it for compatibility with each one of your printers. On the Mac the "Generic Postscript Driver" is a good choice. On Windows select a Color Postscript driver for a mid range popular model. Always carefully test driver compatibility before implementing Find-Me Printing. Take care to address corner cases such advanced graphics options, grayscale mode, paper sizes, duplexing, tray selection, etc. If a common driver cannot be found, you might need to implement multiple virtual queues as discussed in Example 2 above. The following sections provide a simple procedure that you can follow to test printer compatibility.
You might be able to solve compatibility problems with manufacturer drivers using adaptive PDL transforms. See Using vendor driver and adaptive PDL transforms.
Compatibility testing
-
Select your candidate driver to use for your global virtual queue. Use it to set up a print queue on the server, and share the queue.
-
Select the new printer in PaperCut NG and change it to a virtual queue.
-
In the list of compatible queues, select the printers for which you want to test compatibility.
-
In the Hold/Release Queue Settings area, select the Enable hold/release queue check box.
-
Print a test document (e.g. print an email) to the virtual queue from a computer. The job should hold in the virtual queue.
-
Select Printers > Jobs Pending Release.
The Jobs Pending Release page is displayed.
- Release the held job. Select a target queue to test when prompted.
-
Verify that the job printed correctly. Also check the Logs > Application Log tab for any error reports.
-
Repeat the previous 3 steps for all printer types and using different document settings and applications.
Make sure you test a variety of print options targeted at all device types. Problems can manifest in various and subtle ways:
-
Error events logged in PaperCut NG's App Log.
-
Error status on the printer (e.g. a red light and failed print status message).
Or more subtle issues such as:
-
Truncated documents because of different device margin sizes (printable area).
-
Errors only when non-default options options are selected (e.g. finishing options).
-
Issues only on very large documents (due to printer memory limitations).
-
Errors/problems when certain paper sizes are selected.
If issues/problems/errors occur:
-
Disable the Enable Advanced Printing Features option in Windows on the virtual queue on the server. This is accessed by right-clicking the printer, selecting Properties, then the Advanced tab. This change can improve redirection results with some drivers and is required if using the PaperCut Global Print Driver.
-
If you continue to experience compatibility issues, consider setting up multiple virtual queues (for each printer type/class) as discussed in Example 2: Multiple Virtual Queues (Different Printer Types).
Find-Me printing implementation checklist
Setting up Find-Me Printing involves several configuration steps that you must complete before the setup will work. Following is a checklist that you can use to ensure that the main requirements have been carried out. It can also serve as a troubleshooting guide in case of unexpected results.
-
Create a new print queue to function as the virtual queue. Create this print queue using the standard methods or tools provided by the host operating system.
-
Conform that the driver in use by the virtual queue is compatible with the target printers. The output produced by this driver is what is sent to the printer, so it must be compatible.
-
Configure the following settings in the PaperCut NG Admin web interface for the virtual print queue:
-
Queue type—set to This is a virtual queue (jobs will be forwarded to a different queue).
-
Jobs may be forwarded to these queues—configure to reflect the possible or compatible targets for redirection.
-
Select the Enable hold/release queue check box.
-
-
When using Find-Me Printing, Release Stations are recommended because they can automatically select the best nearby printer (based on a match between the virtual queue's configured compatible queues, the Release StationPrint Release Stations place a print job on hold and allow users to release it when required. Often a Release Station is a dedicated PC terminal located next to the printers, however, Release Stations can take other forms such as a web browser based interface. Some common examples where Release Stations can be used include secure printing, approved printing, and authentication. In a secure printing environment jobs are only printed when the user arrives at the print area and confirms his or her identity. This ensures the user is there to collect the job and other users can't "accidentally" collect the document. In some organizations it may be appropriate to hold jobs until they are approved by selected individuals. A good example would be a teacher approving printing on an expensive color printer. Hold/Release queues can be used as a form of authentication in an unauthenticated environment. Users must authenticate prior to releasing their jobs allowing PaperCut NG to confirm their identity.'s configured "releases on" queues and current printer load). If the web based release interface is used instead, the user must select the desired printer from the list of all compatible queues.
-
Configure the releases-on option in the Release Station configuration file to reflect where jobs released at this station can be sent. PaperCut NG compares this list with the Jobs may be forwarded to these queues setting of the virtual queue to find possible target queues. Take care to ensure the name is spelt exactly the same as listed in the printer list.
-
The show-jobs-from-queues option in the Release Station configuration file can optionally be configured to limit the jobs shown in the Release Station to one or more queues. This is useful for situations with multiple virtual queues and Release Stations running in Release Any mode.
-
If there are multiple print servers and the ability to redirect jobs across print servers is required, ensure that the requirements in Cross-Server Job Redirection are met.