Scaling Find Me Printing

KB Home   |   Scaling Find Me Printing

Main.ScalingFindMePrinting History

Hide minor edits - Show changes to output

July 05, 2018, at 06:25 PM by Aaron Pouliot - Added category FindMePrinting
Changed line 68 from:
''Categories:'' [[Category.Administration|+]], [[Category.Configuration|+]]
to:
''Categories:'' [[Category.FindMePrinting|+]]
Changed line 60 from:
!!!Now i've planned, how do I deploy my virtual queues?
to:
!!!Now I've planned, how do I deploy my virtual queues?
June 04, 2015, at 11:41 PM by Alec - Changed to reference Global Print driver.
Changed lines 37-38 from:
If all of the manufacturer's support Postscript on their devices then a “lowest common denominator” driver like a HP Postscript or a Windows “Generic Postscript Driver” will often do the trick for basic printing. You should test common areas across all devices to assure that page boundaries (printable area differences) and finishing options such as duplex combinations work as expected. Users can be instructed to use the direct queues on the server if the printers advanced features are required(e.g. stapling, folding, color profiles, etc).
to:
If all of the printers support Postscript then the PaperCut [[https://www.papercut.com/tour/global-print-driver/ | Global Print driver]] for Windows (LInux and Mac users can use the CUPS Universal Postscript driver) will do the trick for printing. You should test common areas across all devices to assure that page boundaries (printable area differences) and finishing options such as duplex combinations work as expected. Users can be instructed to use the direct queues on the server if the printer's advanced features are required(e.g. stapling, folding, color profiles, etc). Please refer to the PaperCut documentation for more information on how to manage differences between printers.
Changed line 10 from:
to:
 
Changed lines 9-10 from:
Some operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. This is a limitation within Windows that needs to be taken into consideration, and the more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up hitting this upper job limit quite easily.
to:
We have seen that Windows operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. This is a limitation within Windows that needs to be taken into consideration, and the more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up hitting this upper job limit quite easily.
Changed lines 17-18 from:
The following variables need to be taken into account before '''any''' planning begins:
to:
The following variables need to be taken into account before '''any''' changes are made:
Changed lines 27-28 from:
It is recommended to extend your timeout period once a week, doubling the time each week until you have reached a suitable timeout period. This would mean, if you wanted to extend the timeout to 24 hours, it will take 5 weeks to go from the default 2 hours. There are two major variables that '''need''' to be monitored multiple times per day during peak usage periods until the timeout extensions are complete to ensure the extended timeouts are working as intended.
to:
It is recommended to extend your timeout period once a week, doubling the time each week until you have reached a suitable timeout period. This would mean if you wanted to extend the timeout to 24 hours, it will take about 5 weeks to go from the default 2 hours. There are two major variables that '''need''' to be monitored multiple times per day during peak usage periods until the timeout extensions are complete to ensure the extended timeouts are working as intended.
Changed line 60 from:
!!!How do I deploy my virtual queues?
to:
!!!Now i've planned, how do I deploy my virtual queues?
Changed lines 29-30 from:
Number one is the number of print jobs in each virtual queue. How are each virtual queues job count looking? Are they hitting close to the maximum number of jobs? If so, you may either need to split this virtual queue up into two queues to lower the usage on each queue, or keep the timeout at a stable time period where the number of jobs will likely never reach the maximum of 1000 held jobs.
to:
Number one is the number of print jobs in each virtual queue. How are each virtual queues job count looking? Are they hitting close to the maximum number of jobs? If so, you have two options that you can follow. Option one is to split the single virtual queue up into two or more virtual queues to lower the usage of each queue. Option two is to keep the timeout at a stable time period where the number of jobs will likely never reach the maximum of 1000 held jobs.
Deleted lines 13-18:





Deleted line 19:
*Number of print jobs sent to each single virtual queue per day
Added line 21:
*Print server resource utilization
Changed lines 23-43 from:
*Print server resource utilization

These variables will greatly change your planning methods for extending the timeout period and it is important to get a feel of these numbers for each virtual queue before extending your timeout periods.




.

This specific business has 2000 users, 50 printers, and 5 hold/release queues. On average, this company prints 750 print jobs per day.
Week 1 -









to:
*Number of print jobs sent to each virtual queue per day

These variables will greatly change your planning methods for extending the timeout period and it is important to get a feel of these numbers for each virtual queue before extending your timeout periods. Below is a brief planning method which should be a starting point for planning your timeout extension and give you an idea of the variables that need to be monitored throughout the timeout extension period.

It is recommended to extend your timeout period once a week, doubling the time each week until you have reached a suitable timeout period. This would mean, if you wanted to extend the timeout to 24 hours, it will take 5 weeks to go from the default 2 hours. There are two major variables that '''need''' to be monitored multiple times per day during peak usage periods until the timeout extensions are complete to ensure the extended timeouts are working as intended.

Number one is the number of print jobs in each virtual queue. How are each virtual queues job count looking? Are they hitting close to the maximum number of jobs? If so, you may either need to split this virtual queue up into two queues to lower the usage on each queue, or keep the timeout at a stable time period where the number of jobs will likely never reach the maximum of 1000 held jobs.

Number two is server resource utilization. How are the CPU and memory usage going with the extra load? Is the print server showing sluggishness after an extension of the timeout period? If so, there are two options you can follow. One is to set up another print server and separate these virtual queues over two print servers rather than one. The second option is to keep the timeout at a stable time period where the server will likely never be over-stressed.

Changed line 8 from:
!!!Maximum number of held jobs per virtual queue
to:
!!!What is the maximum number of held jobs per virtual queue?
Changed line 11 from:
!!!Timeout periods
to:
!!!How long does a job stay in the virtual queue before it's removed?
Changed lines 14-50 from:
!!!Model and make of printers
to:






!!!What if I want to extend the timeout periods for held jobs?
Sometimes extending the timeout periods of held jobs is requested, and the process for extending these timeouts needs to be very carefully planned and implemented to ensure the number of held jobs never reaches the maximum amount and specific print servers can handle the extra held jobs in each queue. It is recommended to increase the timeout period gradually over a period of weeks to ensure no queue is heavily overloaded.

The following variables need to be taken into account before '''any''' planning begins:

*Average number of print jobs per day
*Number of print jobs sent to each single virtual queue per day
*Number of printers per virtual queue
*Average number of held jobs "forgotten" or never released
*Print server resource utilization

These variables will greatly change your planning methods for extending the timeout period and it is important to get a feel of these numbers for each virtual queue before extending your timeout periods.




.

This specific business has 2000 users, 50 printers, and 5 hold/release queues. On average, this company prints 750 print jobs per day.
Week 1 -










!!!What model and make of printers can I use in a single virtual queue?
Changed line 53 from:
!!!Can I "mix and match" printer models?
to:
!!!Can I "mix and match" printer models for a single virtual queue?
Changed line 56 from:
!!!Manageability
to:
!!!How can I manage these queues once they are setup?
Changed line 77 from:
!!!Managed Deployment
to:
!!!How do I deploy my virtual queues?
Changed lines 8-10 from:
!!!Maximum amount of jobs per virtual queue
Some operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. This is a limitation within Windows that needs to be taken into consideration, and the more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up getting this is upper job limit quite easily.
to:
!!!Maximum number of held jobs per virtual queue
Some operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. This is a limitation within Windows that needs to be taken into consideration, and the more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up hitting this upper job limit quite easily.
Changed line 29 from:
!!!How will you separate these queues
to:
!!!How should I separate these queues?
Deleted lines 47-48:
TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous
Changed line 51 from:
[-Keywords: TODO keywords here if needed-]
to:
[-Keywords: find me printing, hold release, multiple queue, virtual queue, deployment, considerations, FAQ-]
Changed lines 24-25 from:
It’s important that the driver on the global queue is able to product output (e.g. Postscript or PCL) that is compatible with all printers/MFDs that will be associated with the global queue. [[https://www.papercut.com/products/ng/manual/ch-find-me-printing-and-load-balancing.html | Chapter 11]] in the PaperCut manual discusses some selection options. If you have a mixed device fleet, there is of course no substitute for good testing. Take the time to test your selected global queue driver with your target devices.
to:
It’s important that the driver on the global queue is able to produce output (e.g. Postscript or PCL) that is compatible with all printers/MFDs that will be associated with the global queue. [[https://www.papercut.com/products/ng/manual/ch-find-me-printing-and-load-balancing.html | Chapter 11]] in the PaperCut manual discusses some selection options. If you have a mixed device fleet, there is of course no substitute for good testing. Take the time to test your selected global queue driver with your target devices.
Changed lines 12-13 from:
Timeout periods for held jobs within a virtual queue are the amount of time a job is held in the queue before it expires and is deleted. These times differ for each environment, and the default value differs between education and commercial/professional sites (2 hours for education, 4 hours for commercial/professional). The timeout is [[https://www.papercut.com/kb/Main/ChangingJobTimeoutOnReleaseStation | configurable]] but the default is a good compromise between user convenience and environmental savings. It is recommended to keep the timeout periods lower than 2 days for large sites.
to:
Timeout periods for held jobs within a virtual queue are the amount of time a job is held in the queue before it expires and is deleted. These times differ for each environment, and the default value differs between education and commercial/professional sites (2 hours for education, 4 hours for commercial/professional). The timeout is [[https://www.papercut.com/kb/Main/ChangingJobTimeoutOnReleaseStation | configurable]] but the default is a good compromise between user convenience and environmental savings. It is recommended to keep the timeout periods at the default values.
Changed lines 21-22 from:
A single organization-wide global queue does offer some management/simplicity advantages but can introduce others. For example a single queue can be a single point of failure so an issue (say a problem jammed job) can affect printing for all users. Multiple global queues partitioned by office/building/floor/area can help mitigate this single-point-of-failure. This does not mean that the partitioned queue can only route jobs to printers in this area, it simply means that users in this region use this global queue by default. Jobs can still be configured to route to any device in the organization if this is what is desired.
to:
A single organization-wide global queue does offer some management/simplicity advantages but can introduce other complications. For example, a single queue can be a single point of failure for all users. Multiple global queues partitioned by office/building/floor/area can help mitigate this single-point-of-failure. This does not mean that the partitioned queue can only route jobs to printers in this area, it simply means that users in this region use this global queue by default. Jobs can still be configured to route to any device in the organization if this is what is desired.
Changed lines 44-47 from:
The recommended deployment process for Find Me print queues is to deploy one virtual queue every couple of days and to monitor print queue load and active jobs on the print queue to ensure the active job limit is not reached. This process also allows you to roll back easily if there are unrelated factors that are preventing the deployment.


to:
The recommended deployment process for Find Me print queues is to deploy one virtual queue every couple of days and to monitor print queue load and active jobs on the print queue to ensure the active job limit is not reached. This process also allows you to roll back easily if there are unrelated factors that are preventing the deployment. If your Find Me print queues are spread across multiple print servers, it is advised to monitor network usage between the print servers in use, especially if there is likelihood of printing large spool files greater than 1GB that will be redirected through the network.

Once deployment has completed and the entirety of your environment is running Find Me printing, it is your decision whether direct print queues are removed for users, to ensure usage of Find Me printing only.

Changed lines 12-13 from:
Timeout periods for held jobs within a virtual queue are the amount of time a job is held in the queue before it expires and is deleted. These times differ for each environment, and the default value differs between education and commercial/professional sites (2 hours for education, 4 hours for commercial/professional). The timeout is configurable but the default is a good compromise between user convenience and environmental savings. It is recommended to keep the timeout periods lower than 2 days for large sites.
to:
Timeout periods for held jobs within a virtual queue are the amount of time a job is held in the queue before it expires and is deleted. These times differ for each environment, and the default value differs between education and commercial/professional sites (2 hours for education, 4 hours for commercial/professional). The timeout is [[https://www.papercut.com/kb/Main/ChangingJobTimeoutOnReleaseStation | configurable]] but the default is a good compromise between user convenience and environmental savings. It is recommended to keep the timeout periods lower than 2 days for large sites.
Changed lines 42-51 from:
Now you have decided how you will be setting up your Find Me print queues, it is time to deploy them. The suggested method of deployment for this in larger organizations where reaching the maximum number of active jobs is a possibility, is to gradually deploy your printer fleet. Please note that if needed, whilst deploying the Find Me print queues, it is possible to keep the direct print queues set up to ensure a crossover period for users to get used to the Find Me print queue.








to:
Now you have decided how you will be setting up your Find Me print queues, it is time to deploy them. The suggested method of deployment for this in larger organizations where reaching the maximum number of active jobs is a possibility, is to gradually deploy your printer fleet. Please note that if needed, whilst deploying the Find Me print queues, it is possible to keep the direct print queues set up to ensure a crossover period for users to get used to the Find Me print queue functionality.

The recommended deployment process for Find Me print queues is to deploy one virtual queue every couple of days and to monitor print queue load and active jobs on the print queue to ensure the active job limit is not reached. This process also allows you to roll back easily if there are unrelated factors that are preventing the deployment.


Changed lines 42-49 from:







to:
Now you have decided how you will be setting up your Find Me print queues, it is time to deploy them. The suggested method of deployment for this in larger organizations where reaching the maximum number of active jobs is a possibility, is to gradually deploy your printer fleet. Please note that if needed, whilst deploying the Find Me print queues, it is possible to keep the direct print queues set up to ensure a crossover period for users to get used to the Find Me print queue.








Changed lines 30-31 from:
This is the first question you should be asking that will require some thought. Depending on your current environment and fleet of printers, planning the deployment process can be the hardest part of the setup. Most Find Me print queues are separated in the following manner, though each will depend on how your environment is currently set up, and how many users you have:
to:
This is the first question you should be asking that will require some thought. The separation of print queues is an option which the end users will notice the most as this will be the list they are given for printing, so care is needed in ensuring that the conventions for deployment are as easy to understand for the users as possible.

Along with this, the amount of maximum jobs per queue noted earlier need to be taken into account to ensure no printer queue is under too much stress. Most Find Me print queues are separated in the following manner
:
Changed lines 39-41 from:

!!!Multiple virtual
queues
to:
Please note that a printer can be members of multiple virtual queues, so if there is an overlap in separation such as a printer being in two departments sharing a computer area, they can be members of both Find Me print queues.

!!!Managed Deployment







Changed lines 27-28 from:
Now you know the factors in deploying multiple Find Me print queues, we can start planning the deployment. =
to:
Now you know the factors in deploying multiple Find Me print queues, we can start planning the deployment. This planning will include how you want to separate each Find Me print queue, along with staged deployment of print queues within your organization.
Changed lines 30-31 from:
This is one of question that will require some thought. Depending on your current environment and fleet of printers, planning the deployment process can be the hardest part of the setup. Most Find Me print queues are separated in the following manner, though each will depend on how your environment is currently set up, and how many users you have:
to:
This is the first question you should be asking that will require some thought. Depending on your current environment and fleet of printers, planning the deployment process can be the hardest part of the setup. Most Find Me print queues are separated in the following manner, though each will depend on how your environment is currently set up, and how many users you have:
Deleted lines 25-31:






Changed lines 27-28 from:
Now you know the factors in deploying multiple Find Me print queues, we can start planning the deployment.
to:
Now you know the factors in deploying multiple Find Me print queues, we can start planning the deployment. =
Changed lines 8-10 from:
!!!Maximum amount of jobs per queue
Some operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. The more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up getting this is upper job limit.
to:
!!!Maximum amount of jobs per virtual queue
Some operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. This is a limitation within Windows that needs to be taken into consideration, and the more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up getting this is upper job limit quite easily.
Changed lines 12-13 from:
The default value differs between education and commercial/professional sites (2 hours for education, 4 hours for commercial/professional). The timeout is configurable but the default is a good compromise between user convenience and environmental savings.
to:
Timeout periods for held jobs within a virtual queue are the amount of time a job is held in the queue before it expires and is deleted. These times differ for each environment, and the default value differs between education and commercial/professional sites (2 hours for education, 4 hours for commercial/professional). The timeout is configurable but the default is a good compromise between user convenience and environmental savings. It is recommended to keep the timeout periods lower than 2 days for large sites.
Changed lines 23-32 from:









to:
!!!What driver should I use for the global queue?
It’s important that the driver on the global queue is able to product output (e.g. Postscript or PCL) that is compatible with all printers/MFDs that will be associated with the global queue. [[https://www.papercut.com/products/ng/manual/ch-find-me-printing-and-load-balancing.html | Chapter 11]] in the PaperCut manual discusses some selection options. If you have a mixed device fleet, there is of course no substitute for good testing. Take the time to test your selected global queue driver with your target devices.








Changed lines 6-7 from:
Before planning deployment of your Find Me print queues, some planning and considerations need to be noted down to ensure your environment will not only be easier to use, but will be compatible with your current printer fleet along with taking in usage statistics for each printer to ensure no print queue is under-resourced. [[https://www.papercut.com/kb/Main/CommonQuestionsAboutFindMePrinting | This knowledge base article]] explains these factors in detail, however this will all be covered again to ensure these factors are taken into consideration.
to:
Before planning deployment of your Find Me print queues, some planning and considerations need to be noted down to ensure your environment will not only be easier to use, but will be compatible with your current printer fleet along with taking in usage statistics for each printer to ensure no print queue is under-resourced. [[https://www.papercut.com/kb/Main/CommonQuestionsAboutFindMePrinting | This knowledge base article]] explains these factors in detail, however this will be covered again to ensure these factors are taken into consideration when planning your deployment.
Changed lines 9-10 from:
Some operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. The more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up getting this is upper job limit. The solution is to have multiple virtual queues and spread the users across these. For example users in floor A use global queue called QueueA and users in floor B use QueueB, etc.
to:
Some operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. The more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up getting this is upper job limit.
Added lines 17-19:
!!!Can I "mix and match" printer models?
If all of the manufacturer's support Postscript on their devices then a “lowest common denominator” driver like a HP Postscript or a Windows “Generic Postscript Driver” will often do the trick for basic printing. You should test common areas across all devices to assure that page boundaries (printable area differences) and finishing options such as duplex combinations work as expected. Users can be instructed to use the direct queues on the server if the printers advanced features are required(e.g. stapling, folding, color profiles, etc).

Changed lines 44-47 from:
!!!Usability
blablabla

to:

!!!Multiple virtual queues
Changed lines 9-10 from:
One of the main reasons an organization will need to use multiple Find Me print queues is factoring in the amount of active jobs on any one print queue...
to:
Some operating systems have a limit on how many jobs can reside in a single print queue. For example on Windows problems/warnings can occur if there are more than 1000 jobs in a print queue. The more printers/users you associated with a single global queue, the higher the anticipated number of jobs pending in the queue. Large organizations may end up getting this is upper job limit. The solution is to have multiple virtual queues and spread the users across these. For example users in floor A use global queue called QueueA and users in floor B use QueueB, etc.
Changed lines 12-13 from:
blablabla
to:
The default value differs between education and commercial/professional sites (2 hours for education, 4 hours for commercial/professional). The timeout is configurable but the default is a good compromise between user convenience and environmental savings.

!!!Model and make of printers
Large organizations tend to have a mix of printer types, models and makes. The driver on the global virtual queue controls how the print job is rendered and what print options are available to the user. If there is a mix of devices in the organization there may need to be multiple global queues to support this mix. For example jobs rendered on a global queue with a Postscript driver cannot be routed across to a GDI based inkjet device. There may be the need to have multiple global queues each associated with different printer types.

!!!Manageability
A single organization-wide global queue does offer some management/simplicity advantages but can introduce others. For example a single queue can be a single point of failure so an issue (say a problem jammed job) can affect printing for all users. Multiple global queues partitioned by office/building/floor/area can help mitigate this single-point-of-failure. This does not mean that the partitioned queue can only route jobs to printers in this area, it simply means that users in this region use this global queue by default. Jobs can still be configured to route to any device in the organization if this is what is desired.










Changed lines 6-7 from:
Before planning deployment of your Find Me print queues, some planning and considerations need to be noted down to ensure your environment will not only be easier to use, but will be compatible with your current printer fleet along with taking in usage statistics for each printer to ensure no print queue is under-resourced.
to:
Before planning deployment of your Find Me print queues, some planning and considerations need to be noted down to ensure your environment will not only be easier to use, but will be compatible with your current printer fleet along with taking in usage statistics for each printer to ensure no print queue is under-resourced. [[https://www.papercut.com/kb/Main/CommonQuestionsAboutFindMePrinting | This knowledge base article]] explains these factors in detail, however this will all be covered again to ensure these factors are taken into consideration.
Changed lines 8-13 from:





to:
!!!Maximum amount of jobs per queue
One of the main reasons an organization will need to use multiple Find Me print queues is factoring in the amount of active jobs on any one print queue...

!!!Timeout periods
blablabla

Changed lines 15-16 from:
to:
Now you know the factors in deploying multiple Find Me print queues, we can start planning the deployment.
Changed lines 25-47 from:
!!!Maximum amount of jobs per queue

!!!Timeout periods



Multiple virtual queues
Methods of separating these queues = Office/floor/printer type/campus/department
Suggested max jobs per queue
Job Timeout Periods
Staging your deployment











to:
!!!Usability
blablabla


Changed lines 3-4 from:
[[https://www.papercut.com/tour/find-me-printing/ | Find Me printing]] solves the problem of finding the closest printer from a long list of available printers. It is a roaming print service that allows print jobs to find users based on their physical location. Some organizations will need more than one Find Me print queue, and planning the deployment of these queues can lead to some larger questions, which this article will hopefully cover.
to:
[[https://www.papercut.com/tour/find-me-printing/ | Find Me printing]] solves the problem of finding the closest printer from a long list of available printers. It is a roaming print service that allows print jobs to find users based on their physical location. Some organizations will want to utilize more than one Find Me print queue, and this article will cover the considerations that will need to be taken in before and during deployment.

!!Factors to consider
Before planning deployment of your Find Me print queues, some planning and considerations need to be noted down to ensure your environment will not only be easier to use, but will be compatible with your current printer fleet along with taking in usage statistics for each printer to ensure no print queue is under-resourced.






Changed lines 15-16 from:
Planning the deployment of your Find Me print queues will factor in some questions which will rely on your current environments printer setup, and how you want your users to interact with these queues, along with ease of administration and little confusion.
to:
Deleted lines 23-28:
Please note however, there are some factoring restrictions and questions that need to be reviewed before any deployment begins.

!!Factors for deployment


Changed lines 9-16 from:
This is one of question that will require some thought. Depending on your current environment and fleet of printers, planning the deployment process can be the hardest part of the setup, based on a couple of factoring questions:

* How do you want your users to see these queues
*


how you want your users to view these print queues?
Most Find Me print queues are separated in the following manner, though each will depend on how your environment is currently set up, and how many users you have:
to:
This is one of question that will require some thought. Depending on your current environment and fleet of printers, planning the deployment process can be the hardest part of the setup. Most Find Me print queues are separated in the following manner, though each will depend on how your environment is currently set up, and how many users you have:
Changed lines 16-17 from:

to:
Please note however, there are some factoring restrictions and questions that need to be reviewed before any deployment begins.
Changed lines 9-16 from:
This is one of the larger questions that will require some thought. How will you separate your print queues in your environment? How do you want your users to view these print queues? Most Find Me print queues are separated in the following manner, though each will depend on how you're environment is currently set up, and how many users you have:

* One
print queue per floor
* One print queue per campus
* One print queue per
office


to:
This is one of question that will require some thought. Depending on your current environment and fleet of printers, planning the deployment process can be the hardest part of the setup, based on a couple of factoring questions:

* How do you want your users to see these queues
*


how
you want your users to view these print queues? Most Find Me print queues are separated in the following manner, though each will depend on how your environment is currently set up, and how many users you have:

* One Find Me print queue per floor
* One Find Me print queue per
office
* One Find Me print queue per campus
* One Find Me print queue per department



!!Factors for deployment



Changed lines 9-10 from:
This is one of the larger questions that will require some thought.
to:
This is one of the larger questions that will require some thought. How will you separate your print queues in your environment? How do you want your users to view these print queues? Most Find Me print queues are separated in the following manner, though each will depend on how you're environment is currently set up, and how many users you have:

* One print queue per floor
* One print queue per campus
* One print queue per office


Deleted lines 4-5:

Changed lines 6-10 from:

!!!
Planning how your queues will work


to:
Planning the deployment of your Find Me print queues will factor in some questions which will rely on your current environments printer setup, and how you want your users to interact with these queues, along with ease of administration and little confusion.

!!!How will you separate these queues
This is one of the larger questions that will require some thought.

!!!Maximum amount of jobs per queue

!!!Timeout periods



Added lines 1-35:
(:title Scaling Find Me Printing:)

[[https://www.papercut.com/tour/find-me-printing/ | Find Me printing]] solves the problem of finding the closest printer from a long list of available printers. It is a roaming print service that allows print jobs to find users based on their physical location. Some organizations will need more than one Find Me print queue, and planning the deployment of these queues can lead to some larger questions, which this article will hopefully cover.



!!Planning your deployment

!!!Planning how your queues will work



Multiple virtual queues
Methods of separating these queues = Office/floor/printer type/campus/department
Suggested max jobs per queue
Job Timeout Periods
Staging your deployment












TODO link your page here: https://www.papercut.com/kb/Main/Miscellaneous

----
''Categories:'' [[Category.Administration|+]], [[Category.Configuration|+]]
----
[-Keywords: TODO keywords here if needed-]

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 05, 2018, at 06:25 PM
Printable View   |   Article History   |   Edit Article