Burst/Banner pages are generally a single page inserted after a print job. They are most often used to identify the user who printed the job.
Burst pages are often preferred over watermarking where it is not desirable to include any extra information on print jobs, however burst pages use one extra page per print job and add significantly to paper waste.
Windows can produce burst pages that can include several variables; this is outlined in a support article here.
Third party applications are available that can perform watermarking.
Some printer drivers (generally of the high-end / office variety) can also perform watermarking.
On CUPS (the print system on Mac OS X and Linux):
While CUPS can produce burst/banner pages, they are not currently supported by PaperCut.
PaperCut can insert watermarks into PostScript, PCL5, and PCL6 print jobs. PostScript in particular allows us precise control of watermarking, and is available on most modern printers. PaperCutPostScript watermark insertion takes a minimally invasive approach:
The PostScript of the print job is changed as little as possible.
Conflicts between the PaperCut watermark and the original PostScript are resolved by leaving the original PostScript intact.
There may be times when watermarking is enabled in PaperCut and a print job is printed with its own watermark in a way that conflicts with the PaperCut watermark. In this case the PaperCut watermark should not be printed. If the PaperCut watermark is printed instead of a watermark in the document, or if the PaperCut watermark fails to print when the document does not contain a watermark, there may be a conflict between the PostScript driver and PaperCut. If you see this, please email the name of the printer and driver to firstname.lastname@example.org.
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.