Do I need a dedicated print server?

KB Home   |   Do I need a dedicated print server?

Main.DoINeedAPrintServer History

Hide minor edits - Show changes to output

March 16, 2016, at 11:34 PM by josh - Reworded to fit 16.0's feature of Direct Printing
Changed lines 3-8 from:
Q: Do I need a dedicated print server?  Can I have workstations printing directly to the physical printers?

A: PaperCut monitors printing by "watching"
the jobs pass via a print queue.  It needs to intercept the print jobs between the workstation and the printer so that it can perform analysis and control jobs for various reasons (e.g. delete it if the user doesn't have quota available, or hold it if using a release station).  If workstations print directly to printers then interception is not possible (unless the workstation is set up to host the special monitoring software).

The best solution in a medium to large network is to host your printers and PaperCut on a "print server".  In some cases a print server may be a dedicated server, however on most networks an existing file server or domain server will fill this task.
Hosting printers on a centralized server also has a number of administrative advantages over direct printer connection, including:
to:
PaperCut monitors printing by watching the jobs pass via a print queue. It needs to intercept the print jobs between the workstation and the printer so that it can perform analysis and control jobs for various reasons (e.g. delete it if the user doesn’t have quota available, or hold it if using a release station).

The best solution in a medium to large network is to host your printers and PaperCut on a “print server”. In some cases a print server may be a dedicated server, however on most networks an existing file server or domain server will fill this task.
Hosting printers on a centralized server also has a number of administrative advantages over direct printer connection, including:
Changed lines 14-17 from:
Q: Can I monitor a locally attached USB printers or Direct IP printing?

A: Yes.  PaperCut can monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the
jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut manual.  You can read the [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html | online version here]].
to:
If you're a small business or a distributed site organization with a modest numbers of users that are separated by different offices, then it may make more sense to print directly to a printer rather than have your print jobs travel through a print server. [[https://www.papercut.com/tour/direct-printing/|PaperCut's Direct Printing feature]] may be best for you in this case. This feature gives you a lot more flexibility when choosing whether or not you need a print server at all.
Changed line 19 from:
[-keywords: print server, printer setup, configuration, installation, direct IP connection-]
to:
[-keywords: print server, printer setup, configuration, installation, direct IP connection, BODP, branch office direct printing, direct print-]
Changed lines 18-19 from:
A: Yes.  PaperCut can monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut NG manual.  You can read the [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html | online version here]].
to:
A: Yes.  PaperCut can monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut manual.  You can read the [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html | online version here]].
Changed lines 18-19 from:
A: Yes.  PaperCut NG and PaperCut ChargeBack can monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut NG manual.  You can read the [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html | online version here]].
to:
A: Yes.  PaperCut can monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut NG manual.  You can read the [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html | online version here]].
Changed lines 7-8 from:
The best solution in a medium to large network is to host your printers and PaperCut on a "print server".  In same cases a print server may be a dedicated server, however on most networks an existing file server or domain server will fill this task.  Hosting printers on a centralized server also has a number of administrative advantages over direct printer connection, including:
to:
The best solution in a medium to large network is to host your printers and PaperCut on a "print server".  In some cases a print server may be a dedicated server, however on most networks an existing file server or domain server will fill this task.  Hosting printers on a centralized server also has a number of administrative advantages over direct printer connection, including:
Changed lines 18-19 from:
A: Yes.  PaperCut NG and PaperCut ChargeBack and monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut NG manual.  You can read the [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html | online version here]].
to:
A: Yes.  PaperCut NG and PaperCut ChargeBack can monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut NG manual.  You can read the [[https://www.papercut.com/products/ng/manual/ch-secondary-print.html | online version here]].
Changed line 21 from:
''Categories:'' [[Category.Implementation|+]], [[Category.Deployment|+]]
to:
''Categories:'' [[Category.Implementation|+]]
Changed lines 3-9 from:
Q:Do I need a dedicated print server?  Can I have workstations printing directly to the physical printers?

A: PaperCut monitors printing by "watching" the jobs pass via a print queue.  It needs to intercept the print jobs between the workstation and the printer so that it can analyze the job and control the job for various reasons (e.g. delete it if the user doesn't have quota available, or hold it if using a release station).  If workstations print directly to printers, then interception is not possible (unless the workstation is set up to host the special monitoring software).

The best solution in a medium to large network is to host your printers and the PaperCut application on a "print server".  In same cases a print server may be a dedicated server, however on most networks and existing file server or domain server will fill this task.   Hosting printers on a centralized server also has a number of administrative advantages over direct printer connection.  e.g.

*
Automatic driver deployment and update from the server
to:
Q: Do I need a dedicated print server?  Can I have workstations printing directly to the physical printers?

A: PaperCut monitors printing by "watching" the jobs pass via a print queue.  It needs to intercept the print jobs between the workstation and the printer so that it can perform analysis and control jobs for various reasons (e.g. delete it if the user doesn't have quota available, or hold it if using a release station).  If workstations print directly to printers then interception is not possible (unless the workstation is set up to host the special monitoring software).

The best solution in a medium to large network is to host your printers and PaperCut on a "print server".  In same cases a print server may be a dedicated server, however on most networks an existing file server or domain server will fill this task.  Hosting printers on a centralized server also has a number of administrative advantages over direct printer connection, including:

*
Automatic printer driver deployment and updates from the server
Changed line 13 from:
** use windows security to secure the printer (e.g. a staff only printer)
to:
** use Windows/OS level security to secure the printer (e.g. a staff only printer)
Deleted lines 19-21:

[-keywords: print server, printer setup, configuration, installation, direct IP connection-]

Changed lines 21-22 from:
''Categories:'' [[!Implementation]], [[!Deployment]]
----
to:
''Categories:'' [[Category.Implementation|+]], [[Category.Deployment|+]]
----
[-keywords: print server, printer setup, configuration, installation, direct IP connection-]
Changed lines 9-11 from:
* Automatic driver deployment from the server
to:
* Automatic driver deployment and update from the server
* Centralized access control
* Ability to deploy printers via Active Directory and related tools
Changed lines 14-15 from:
Q: Can I monitor a locally attached USB printer?
to:
Q: Can I monitor a locally attached USB printers or Direct IP printing?
Changed lines 19-20 from:
[-keywords: print server, printer setup, configuration, installation-]
to:
[-keywords: print server, printer setup, configuration, installation, direct IP connection-]
Changed lines 16-19 from:
A: Yes.  PaperCut NG and PaperCut ChargeBack and monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut NG manual.  You can read the [[
http://papercut.biz/products/ng/manual/ch-secondary-print.html | online version here]].

to:
A: Yes.  PaperCut NG and PaperCut ChargeBack and monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut NG manual.  You can read the [[http://papercut.biz/products/ng/manual/ch-secondary-print.html | online version here]].

Changed lines 1-2 from:
(:title Do I need a dedicated print server? :)
to:
(:title Do I need a dedicated print server?:)
Added lines 14-19:
Q: Can I monitor a locally attached USB printer?

A: Yes.  PaperCut NG and PaperCut ChargeBack and monitor locally attached printers.  This works by installing a small monitoring component onto the workstation.  This component intercepts the jobs and reports the printing back to the central PaperCut server (the primary server) using XML Web Services calls.  More information on this architecture and setup is covered in the PaperCut NG manual.  You can read the [[
http://papercut.biz/products/ng/manual/ch-secondary-print.html | online version here]].

Added lines 15-18:

----
''Categories:'' [[!Implementation]], [[!Deployment]]
----
Added lines 1-14:
(:title Do I need a dedicated print server? :)

Q:Do I need a dedicated print server?  Can I have workstations printing directly to the physical printers?

A: PaperCut monitors printing by "watching" the jobs pass via a print queue.  It needs to intercept the print jobs between the workstation and the printer so that it can analyze the job and control the job for various reasons (e.g. delete it if the user doesn't have quota available, or hold it if using a release station).  If workstations print directly to printers, then interception is not possible (unless the workstation is set up to host the special monitoring software).

The best solution in a medium to large network is to host your printers and the PaperCut application on a "print server".  In same cases a print server may be a dedicated server, however on most networks and existing file server or domain server will fill this task.  Hosting printers on a centralized server also has a number of administrative advantages over direct printer connection.  e.g.

* Automatic driver deployment from the server
* Consolidated queue management, which allows you to
** use windows security to secure the printer (e.g. a staff only printer)
** view/manage all print jobs in a queue

[-keywords: print server, printer setup, configuration, installation-]

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 March 16, 2016, at 11:34 PM
Printable View   |   Article History   |   Edit Article