![]() An example of a group policy object follows. The Group Policy Object for printer deployment to users needs to contain network path to the shared printer created beforehand and it needs to be assigned to an Organizational Unit with users. Do not forget to mark the printer as shared.ĭirect queue configuration in Dispatcher Paragon When setting up the printer port, the printer name or IP address is our Dispatcher Paragon server and queue name matches the direct queue name assigned to the printer in the previous step. When we want to deploy this printer with the direct queue to users, the easiest way is to create a shared printer in Windows. ![]() Each of the following license modules activates direct queues: Authentication, Print Roaming, Reporting, Credit and Billing and Rule-Based Engine. Every direct queue has a specific name and is assigned to a particular print device as shown below. Users will not notice any significant delay while metadata of their jobs is captured by Dispatcher Paragon for reporting purposes. The main benefit of direct queues is that they are transparent to users, all print jobs are released at the print device as soon as they are accepted and (optionally) analyzed by Dispatcher Paragon. This article describes how these queues can be created in Dispatcher Paragon and deployed to users using Group Policy Objects (GPO) in Active Directory, which is the most widely used deployment method. ![]() This is significantly improved by self-managed shared queues where only one shared printer per Dispatcher Paragon server is needed and users can manage members of their personal shared queues by themselves in the web portal provided by the SWC-49 product extension. In addition, when a change is needed, it must be done by administrators. Standard shared queues (print delegation) are similar to direct queues because each of them needs to have a unique name and a unique shared printer. The biggest challenge here is how to deploy the queue for traveling users who change their location and therefore need to send print job into a different server. Ĭonfiguration of secure queue is easy, as it does not require any configuration on Dispatcher Paragon side and only one shared printer and GPO for every spooling Dispatcher Paragon server.Their configuration requires a non-trivial amount of effort by administrators who need to configure them in Dispatcher Paragon, create a shared printer for every device and deploy them to the right people. Dispatcher Paragon knows three types of queues: direct, secure and shared:ĭirect queues are mainly suitable for small network printers where authentication is not required because there is only a limited number of users who send submit print jobs to them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |