Windows Print Queue Configuration

KB Home   |   Windows Print Queue Configuration

Main.PrintQueueSetUpOnWindows History

Show minor edits - Show changes to output

October 11, 2018, at 10:53 PM by Aaron Pouliot - Added note about print queue permissions
Changed lines 52-53 from:
* It’s a good idea to stick with the default permissions and use PaperCut features to manage printer access as found in [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-filters.html|Filters & Restrictions]].
* This is optional, but for physical print queues, you could remove the Manage Documents right for Creator Owner to prevent users from bypassing PaperCut Hold & Release settings. However, don't worry about this for Find-Me print queues which should point to a nul port, anyway.
to:
* It’s a good idea to just stick with the default permissions and use PaperCut features to manage printer access as found in [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-filters.html|Filters & Restrictions]].
* This is optional, but for physical print queues you could remove the Manage Documents right for Creator Owner to prevent users from bypassing PaperCut Hold & Release settings. However, don't worry about this for Find-Me print queues which should point to a nul port anyway.  The caveat to this technique is that we've seen cases where some manufacturer's drivers require the Creator Owner permission.
* Another way to prevent users from resuming held print jobs (without modifying permissions) is to use the PaperCut TCP/IP Port. If a user attempts to resume their held job, it will be automatically deleted by PaperCut.

