KB Home | Automatically set up the PaperCut TCP/IP Port
“Help! Iím a sysadmin or PaperCut partner trying to configure all the print queues on a Windows server to use the PaperCut TCP/IP port. Is there a way to script this setup automatically?”
A word about using the PaperCut TCP/IP Port…
PaperCutís Hardware Page Count Validation ensures that PaperCut is able to determine the exact number of pages printed by a device for each job. As a prerequisite for using this feature, a printer must be configured to use the PaperCut TCP/IP Port. Because it can be a bit tedious to go through every single printer on a server weíve put together a couple scripts to automatically configure every printer to use the PaperCut TCP/IP Port (and switch back to using Standard TCP/IP Ports if needed).
Note that this should come with a word of caution. Using the PaperCut TCP/IP Port is not recommended in all scenarios. It’s best used when you need PaperCut to check the printerís page meter to confirm the total number of printed pages. By necessity this feature will slow down printing so that the PaperCut server can track the number of pages printed by each printer. For this reason, we recommend using a Standard TCP/IP Port in most cases. Have a look at this article for the rest of our advice on configuring Windows print queues.
Configure all printers to use the PaperCut TCP/IP Port
Run the following script in an elevated PowerShell window on your print server.
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.