Amalgamate printer queues

KB Home   |   Amalgamate printer queues

Main.AmalgamatePrinterQueues History

Hide minor edits - Show changes to output

Added lines 35-36:
* Conversion Filters (forced grayscale, forced duplex) and Watermarking will also transfer the jobs to the server who's name matches the selected alias.
Changed lines 41-42 from:

to:
* Web Print will only print to the aliases server.

* PaperCut's internal printer load balancing will only load balance on the aliases servers queues.

Changed lines 29-30 from:
'''Exceptions:'''
to:
'''Exceptions & Known Issues:'''
Added line 32:
Added line 34:
Changed lines 37-38 from:

to:
* [[https://www.papercut.com/products/ng/manual/ch-printer-mgmt-hwcheck.html|Hardware page count validation]] may not work if multiple queues from different servers point to the same device.


July 02, 2013, at 06:24 AM by 203.12.22.94 -
Added line 30:
July 02, 2013, at 06:24 AM by 203.12.22.94 -
Changed line 14 from:
'''Normal Setup in PaperCut NG:'''
to:
'''Normal Setup in PaperCut:'''
Changed lines 16-22 from:
* Printers are prefixed by the server name (server\printer) so we have separate printers for each queue on each server.

'''Aliased setup in PaperCut NG:'''
* '''Aim:''' Force one server to report itself as the same name as the other server.

* On one of the servers, set the ''[=ServerName=]'' property in the file:
to:
* Printers are prefixed by the server name ([@server\printer@]) so we have separate printers for each queue on each server.

'''Aliased setup in PaperCut:'''
* '''Aim:''' Force one server or servers to report itself as the same name as the other server.

* On one of the servers, set the [@ServerName=@] property in the file:
Changed lines 27-29 from:
* Jobs will now appear under the one printer in PaperCut.  The old queues can be deleted.

to:
* Jobs will now appear under the one printer name in PaperCut.  The old queues can be deleted.

'''Exceptions:'''
The following features may not work as excepted using server aliasing:
* Find-me printing will transfer the jobs to the server who's name matches the selected alias rather than selecting the local server's queue.  This is because queues are selected via a fully qualified queue name.
* Queue error alerts will not identify the server - the server alias name will be required.



Changed lines 21-22 from:
* One one of the servers, set the ''[=ServerName=]'' property in the file:
to:
* On one of the servers, set the ''[=ServerName=]'' property in the file:
Changed line 30 from:
[-keywords: load balance, distributed queues-]
to:
[-keywords: load balance, distributed queues, join-]
Changed lines 3-4 from:
Q: Is there a way in PaperCut to amalgamate printer queues? See we have multiple queues for the same printers. This is partly to split the load between servers and also to act as backup queues.
to:
Q: Is there a way in PaperCut to amalgamate printer queues? We have multiple queues for the same printers. This is partly to split the load between servers and also to act as backup queues.
Changed lines 19-20 from:
* Aim: Force one server to report itself as the same name as the other server.
to:
* '''Aim:''' Force one server to report itself as the same name as the other server.
Changed lines 12-13 from:
to:
* This example assumes both servers run Windows, but the concept can equally be applied to Mac and Linux.
Changed lines 23-24 from:
-->[@c:\Program Files\PaperCut NG\providers\print\win\print-provider.conf@]
to:
-->[@C:\Program Files\PaperCut NG\providers\print\win\print-provider.conf@]
Changed lines 20-21 from:
* One one of the servers, set the ''[@ServerName@]'' property in the file:
to:
* One one of the servers, set the ''[=ServerName=]'' property in the file:
Changed lines 20-21 from:
* One one of the servers, set the ''[@ServerName@'' property in the file:
to:
* One one of the servers, set the ''[@ServerName@]'' property in the file:
Changed lines 3-4 from:
Q: Is there a way in papercut to amalgamate printer queues? See we have mutiple queues for the same printers. This is partly to split the load between servers and also to act as backup queues.
to:
Q: Is there a way in PaperCut to amalgamate printer queues? See we have multiple queues for the same printers. This is partly to split the load between servers and also to act as backup queues.
Changed lines 7-12 from:
We have no easy way to amalgamate print queues in the web interface.  It is something that
have been requested before but does not yet have enough votes to push it
forward onto the TODO list.  There is however the ability to alias at
the server level.  This may helpful in this "backup" queue situation.  I'll explain, by
example, how server aliasing can be useful:
to:
We have no easy way to amalgamate print queues in the web interface.  It is something that have been requested before but does not yet have enough votes to push it forward onto the TODO list.  There is however the ability to alias at the server-level.  This may helpful in this "backup" queue situation.  I'll explain, by example, how server aliasing can be useful:
Added lines 1-35:
(:title Amalgamate printer queues:)

Q: Is there a way in papercut to amalgamate printer queues? See we have mutiple queues for the same printers. This is partly to split the load between servers and also to act as backup queues.

A: This is a complex area!  Organization's with large networks may also wish to consider [[http://www.papercut.biz/products/ng/manual/ch-clustering.html | clustering]].

We have no easy way to amalgamate print queues in the web interface.  It is something that
have been requested before but does not yet have enough votes to push it
forward onto the TODO list.  There is however the ability to alias at
the server level.  This may helpful in this "backup" queue situation.  I'll explain, by
example, how server aliasing can be useful:

'''Setup:'''
* Two print servers (to distribute load and/or act as a backup).
* Both servers have the same set of physical printers installed under matching/identical names.

'''Normal Setup in PaperCut NG:'''
* Each server would report their printers to the central server.
* Printers are prefixed by the server name (server\printer) so we have separate printers for each queue on each server.

'''Aliased setup in PaperCut NG:'''
* Aim: Force one server to report itself as the same name as the other server.

* One one of the servers, set the ''[@ServerName@'' property in the file:

-->[@c:\Program Files\PaperCut NG\providers\print\win\print-provider.conf@]

* Now jobs from this server will list under the same name as the other server.

* Jobs will now appear under the one printer in PaperCut.  The old queues can be deleted.


[-keywords: load balance, distributed queues-]
----
''Catagories:'' [[!Printers]]

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 July 08, 2013, at 04:54 AM
Printable View   |   Article History   |   Edit Article