June 25, 2018, at 05:44 PM by Aaron Pouliot - fixed typo in Advanced Print Features blurb
Changed line 46 from:
* Uncheck [[https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures|Enable Advanced Printing Features]] to prevent the driver from spooling print jobs in proprietary print languages instead of PCL or PostScript. Enabling this setting can cause trouble with detecting attrivutes like page count and color detection, among others.
to:
* Uncheck [[https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures|Enable Advanced Printing Features]] to prevent the driver from spooling print jobs in proprietary print languages instead of PCL or PostScript. Disabling this setting ensures that  PaperCut can accurately read the spool files of the print job, which in turn enables a number of PaperCut features such as precise page count and color detection, grayscale conversion, and watermarking.
May 03, 2018, at 09:14 PM by Aaron Pouliot -
Changed line 45 from:
* We recommend configuring '''Start printing after the last page is spooled''' so the application can finish collecting print job attributes before the job goes to the printer. PaperCut automatically switches the setting to ensure compatibility.
to:
* About the setting'''Start printing after the last page is spooled''', PaperCut will automatically configure [[https://www.papercut.com/kb/Main/ExplanationOfPrintingAfterLastHasBeenSpooled|this setting]] to ensure that the print job is fully analyzed before it goes to the printer.
March 30, 2018, at 07:42 PM by Aaron Pouliot -
Changed line 31 from:
* The PaperCut Port and [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-hwcheck.html|Hardware Page Checks]] go hand in hand, so only use one when you use the other. By necessity, the PaperCut port will slow down printing as the application waits for the last job to finish printing before analyzing the next one.
to:
* The PaperCut TCP/IP Port can also be used, but this is only recommended when doing [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-hwcheck.html|Hardware Page Checks]]. By necessity, the PaperCut port will slow down printing as the application waits for the last job to finish printing before analyzing the next one.  So if Hardware Page Checks are not needed, then stick with using a Standard TCP/IP Port.
March 30, 2018, at 06:20 PM by 207.173.252.92 - fixed grammatical errors
Changed lines 4-5 from:
PaperCut is intended to work ‘out of the box’ in most environments, but to get the most out of the application and ensure all of the features work as intended, we’ve put together this guide to showcase some of the most helpful knowledge and experience about Windows Printing that the we’ve learned over the years.   [[#Summary |Skip to the bottom]] for a quick summary.
to:
PaperCut is intended to work ‘out of the box’ in most environments. However, to make sure you get the most out of the application and ensure all of the features work as intended, we’ve put together this guide to showcase some of the most helpful Windows Printing knowledge and experience that we’ve gathered over the years.   [[#Summary |Skip to the bottom]] for a quick summary.
Changed lines 7-10 from:
Everything about a printer in Windows can be managed in Print Management Console. The fastest way to open this is to open '''Run''' (by pressing '''Windows key + R''') then type '''printmanagement.msc''' and hit '''Enter'''.  Then right-click on the printer you want to manage and choose '''Properties…''' This will open the Printer Properties dialog which will have a lot of options to configure.

Below is a description
of each one of the tabs, as well as our advice for how a printer should be configured.
to:
Print Management Console lets you manage everything about a printer in Windows. The fastest way to open the console is to launch '''Run''' by pressing '''Windows key + R,''' then type '''printmanagement.msc''' and hit '''Enter'''.  Next, right-click on the printer you want to manage and choose '''Properties…''' This will open the Printer Properties dialog with lots of options to configure.

Below is a description of each one
of the tabs, as well as our configuration advice.
Changed line 14 from:
* The '''Location''' field is recognized by PaperCut and can be used to generate reports based on this attribute.  If populated, this field is also used by Mobility Print to tell users where they can find your printer.
to:
* PaperCut can recognize the '''Location''' field which means the attribute is helpful for generating reports.  If populated, this field is also used by Mobility Print to tell users where they can find your printer.
Changed line 19 from:
On this tab you can configure your print server to share out the printer, as well as a few other settings.  Here’s our advice:
to:
On this tab, you can configure your print server to share the printer, as well as a few other settings.
Changed lines 22-24 from:
* Its best practice in environments (with Macs and LPR printing) for the '''Share Name''' to not include spaces.
* Make sure that '''Render print jobs on client computers''' is checked. (This should be the default anyway, but if this has been disabled for whatever reason it can cause additional load on the server and printing issues from Windows 10 clients.)
* The
'''Additional Drivers…''' button can be clicked to add print drivers for legacy 32-bit systems.
to:
* Its best practice in environments with Macs and LPR printing for the '''Share Name''' to not include spaces.
* Make sure to check '''Render print jobs on client computers.''' This should be the default anyway, but if this is disabled for whatever reason, it can cause additional load on the server and printing issues from Windows 10 clients.
* Clicking the '''Additional Drivers…''' button lets you add drivers for legacy 32-bit systems.
Changed lines 28-33 from:
This is where an administrator configure what 'port' the print queue in Windows will use to communicate with the physical printer. This is different from a firewall port and traditionally referred to physical ports on the computer like COM1 and LPT1, but nowadays this is where you go to specify the IP address of your printer.  What sort of port should you use? Well that depends...
* For most printers the port should be a standard TCP/IP Port that points towards the IP address of your printer.
* If you are setting up a Find-Me printer, then [[https://www.papercut.com/kb/Main/SetupNulPortOnWindows|the port should be set to 'nul']]. (That's not a typo.)
* The PaperCut port can also be used instead of a standard TCP/IP port, but is only recommended when [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-hwcheck.html|Hardware Page Checks]] are needed. By necessity the PaperCut port will intentionally slow down printing as the application waits for the last job to finish printing before sending the next one. So only use the PaperCut Port when Hardware Page count is required.
* We don't recommend WSD ports as this obscures the IP address of the printer, making it difficult for PaperCut to communicate with the printer over SNMP to determine toner levels and status.
* Do uncheck '''Enable bidirectional support''' if you are experiencing problems. In our experience, this setting can [[https://www.papercut.com/kb/Main/FixingPrintSpoolerCrashes|cause system instability]]. If this setting is grayed out, then it means it is not applicable with this driver, as is the case with the PaperCut Global PostScript driver.
to:
This tab lets an administrator configure which 'port' the Windows print queue will use to communicate with the physical printer. Printer ports are different from a firewall port and traditionally referred to physical ports on the computer like COM1 and LPT1, but nowadays this is where you go to specify the IP address of your printer.  What sort of port should you use? Well, that depends...
* For most printers, the port should be a standard TCP/IP Port that points to the IP address of your printer.
* If you are setting up a Find-Me printer, then [[https://www.papercut.com/kb/Main/SetupNulPortOnWindows|the port should be set to 'nul']]. No, that's not a typo.
* The PaperCut Port and [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-hwcheck.html|Hardware Page Checks]] go hand in hand, so only use one when you use the other. By necessity, the PaperCut port will slow down printing as the application waits for the last job to finish printing before analyzing the next one.
*
We don't recommend WSD ports as this obscures the IP address of the printer, making it difficult for PaperCut to communicate over SNMP to determine toner levels and status.
* Do uncheck
'''Enable bidirectional support.''' In our experience, this setting can [[https://www.papercut.com/kb/Main/FixingPrintSpoolerCrashes|cause instability]]. If the setting is grayed out, it means it is not applicable to this driver, as is the case with the PaperCut Global PostScript driver.
Changed lines 37-39 from:
In this section, admins can specify advanced settings for the port. Most of the time this is automatically configured,
* Ideally, the selected Protocol should be RAW. This type of connection is faster than legacy LPR connections and is supported by nearly all modern printers.
* It’s recommended to check '''SNMP Status Enabled''' this will allow the Windows OS to query the printer over SNMP to see if it has toner or in in an error state.  If this setting is enabled then the Community Names must exactly match the setting on the printer, or Windows will think that the device is offline.
to:
In this section, admins can specify advanced settings for the port. Most of the time this is automatically configured.
* Ideally, the selected Protocol should be RAW. This type of connection is faster than legacy LPR connections and nearly all modern printers support it.
* It’s recommended to check '''SNMP Status Enabled''' to let Windows query the printer for things like its error status, serial number, and toner levels. The Community Name here and on the printer must match, or Windows will think that the device is offline.
Changed lines 44-47 from:
* The '''Driver''' will show the name of the driver configured in Print Management Console. We strongly recommend PostScript or PCL compatible printers and drivers when available. See our article about [[https://www.papercut.com/kb/Main/SupportedPrinters|Supported Printers]] for more details. 
* We recommend configuring '''Start printing after the last page is spooled''' so the application can finish collecting a print job attributes before the job is sent to the printer. (This will be set automatically by PaperCut to ensure compatibility).
* Uncheck [[https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures|Enable Advanced Printing Features]] to prevent the driver from spooling print jobs in proprietary print languages instead of PCL or PostScript. Enabling this setting can cause trouble with page count and color detection, among others.
* The '''Printing Defaults
''' button leads to a menu for setting default options for the printer (such as the default page size or color preference). This is similar to the '''Printing Preferences''' menu, which changes the same settings, but only for the logged-in user.
to:
* '''Driver''' will show the name of the driver configured in Print Management Console. We strongly recommend PostScript or PCL  drivers when available. See our article about [[https://www.papercut.com/kb/Main/SupportedPrinters|Supported Printers]] for more details. 
* We recommend configuring '''Start printing after the last page is spooled''' so the application can finish collecting print job attributes before the job goes to the printer. PaperCut automatically switches the setting to ensure compatibility.
* Uncheck [[https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures|Enable Advanced Printing Features]] to prevent the driver from spooling print jobs in proprietary print languages instead of PCL or PostScript. Enabling this setting can cause trouble with detecting attrivutes like page count and color detection, among others.
* The
'''Printing Defaults''' button lets you set default options for all users like default page size or color preference. This is similar to the '''Printing Preferences''' menu, which changes the same settings, but only for the logged-in user.
Changed lines 52-53 from:
* It’s a good idea to stick with the default permissions and use the built-in features in PaperCut to manage printer access as found in [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-filters.html|Filters & Restrictions]].
* This is optional, but for normal print queues you could remove the Manage Documents right for Creator Owner to prevent users from bypassing PaperCut Hold & Release settings. (However, this would be a needless step for Find-Me print queues which should point to a nul port anyway.)
to:
* It’s a good idea to stick with the default permissions and use PaperCut features to manage printer access as found in [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-filters.html|Filters & Restrictions]].
* This is optional, but for physical print queues, you could remove the Manage Documents right for Creator Owner to prevent users from bypassing PaperCut Hold & Release settings. However, don't worry about this for Find-Me print queues which should point to a nul port, anyway.
Changed line 57 from:
The settings on this tab are specified by the printer manufacturer and may be unique to the make, model, and driver.  Usually this is where you go to manually specify that a printer has additional trays or a copier is configured with a finishing unit for stapling. It's also possible that certain settings can be configured here that may interfere with PaperCut such as pin authentication or Pull Printing.
to:
These settings may be unique to the make, model, and driver. It's also possible that settings here can interfere with PaperCut features. For example, watch out for things like settings to configure the manufacturer’s implementation of Pull/Print among other queue management features.
Changed lines 63-64 from:
* '''Render print jobs on client computers''' should be checked
* Configure printers to use a
'''Standard TCP/IP port''', only use the '''PaperCut TCP/IP Port''' if Hardware Page Checks are needed, and use the '''nul''' port for Find-Me print queues
to:
* Check '''Render print jobs on client computers'''
* Configure printers to use a '''Standard TCP/IP port'''
* Only
use the '''PaperCut TCP/IP Port''' with the Hardware Page Checks feature
* Use
the '''nul''' port for Find-Me print queues
Changed lines 69-70 from:
* Use Type-3 '''PCL''' or '''PostScript''' drivers when available.
* Disable '''Advanced Print Features '''
to:
* Use Type-3 '''PCL''' or '''PostScript''' drivers when available
* Disable '''Advanced Printing Features '''
Changed line 79 from:
[-Keywords: Forgotten Tasks, hold release, virtual queue, nul, port, sharing, permissions, rights, Windows, initial set up, step, miss, missed, queue resume print, right-click resume, job -]
to:
[-Keywords: Forgotten Tasks, hold release, virtual queue, nul, port, sharing, permissions, rights, Windows, initial set up, step, miss, missed, queue resume print, right-click resume, job -]
March 30, 2018, at 04:07 PM by Aaron Pouliot -
Changed line 2 from:
''“What do all the settings in Printer Properties do, and what’s the best way to configure everything?”''
to:
''“How should I configure my Windows Print Server to get the most out of PaperCut?”''
Changed line 6 from:
!!How to manage the Printer Properties
to:
!!How to manage your printers
March 30, 2018, at 06:50 AM by Aaron Pouliot -
Changed line 20 from:
* Do check '''Share the printer''' so that users can add the printer from your Print Server.
to:
* Do check '''Share this printer''' so that users can add the printer from your Print Server.
March 30, 2018, at 06:49 AM by Aaron Pouliot -
Added lines 13-14:
* Give your printers a good name. We recommend coming up with an easy to read naming convention that includes the site, make, and model of each printer.
* The '''Location''' field is recognized by PaperCut and can be used to generate reports based on this attribute.  If populated, this field is also used by Mobility Print to tell users where they can find your printer.
Deleted line 15:
* The '''Location''' field is recognized by PaperCut and can be used to generate reports based on this attribute.  If populated, this field is also used by Mobility Print to tell users where they can find your printer.
March 30, 2018, at 06:43 AM by Aaron Pouliot -
March 30, 2018, at 06:37 AM by Aaron Pouliot -
Changed lines 63-65 from:
* Use a '''Standard TCP/IP port''' for normal print queues, instead of a WSD port
* Only use the '''PaperCut Port''' when configuring Hardware Page Checks
* Create a
'''nul''' port for Find-Me print queues
to:
* Configure printers to use a '''Standard TCP/IP port''', only use the '''PaperCut TCP/IP Port''' if Hardware Page Checks are needed, and use the '''nul''' port for Find-Me print queues
March 30, 2018, at 06:29 AM by Aaron Pouliot -
Changed line 32 from:
* Do uncheck '''Enable bidirectional support''' if you are experiencing problems. In our experience, this setting can [[https://www.papercut.com/kb/Main/FixingPrintSpoolerCrashes|cause system instability]].
to:
* Do uncheck '''Enable bidirectional support''' if you are experiencing problems. In our experience, this setting can [[https://www.papercut.com/kb/Main/FixingPrintSpoolerCrashes|cause system instability]]. If this setting is grayed out, then it means it is not applicable with this driver, as is the case with the PaperCut Global PostScript driver.
Changed line 56 from:
These settings may be unique to the make, model, and driver. It's also possible that settings here can interfere with PaperCut features. For example, watch out for things like settings to configure the manufacturer’s implementation of Pull/Print among other queue management features.
to:
The settings on this tab are specified by the printer manufacturer and may be unique to the make, model, and driver.  Usually this is where you go to manually specify that a printer has additional trays or a copier is configured with a finishing unit for stapling. It's also possible that certain settings can be configured here that may interfere with PaperCut such as pin authentication or Pull Printing.
Changed line 66 from:
* Uncheck '''Enable bidirectional support'''
to:
* Disable '''Bidirectional Support'''
Changed line 69 from:
* Uncheck '''Enable Advanced Print Features '''
to:
* Disable '''Advanced Print Features '''
March 30, 2018, at 06:22 AM by Aaron Pouliot - Various changes and clarifications per suggestions from Alan Morris
Changed lines 4-5 from:
PaperCut is intended to work ‘out of the box’ in most environments, but to get the most out of the application and ensure all of the features work as intended, we’ve put together this guide to showcase some of the most helpful knowledge and experience about Windows Printing that the we’ve learned over the years.   Skip to the bottom for a quick summary.
to:
PaperCut is intended to work ‘out of the box’ in most environments, but to get the most out of the application and ensure all of the features work as intended, we’ve put together this guide to showcase some of the most helpful knowledge and experience about Windows Printing that the we’ve learned over the years.   [[#Summary |Skip to the bottom]] for a quick summary.
Changed line 12 from:
This is where you can configure the printer’s name and location. There are not too many details on this page that can affect PaperCut though.
to:
This is where you can configure the printer’s name and location.
Changed line 14 from:
* The '''Location''' field will be used by Mobility Print to tell users where they can find your printer.  If this is left blank, PaperCut will substitute this with the print server name instead.
to:
* The '''Location''' field is recognized by PaperCut and can be used to generate reports based on this attribute.  If populated, this field is also used by Mobility Print to tell users where they can find your printer. 
Changed line 27 from:
This is where an administrator configure what 'port' the printer object in Windows will communicate with the physical device. This is different from a firewall port and traditionally referred to physical ports on the computer like COM1 and LPT1, but nowadays this is where you go to specify the IP address of your printer.  What sort of port should you use? Well that depends...
to:
This is where an administrator configure what 'port' the print queue in Windows will use to communicate with the physical printer. This is different from a firewall port and traditionally referred to physical ports on the computer like COM1 and LPT1, but nowadays this is where you go to specify the IP address of your printer.  What sort of port should you use? Well that depends...
Changed lines 31-32 from:
* We don't recommend WSD ports since this Port Monitor may prevent PaperCut from learning when the printer is in error or out of toner.
* Do uncheck '''Enable bidirectional support''' for the smoothest experience.
In our experience, this setting can [[https://www.papercut.com/kb/Main/FixingPrintSpoolerCrashes|cause system instability]].
to:
* We don't recommend WSD ports as this obscures the IP address of the printer, making it difficult for PaperCut to communicate with the printer over SNMP to determine toner levels and status.
* Do uncheck '''Enable bidirectional support''' if you are experiencing problems
. In our experience, this setting can [[https://www.papercut.com/kb/Main/FixingPrintSpoolerCrashes|cause system instability]].
Changed lines 37-38 from:
* Ideally, the selected Protocol should be RAW. (Rarely printers may use [[https://www.papercut.com/kb/Main/LPROnWindows|legacy LPR connections]], although this is not recommended for most scenarios).
* It’s recommended to check '''SNMP Status Enabled'''. PaperCut queries the printer over SNMP to get things like the printer’s error status, serial number, and toner levels. If this setting is enabled then the Community Names must exactly match the setting on the printer, or Windows will think that the device is offline.
to:
* Ideally, the selected Protocol should be RAW. This type of connection is faster than legacy LPR connections and is supported by nearly all modern printers.
* It’s recommended to check '''SNMP Status Enabled''' this will allow the Windows OS to query the printer over SNMP to see if it has toner or in in an error state. If this setting is enabled then the Community Names must exactly match the setting on the printer, or Windows will think that the device is offline.
Changed line 43 from:
* The '''Driver''' will show the name of the driver configured in Print Management Console. We strongly recommend PostScript or PCL compatible printers and drivers when available. See: https://www.papercut.com/kb/Main/SupportedPrinters. 
to:
* The '''Driver''' will show the name of the driver configured in Print Management Console. We strongly recommend PostScript or PCL compatible printers and drivers when available. See our article about [[https://www.papercut.com/kb/Main/SupportedPrinters|Supported Printers]] for more details
Added line 46:
* The '''Printing Defaults''' button leads to a menu for setting default options for the printer (such as the default page size or color preference). This is similar to the '''Printing Preferences''' menu, which changes the same settings, but only for the logged-in user.
Changed lines 51-52 from:
* It’s a good idea to stick with the default permissions and use the built-in features in PaperCut to manage printer access.
* This is optional, but you could remove the Manage Documents right
for Creator Owner to prevent users from bypassing PaperCut Hold & Release settings.
to:
* It’s a good idea to stick with the default permissions and use the built-in features in PaperCut to manage printer access as found in [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-filters.html|Filters & Restrictions]].
* This is optional, but
for normal print queues you could remove the Manage Documents right for Creator Owner to prevent users from bypassing PaperCut Hold & Release settings. (However, this would be a needless step for Find-Me print queues which should point to a nul port anyway.)
Changed lines 59-60 from:
!!Summary
to:

!! [[#Summary]]Summary
March 29, 2018, at 10:52 PM by Aaron Pouliot -
Changed line 66 from:
* Only use Type-3 '''PCL''' or '''PostScript''' drivers
to:
* Use Type-3 '''PCL''' or '''PostScript''' drivers when available.
March 29, 2018, at 10:48 PM by Aaron Pouliot -
Changed lines 59-68 from:
* The Printer Share Name should be shorter than 32 characters
* Make sure that '''Render print jobs on client computers''' is checked
* Use a Standard TCP/IP port for normal print queues, instead of a WSD port
* Only use the PaperCut Port when configuring Hardware Page Checks
* Create a 'nul' port for Find-Me print queues
* Uncheck   '''Enable bidirectional support'''
* The port protocol should be RAW
* Use a Type-3 PCL or PostScript Driver
* Uncheck  '''Enable Advanced Print Features '''
* Leave the default permissions
to:
* The '''Printer Share Name''' should be shorter than 32 characters
* '''Render print jobs on client computers''' should be checked
* Use a '''Standard TCP/IP port''' for normal print queues, instead of a WSD port
* Only use the '''PaperCut Port''' when configuring Hardware Page Checks
* Create a '''nul''' port for Find-Me print queues
* Uncheck '''Enable bidirectional support'''
* The port protocol should be '''RAW'''
* Only use Type-3 '''PCL''' or '''PostScript''' drivers
* Uncheck '''Enable Advanced Print Features '''
* Leave the '''default permissions''' on the Security Tab
March 29, 2018, at 10:44 PM by Aaron Pouliot -
Changed lines 4-5 from:
PaperCut is intended to work ‘out of the box’ in most environments, but to get the most out of the application and ensure all of the features work as intended, we’ve put together this guide to showcase some of the most helpful knowledge and experience about Windows Printing that the we’ve learned over the years.   
to:
PaperCut is intended to work ‘out of the box’ in most environments, but to get the most out of the application and ensure all of the features work as intended, we’ve put together this guide to showcase some of the most helpful knowledge and experience about Windows Printing that the we’ve learned over the years.   Skip to the bottom for a quick summary.
Changed line 45 from:
* Uncheck [[https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures|Enable Advanced Printing Features]] to prevent the driver from spooling print jobs in proprietary print languages instead of PCL or PostScript. Enabling this setting can cause trouble with page count and color detection, among others. https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures
to:
* Uncheck [[https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures|Enable Advanced Printing Features]] to prevent the driver from spooling print jobs in proprietary print languages instead of PCL or PostScript. Enabling this setting can cause trouble with page count and color detection, among others.
Changed line 60 from:
* Make sure that  '''Render print jobs on client computers is checked'''
to:
* Make sure that '''Render print jobs on client computers''' is checked
Added line 62:
* Only use the PaperCut Port when configuring Hardware Page Checks
Changed line 66 from:
* Use a PCL or PostScript Driver
to:
* Use a Type-3 PCL or PostScript Driver
March 29, 2018, at 10:41 PM by Aaron Pouliot - Added Summary section
Added lines 57-67:

!!Summary
* The Printer Share Name should be shorter than 32 characters
* Make sure that  '''Render print jobs on client computers is checked'''
* Use a Standard TCP/IP port for normal print queues, instead of a WSD port
* Create a 'nul' port for Find-Me print queues
* Uncheck  '''Enable bidirectional support'''
* The port protocol should be RAW
* Use a PCL or PostScript Driver
* Uncheck  '''Enable Advanced Print Features '''
* Leave the default permissions
March 29, 2018, at 10:11 PM by Aaron Pouliot - Overhaul of this KB based on current knowledge from Alan Morris. Editing from Artuo Almaguer.
Changed lines 1-38 from:
(:title Print queue set up on Windows - forgotten task!:)

When using release stations or account selection popups, PaperCut pauses jobs on the Windows print queue to hold jobs prior to printing.  It is important, especially in charging environments, that the queue is secured to prevent users from resuming jobs themselves and bypassing PaperCut.

There are two ways a Windows print queue can be secured:
# Restrict the print queue security permissions to prevent users from performing management functions.
# Configure the queue using the PaperCut TCP/IP Port. 


!!Restricting Windows Print Queue Security Permissions

In order to use this method with Windows Server 2012 and 2012R2, Microsoft released a [[https://support.microsoft.com/en-us/kb/3139649|patch for Windows Server 2012 and 2012R2]].  As always, please consult your Microsoft experts as to the suitability of this patch.

To change print queue permissions:

# Log onto the server hosting the printers as an Administrator.
# Open the printer configuration screen: @@Start → Printers@@
# Right-click a printer and select @@Printer Properties@@.
# Select the Security tab.
# Select the @@CREATOR OWNER@@ user and '''un-check''' the @@Manage Documents@@ permission.
%center%Attach:config-print-queue-perms.png
# Press the '''OK''' button.
# Perform these steps for each of the monitored printers.

This task is Step 2 in the installation manual, however is often forgotten: [[https://www.papercut.com/products/ng/manual/ch-installation.html#ch-installation-win-print-queue-conf]]

A tip from one of our customers (Chris), is to use Server Manager, navigate to the Print Management Console and globally set the security permissions by right-clicking the @@Print Server(s)@@ → @@Properties@@ → @@Security@@ and editing the permissions there.


!!Using the PaperCut TCP/IP Port
PaperCut TCP/IP port is mainly used for enabling [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|hardware checking]].

Queues configured to use the PaperCut TCP/IP Port (in PaperCut version 14.1 or higher) will automatically ensure that  manually resumed jobs will not be printed.  You will already be using a PaperCut TCP/IP Port if you are using hardware page count validation.  You can see which port is being used in the @@Ports@@ tab under @@Printer Properties@@.

''Note: If you're using Virtual queues on your server which are redirecting to other target queues, the recommendation is to use LPT or 'nul' ports for the Virtual queues - since no jobs should be actually printing from that queue. In that case, since the virtual queues can't print, you won't need to use the PaperCut TCP/IP ports on the target queues, unless you're using them for hardware checking.''

If you are not currently using PaperCut TCP/IP ports, you may do so by following the [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win|hardware checking setup]] instructions.

to:
(:title Windows Print Queue Configuration:)
''“What do all the settings in Printer Properties do, and what’s the best way to configure everything?”''
Changed lines 4-12 from:
!!Sent to printer - Jobs stuck in queue
In some rare circumstances it's been observed that when changing permissions on print queues AND changing driver isolation modes, print jobs may remain in the print queue with the status of "Sent to printer". Microsoft  released a [[https://support.microsoft.com/en-us/kb/2906850|patch for Windows 7 and Windows Server 2008R2]]. This may be relevant to your environment if you have this issue. As always, please consult your Microsoft experts as to the suitability of this patch.

In early 2014, PaperCut Technical Support also found that the HP Universal Driver had similar behaviour and required the "Enable bidirectional support" on the Ports tab to be unticked.

!!Access Denied errors
If you receive an "@@Access denied@@" error when changing both the @@CREATOR OWNER@@ permissions and the @@Print Driver Isolation@@ settings you may need to turn off the @@Render print jobs on client computers@@ found under the Sharing Tab for that printer.

%center%Attach:config-print-queue-rendering.png
to:
PaperCut is intended to work ‘out of the box’ in most environments, but to get the most out of the application and ensure all of the features work as intended, we’ve put together this guide to showcase some of the most helpful knowledge and experience about Windows Printing that the we’ve learned over the years.   

!!How to manage the Printer Properties
Everything about a printer in Windows can be managed in Print Management Console. The fastest way to open this is to open '''Run''' (by pressing '''Windows key + R''') then type '''printmanagement.msc''' and hit '''Enter'''.  Then right-click on the printer you want to manage and choose '''Properties…''' This will open the Printer Properties dialog which will have a lot of options to configure.

Below is a description of each one of the tabs, as well as our advice for how a printer should be configured.

!!General Tab
This is where you can configure the printer’s name and location. There are not too many details on this page that can affect PaperCut though.
* The button '''Print Test Page''' is your friend.  Use this button to quickly and easily make sure you can send a print job from your server to your device.
* The '''Location''' field will be used by Mobility Print to tell users where they can find your printer.  If this is left blank, PaperCut will substitute this with the print server name instead.
Attach:General_Tab.png

!!Sharing Tab
On this tab you can configure your print server to share out the printer, as well as a few other settings.  Here’s our advice:
* Do check '''Share the printer''' so that users can add the printer from your Print Server.
* PaperCut will work with long printer names, but [[https://support.microsoft.com/en-us/help/240082/info-working-with-long-printer-namesh|according to Microsoft]] the Printer Share Name  hould be shorter than 32 characters.
* It’s best practice in environments (with Macs and LPR printing) for the '''Share Name''' to not include spaces.
* Make sure that '''Render print jobs on client computers''' is checked. (This should be the default anyway, but if this has been disabled for whatever reason it can cause additional load on the server and printing issues from Windows 10 clients.)
* The '''Additional Drivers…''' button can be clicked to add print drivers for legacy 32-bit systems.
Attach:Sharing_Tab.png

!!Ports Tab
This is where an administrator configure what 'port' the printer object in Windows will communicate with the physical device. This is different from a firewall port and traditionally referred to physical ports on the computer like COM1 and LPT1, but nowadays this is where you go to specify the IP address of your printer.  What sort of port should you use? Well that depends...
* For most printers the port should be a standard TCP/IP Port that points towards the IP address of your printer.
* If you are setting up a Find-Me printer, then [[https://www.papercut.com/kb/Main/SetupNulPortOnWindows|the port should be set to 'nul']]. (That's not a typo.)
* The PaperCut port can also be used instead of a standard TCP/IP port, but is only recommended when [[https://www.papercut.com/products/ng/manual/applicationserver/topics/printer-hwcheck.html|Hardware Page Checks]] are needed. By necessity the PaperCut port will intentionally slow down printing as the application waits for the last job to finish printing before sending the next one. So only use the PaperCut Port when Hardware Page count is required.
* We don't recommend WSD ports since this Port Monitor may prevent PaperCut from learning when the printer is in error or out of toner.
* Do uncheck '''Enable bidirectional support''' for the smoothest experience. In our experience, this setting can [[https://www.papercut.com/kb/Main/FixingPrintSpoolerCrashes|cause system instability]].
Attach:Ports_Tab.png

!!Ports Tab > Configure Port…
In this section, admins can specify advanced settings for the port. Most of the time this is automatically configured,
* Ideally, the selected Protocol should be RAW. (Rarely printers may use [[https://www.papercut.com/kb/Main/LPROnWindows|legacy LPR connections]], although this is not recommended for most scenarios).
* It’s recommended to check '''SNMP Status Enabled'''. PaperCut queries the printer over SNMP to get things like the printer’s error status, serial number, and toner levels. If this setting is enabled then the Community Names must exactly match the setting on the printer, or Windows will think that the device is offline.
Attach:Configure_Port.png

!!Advanced Tab
In this section, administrators can specify the hours a printer is available, what driver a print queue should use to communicate with the physical printer, as well as configure how documents spool.  
* The '''Driver''' will show the name of the driver configured in Print Management Console. We strongly recommend PostScript or PCL compatible printers and drivers when available. See: https://www.papercut.com/kb/Main/SupportedPrinters. 
* We recommend configuring '''Start printing after the last page is spooled''' so the application can finish collecting a print job attributes before the job is sent to the printer. (This will be set automatically by PaperCut to ensure compatibility).
* Uncheck [[https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures|Enable Advanced Printing Features]] to prevent the driver from spooling print jobs in proprietary print languages instead of PCL or PostScript. Enabling this setting can cause trouble with page count and color detection, among others. https://www.papercut.com/kb/Main/EnableAdvancedPrintingFeatures
Attach:Advanced_Tab.png

!!Security Tab
Here is where permissions are set to control which users or groups of users have rights to manage the print queue or documents.
* It’s a good idea to stick with the default permissions and use the built-in features in PaperCut to manage printer access.
* This is optional, but you could remove the Manage Documents right for Creator Owner to prevent users from bypassing PaperCut Hold & Release settings. https://www.papercut.com/kb/Main/PrintQueueSetUpOnWindows
Attach:Security_Tab.png

!!Device Settings Tab
These settings may be unique to the make, model, and driver. It's also possible that settings here can interfere with PaperCut features. For example, watch out for things like settings to configure the manufacturer’s implementation of Pull/Print among other queue management features.
Attach:Device_Settings_Tab.png

!!Still have questions?
Let us know! We’re definitely happy to chat about what's going on under the hood. Feel free to leave a comment below if you have any questions at all or visit our [[https://support.papercut.com/|Support Portal]] for further assistance.

June 03, 2016, at 11:53 PM by Alan Morris - linked to Microsoft patch for 2012, 2012R2 Creator owner fix. Removed references to previous failure
Deleted line 5:
# Configure the queue using the PaperCut TCP/IP Port.  (Useful for Windows 8.1 and Windows 2012 R2)
Changed lines 7-17 from:

!!Using the PaperCut TCP/IP Port (Useful for Windows 8.1 and Windows 2012 R2)

PaperCut TCP/IP port is mainly used for enabling [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|hardware checking]]. It can also be used to secure the print queue on Windows 8.1 and Windows 2012 R2 Server where it is not possible to use method #2 above.

Queues configured to use the PaperCut TCP/IP Port (in PaperCut version 14.1 or higher) will automatically ensure that  manually resumed jobs will not be printed.  You will already be using a PaperCut TCP/IP Port if you are using hardware page count validation.  You can see which port is being used in the @@Ports@@ tab under @@Printer Properties@@.

''Note: If you're using Virtual queues on your server which are redirecting to other target queues, the recommendation is to use LPT or 'nul' ports for the Virtual queues - since no jobs should be actually printing from that queue. In that case, since the virtual queues can't print, you won't need to use the PaperCut TCP/IP ports on the target queues, unless you're using them for hardware checking.''

If you are not currently using PaperCut TCP/IP ports, you may do so by following the [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win|hardware checking setup]] instructions.

to:
# Configure the queue using the PaperCut TCP/IP Port. 

Changed lines 12-13 from:
This method works for most versions of Windows.  However, it may interfere with printing on Windows 8.1 and Windows 2012 R2 Server.  On these systems you may secure printing by using '''PaperCut TCP/IP ports''' (PaperCut version 14.1 or higher).
to:
In order to use this method with Windows Server 2012 and 2012R2, Microsoft released a [[https://support.microsoft.com/en-us/kb/3139649|patch for Windows Server 2012 and 2012R2]].  As always, please consult your Microsoft experts as to the suitability of this patch.
Changed lines 27-38 from:
A Windows 2008 server tip from one of our customers (Chris), is to use Server Manager, navigate to the Print Management Console and globally set the security permissions by right-clicking the @@Print Server(s)@@ → @@Properties@@ → @@Security@@ and editing the permissions there
to:
A tip from one of our customers (Chris), is to use Server Manager, navigate to the Print Management Console and globally set the security permissions by right-clicking the @@Print Server(s)@@ → @@Properties@@ → @@Security@@ and editing the permissions there.


!!Using the PaperCut TCP/IP Port
PaperCut TCP/IP port is mainly used for enabling [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|hardware checking]].

Queues configured to use the PaperCut TCP/IP Port (in PaperCut version 14.1 or higher) will automatically ensure that  manually resumed jobs will not be printed.  You will already be using a PaperCut TCP/IP Port if you are using hardware page count validation.  You can see which port is being used in the @@Ports@@ tab under @@Printer Properties@@.

''Note: If you're using Virtual queues on your server which are redirecting to other target queues, the recommendation is to use LPT or 'nul' ports for the Virtual queues - since no jobs should be actually printing from that queue. In that case, since the virtual queues can't print, you won't need to use the PaperCut TCP/IP ports on the target queues, unless you're using them for hardware checking.''

If you are not currently using PaperCut TCP/IP ports, you may do so by following the [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win|hardware checking setup]] instructions.

Changed line 41 from:
In some rare circumstances it's been observed that when changing permissions on print queues AND changing driver isolation modes, print jobs may remain in the print queue with the status of "Sent to printer". Microsoft have released a [[https://support.microsoft.com/en-us/kb/2906850|patch for Windows 7 and Windows Server 2008R2]]. This may be relevant to your environment if you have this issue. As always, please consult your Microsoft experts as to the suitability of this patch.
to:
In some rare circumstances it's been observed that when changing permissions on print queues AND changing driver isolation modes, print jobs may remain in the print queue with the status of "Sent to printer". Microsoft released a [[https://support.microsoft.com/en-us/kb/2906850|patch for Windows 7 and Windows Server 2008R2]]. This may be relevant to your environment if you have this issue. As always, please consult your Microsoft experts as to the suitability of this patch.
October 21, 2015, at 06:34 PM by timg - Updated with Virtual Queue / PaperCut Port Clarification
Changed lines 11-12 from:
PaperCut TCP/IP port is mainly used for enabling [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|hardware checking]]. It can also be used to secure the print queue on Windows 8.1 and Windows 2012 R2 Server where it is not possible to use method #2.
to:
PaperCut TCP/IP port is mainly used for enabling [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|hardware checking]]. It can also be used to secure the print queue on Windows 8.1 and Windows 2012 R2 Server where it is not possible to use method #2 above.
Changed lines 15-17 from:
If you are not currently using PaperCut TCP/IP ports, you may do so by following [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win|the manual]].
to:
''Note: If you're using Virtual queues on your server which are redirecting to other target queues, the recommendation is to use LPT or 'nul' ports for the Virtual queues (or the regular TCP/IP port if the driver needs to 'talk' to an actual printer) - since no jobs should be actually printing from that queue. Only use the PaperCut TCP/IP Port on the target queues.''

If you are not currently using PaperCut TCP/IP ports, you may do so by following the [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win|hardware checking setup]] instructions
.
Changed line 9 from:
!!Using the PaperCut TCP/IP Port
to:
!!Using the PaperCut TCP/IP Port (Useful for Windows 8.1 and Windows 2012 R2)
Changed line 11 from:
PaperCut TCP/IP port is mainly used for enabling [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|hardware checking]]. It can also be used to secure the print queue on Windows 8.1 and Windows 2012 R2 Server where it is not possible to restrict the print queue security permission.
to:
PaperCut TCP/IP port is mainly used for enabling [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|hardware checking]]. It can also be used to secure the print queue on Windows 8.1 and Windows 2012 R2 Server where it is not possible to use method #2.
Changed line 6 from:
# Configure the queue using the PaperCut TCP/IP Port. 
to:
# Configure the queue using the PaperCut TCP/IP Port.  (Useful for Windows 8.1 and Windows 2012 R2)
Added lines 10-11:

PaperCut TCP/IP port is mainly used for enabling [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|hardware checking]]. It can also be used to secure the print queue on Windows 8.1 and Windows 2012 R2 Server where it is not possible to restrict the print queue security permission.
Changed lines 13-14 from:
If you are not currently using PaperCut TCP/IP ports, you may do so by following :[[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win|this manual]].
to:
If you are not currently using PaperCut TCP/IP ports, you may do so by following [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win|this manual]].
May 25, 2015, at 05:46 AM by 203.222.91.204 -
Changed lines 13-14 from:
If you are not currently using PaperCut TCP/IP ports, you may do so by following the manual:[[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win]] 
to:
If you are not currently using PaperCut TCP/IP ports, you may do so by following :[[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win|this manual]].
Changed lines 17-18 from:
This method works for most versions of Windows.  However it may interfere with printing on Windows 8.1 and Windows 2012 Server SP2.  On these systems you may secure printing by using '''PaperCut TCP/IP ports''' (PaperCut version 14.1 or higher).
to:
This method works for most versions of Windows.  However, it may interfere with printing on Windows 8.1 and Windows 2012 Server SP2.  On these systems you may secure printing by using '''PaperCut TCP/IP ports''' (PaperCut version 14.1 or higher).
Changed lines 17-18 from:
This method works for most versions of Windows.  However it may interfere with printing on Windows 8.1 and Windows 2012 Server SP2.  On these systems you may secure printing by using PaperCut TCP/IP ports (PaperCut version 14.1 or higher).
to:
This method works for most versions of Windows.  However it may interfere with printing on Windows 8.1 and Windows 2012 Server SP2.  On these systems you may secure printing by using '''PaperCut TCP/IP ports''' (PaperCut version 14.1 or higher).
March 27, 2014, at 05:29 AM by geoff - Rework for 14.1: use of PaperCut TCP/IP port vs. changing permissions
Changed lines 3-11 from:
When using release stations or account selection popups it is possible for users to pause/resume documents in the queue
without steps being taken to prevent this.

On '''Windows 8.1''' and '''2012 Server'''
, there is no support for configuring the printer to prevent this, so instead please use the PaperCut TCP/IP Port in PaperCut version 14.1 or higher to ensure that manually resumed jobs will not be printed. The PaperCut TCP/IP Port may already be used if you are doing SNMP Hardware Checking in which case no other steps are necessary. Otherwise the PaperCut TCP/IP Port may be set up by following the manual:
[[https://www
.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win]]

On earlier versions of Windows, the following steps can be taken to secure the queue.
This allows PaperCut to have full control of documents without interference from users. To
do this:
to:
When using release stations or account selection popups, PaperCut pauses jobs on the Windows print queue to hold jobs prior to printing.  It is important, especially in charging environments, that the queue is secured to prevent users from resuming jobs themselves and bypassing PaperCut.

There are two ways a Windows print queue can be secured:
# Configure the queue using the PaperCut TCP/IP Port
.  
# Restrict the print queue security permissions to prevent users from performing management functions.

!!Using the PaperCut TCP/IP Port

Queues configured to use the PaperCut
TCP/IP Port (in PaperCut version 14.1 or higher) will automatically ensure that  manually resumed jobs will not be printed.  You will already be using a PaperCut TCP/IP Port if you are using hardware page count validation.  You can see which port is being used in the Ports tab under @@Printer Properties@@.

If you are not currently using PaperCut TCP/IP ports, you may
do so by following the manual:[[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win]] 

!!Restricting Windows Print Queue Security Permissions

This method works for most versions of Windows.  However it may interfere with printing on Windows 8.1 and Windows 2012 Server SP2.  On these systems you may secure printing by using PaperCut TCP/IP ports (PaperCut version 14.1 or higher).

To change print queue permissions
:
Changed line 33 from:
to:
 
March 26, 2014, at 11:44 PM by 203.12.22.94 -
Changed line 6 from:
On '''Windows 8.1''' and '''2012 Server''', it does not support configuring the printer to prevent this, so instead please use the PaperCut TCP/IP Port in PaperCut version 14.1 or higher to ensure that manually resumed jobs will not be printed. The PaperCut TCP/IP Port may already be used if you are doing SNMP Hardware Checking in which case no other steps are necessary. Otherwise the PaperCut TCP/IP Port may be set up by following the manual:
to:
On '''Windows 8.1''' and '''2012 Server''', there is no support for configuring the printer to prevent this, so instead please use the PaperCut TCP/IP Port in PaperCut version 14.1 or higher to ensure that manually resumed jobs will not be printed. The PaperCut TCP/IP Port may already be used if you are doing SNMP Hardware Checking in which case no other steps are necessary. Otherwise the PaperCut TCP/IP Port may be set up by following the manual:
March 26, 2014, at 11:40 PM by 203.12.22.94 -
Changed lines 7-8 from:
[[https://www.papercut.com/products/ng/manual/ch-printer-mgmt.html#ch-printer-mgmt-hwcheck-conf-win]]
to:
[[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html#ch-printer-mgmt-hwcheck-conf-win]]
March 26, 2014, at 11:33 PM by 203.12.22.94 -
Changed lines 6-7 from:
On '''Windows 8.1''' and '''2012 Server''', it does not support configuring the printer to prevent this, so instead please use the PaperCut TCP/IP Port in PaperCut version 14.1 or higher to ensure that manually resumed jobs will not be printed. The PaperCut TCP/IP Port may already be used if you are doing SNMP Hardware Checking in which case no other steps are necessary.
to:
On '''Windows 8.1''' and '''2012 Server''', it does not support configuring the printer to prevent this, so instead please use the PaperCut TCP/IP Port in PaperCut version 14.1 or higher to ensure that manually resumed jobs will not be printed. The PaperCut TCP/IP Port may already be used if you are doing SNMP Hardware Checking in which case no other steps are necessary. Otherwise the PaperCut TCP/IP Port may be set up by following the manual:
[[https://www.papercut.com/products/ng/manual/ch-printer-mgmt.html#ch-printer-mgmt-hwcheck-conf-win]]

March 26, 2014, at 11:25 PM by 203.12.22.94 -
Changed lines 5-7 from:
On Windows 8.1 and 2012 Server, it does not support configuring the printer to prevent this, so instead please use the PaperCut TCP/IP Port in PaperCut version 14.1 or higher to ensure that manually resumed jobs will not be printed.
to:

On '''Windows 8.1''' and '''2012 Server''', it does not support configuring the printer to prevent this, so instead please use the PaperCut TCP/IP Port in PaperCut version 14.1 or higher to ensure that manually resumed jobs will not be printed. The PaperCut TCP/IP Port may already be used if you are doing SNMP Hardware Checking in which case no other steps are necessary.
Changed line 5 from:
On Windows 8.1 and 2012 Server and higher, with PaperCut version 14.1 or higher, it is necessary to use the PaperCut TCP/IP Port to ensure that manually resumed jobs will not be printed.
to:
On Windows 8.1 and 2012 Server, it does not support configuring the printer to prevent this, so instead please use the PaperCut TCP/IP Port in PaperCut version 14.1 or higher to ensure that manually resumed jobs will not be printed.
March 26, 2014, at 04:09 AM by tim - support in 14.1 for PaperCut Port Monitor to help Windows 8.1/2012
Changed lines 3-4 from:
When using release stations or account selection pop-ups it is recommended to secure the print queue so that users do not have permission to pause/resume documents in the queue. This allows PaperCut to have full control of documents without interference from users. To do this:
to:
When using release stations or account selection popups it is possible for users to pause/resume documents in the queue
without steps being taken
to prevent this.
On Windows 8
.1 and 2012 Server and higher, with PaperCut version 14.1 or higher, it is necessary to use the PaperCut TCP/IP Port to ensure that manually resumed jobs will not be printed.
On earlier versions of Windows, the following steps can be taken to secure the queue.

This allows PaperCut to have full control of documents without interference from users. To do this:
Added lines 21-22:
In early 2014, PaperCut Technical Support also found that the HP Universal Driver had similar behaviour and required the "Enable bidirectional support" on the Ports tab to be unticked.
Added lines 18-20:
!!Sent to printer - Jobs stuck in queue
In some rare circumstances it's been observed that when changing permissions on print queues AND changing driver isolation modes, print jobs may remain in the print queue with the status of "Sent to printer". Microsoft have released a [[http://support.microsoft.com/default.aspx?scid=kb;EN-US;2906850|patch for Windows 7 and Windows Server 2008r2]]. This may be relevant to your environment if you have this issue. As always, please consult your Microsoft experts as to the suitability of this patch.

Changed line 9 from:
# Select the @@CREATOR OWNER@@ user and '''un-check''' the @@Manage Documents@@ permission.\\\
to:
# Select the @@CREATOR OWNER@@ user and '''un-check''' the @@Manage Documents@@ permission.
Changed lines 19-20 from:
If you receive an "Access denied" error when changing both the CREATOR OWNER permissions and the Print Driver Isolation settings you may need to turn off the Render print jobs on client computers found under the Sharing Tab for that printer.
to:
If you receive an "@@Access denied@@" error when changing both the @@CREATOR OWNER@@ permissions and the @@Print Driver Isolation@@ settings you may need to turn off the @@Render print jobs on client computers@@ found under the Sharing Tab for that printer.
May 30, 2013, at 12:33 AM by Jason - Added note about Access Denied errors.
Added lines 17-21:

!!Access Denied errors
If you receive an "Access denied" error when changing both the CREATOR OWNER permissions and the Print Driver Isolation settings you may need to turn off the Render print jobs on client computers found under the Sharing Tab for that printer.

Attach:config-print-queue-rendering.png
Changed line 9 from:
# Select the @@CREATOR OWNER@@ user and un-check the @@Manage Documents@@ permission.\\\
to:
# Select the @@CREATOR OWNER@@ user and '''un-check''' the @@Manage Documents@@ permission.\\\
September 26, 2012, at 03:09 PM by RossM - changed 20008 to 2008
Changed line 16 from:
A Windows 20008 server tip from one of our customers (Chris), is to use Server Manager, navigate to the Print Management Console and globally set the security permissions by right-clicking the @@Print Server(s)@@ → @@Properties@@ → @@Security@@ and editing the permissions there
to:
A Windows 2008 server tip from one of our customers (Chris), is to use Server Manager, navigate to the Print Management Console and globally set the security permissions by right-clicking the @@Print Server(s)@@ → @@Properties@@ → @@Security@@ and editing the permissions there
Changed line 16 from:
A Windows 20008 server tip from one of our customers Chris, is to use Server Manager, navigate to the Print Management Console and globally set the security permissions by right-clicking the @@Print Server(s)@@ → @@Properties@@ → @@Security@@ and editing the permissions there
to:
A Windows 20008 server tip from one of our customers (Chris), is to use Server Manager, navigate to the Print Management Console and globally set the security permissions by right-clicking the @@Print Server(s)@@ → @@Properties@@ → @@Security@@ and editing the permissions there
Changed line 16 from:
A tip from one of our customers Chris, is when using Windows 2008 Server is to use the Print Management MMC Snapin and globally set the security permissions by right-clicking the Print Server(s) -> Properties -> Security and editing the permissions there.
to:
A tip from one of our customers Chris, is when using Windows 2008 Server is to use the Server Manager, navigate to the Print Management Console and globally set the security permissions by right-clicking the @@Print Server(s)@@ → @@Properties@@ → @@Security@@ and editing the permissions there
Added lines 15-16:

A tip from one of our customers Chris, is when using Windows 2008 Server is to use the Print Management MMC Snapin and globally set the security permissions by right-clicking the Print Server(s) -> Properties -> Security and editing the permissions there.
Changed line 20 from:
[-Keywords: hold / release, rights, initial set up, step, miss, missed, queue resume print, right-click resume, job -]
to:
[-Keywords: hold / release, rights, initial set up, step, miss, missed, queue resume print, right-click resume, job -]
March 16, 2012, at 03:41 AM by ian - Revert to before "net share" addition.
Deleted lines 14-31:

!! List permissions on a print queue

Checking the list of permissions on many print queues can be a time consuming task. You can use the @@net share@@ command to check permissions quickly. For example:

[@C:\Users\administrator>net share "Building A - Back Foyer Printer"
Share name        Building A - Back Foyer Printer
Path              192.168.1.10
Remark            Building A - Back Foyer Printer
Maximum users    No limit
Users
Caching          Manual caching of documents
Permission        print-server\administrator, FULL
                  Everyone, FULL
                  BUILTIN\Administrators, FULL

The command completed successfully.@]

Added lines 15-32:

!! List permissions on a print queue

Checking the list of permissions on many print queues can be a time consuming task. You can use the @@net share@@ command to check permissions quickly. For example:

[@C:\Users\administrator>net share "Building A - Back Foyer Printer"
Share name        Building A - Back Foyer Printer
Path              192.168.1.10
Remark            Building A - Back Foyer Printer
Maximum users    No limit
Users
Caching          Manual caching of documents
Permission        print-server\administrator, FULL
                  Everyone, FULL
                  BUILTIN\Administrators, FULL

The command completed successfully.@]

Changed line 18 from:
[-Keywords: hold / release, rights, initial set up, step, miss, missed, queue resume print -]
to:
[-Keywords: hold / release, rights, initial set up, step, miss, missed, queue resume print, right-click resume, job -]
Changed line 18 from:
[-Keywords: hold / release, rights, initial set up, step, miss, missed-]
to:
[-Keywords: hold / release, rights, initial set up, step, miss, missed, queue resume print -]
Changed line 14 from:
This task is Step 2 in the installation manual, however is often forgotten: [[https://www.papercut.com/products/ng/manual/ch-installation.html#id471279]]
to:
This task is Step 2 in the installation manual, however is often forgotten: [[https://www.papercut.com/products/ng/manual/ch-installation.html#ch-installation-win-print-queue-conf]]
February 24, 2010, at 02:47 AM by 202.129.124.120 -
Changed line 18 from:
[-Keywords: hold / release, rights, initial set up, step, miss-]
to:
[-Keywords: hold / release, rights, initial set up, step, miss, missed-]
Changed lines 1-4 from:
(:title Print queue set up on Windows - forgotten task! :)

When
using release stations or account selection popups it is recommended to secure the print queue so that users do not have permission to pause/resume documents in the queue. This allows PaperCut to have full control of documents without interference from users. To do this:
to:
(:title Print queue set up on Windows - forgotten task!:)

When
using release stations or account selection pop-ups it is recommended to secure the print queue so that users do not have permission to pause/resume documents in the queue. This allows PaperCut to have full control of documents without interference from users. To do this:
Changed line 9 from:
# Select the @@CREATOR OWNER@@ user and uncheck the @@Manage Documents@@ permission.\\\
to:
# Select the @@CREATOR OWNER@@ user and un-check the @@Manage Documents@@ permission.\\\
Changed line 14 from:
This task is Step 2 in the installation manual, however is often forgotton: [[https://www.papercut.com/products/ng/manual/ch-installation.html#id471279]]
to:
This task is Step 2 in the installation manual, however is often forgotten: [[https://www.papercut.com/products/ng/manual/ch-installation.html#id471279]]
Changed lines 16-18 from:
[-Keywords: hold / release, rights, initial set up, step, miss -]
to:
''Categories:'' [[Category.Administration|+]], [[Category.Security|+]]
----
[-Keywords: hold / release
, rights, initial set up, step, miss-]
Changed line 14 from:
It is also given in this section of the manual: [[https://www.papercut.com/products/ng/manual/ch-installation.html#id471279]]
to:
This task is Step 2 in the installation manual, however is often forgotton: [[https://www.papercut.com/products/ng/manual/ch-installation.html#id471279]]
Changed line 16 from:
[-Keywords: hold / release, rights, initial set up -]
to:
[-Keywords: hold / release, rights, initial set up, step, miss -]
December 10, 2008, at 11:33 PM by 218.214.136.161 -
Added lines 13-14:

It is also given in this section of the manual: [[https://www.papercut.com/products/ng/manual/ch-installation.html#id471279]]

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on October 11, 2018, at 10:53 PM
Printable View   |   Article History   |   Edit Article