2 of 2 people found this helpful
There is no "official" way...but there is a way that proves to be more successful than others. I'm attaching the presentation that others in your organization saw last year at the User's Conference in New Orleans. Your specific query on "...it was recommended that on initial creation of the Secure Release Virtual Queue is to point it to an actual print device..." is covered in Tip #2. What we have learned over time is that as things like Universal Print Drivers get smarter, there's a need to let it "reach out and touch someone" to get some pretty awesome features chucked into the queue. One particular file-saver is the inclusion of HP's Resolution Enhancement Technology (RET), which optimizes the resolution of bitmap imagery in the print file so that the spool file is smaller and faster to chew on once it gets to the printer (a win for the network team, the server team, the end user -- and ultimately YOU!).
So my typical workflow is:
- Install the printer driver.
- Add a printer, pointing it -- via Standard TCP/IP -- to a reference printer and letting it self-configure.
- Adjusting any settings that I want to (change a finisher option or "mopier mode" or whatever) change.
- Share the queue.
- Secure the queue.
Step 2 is the only difference to your workflow, and adds maybe 90 seconds or so to the ordeal.
I hope that this helps!
2 of 2 people found this helpful
Two other best practices that we preach:
- Disable the "bidirectional commincations" support option (Ports tab) for each secured queue.
- Select the "Start printing after last page is spooled" option (Advanced tab) for each secured queue.
If advanced printing features and / or manufacture specific features (e.g. printing effects, scaling, watermarking, etc.) is not required or desired, select the winprint\RAW print processor.
THANKS TIM!!! I'll share with the TEAM.
Just so you know - we already do the two other best practices you've preached
In regards to the optional item you mentioned - our end users always require because they desire - but i'll discuss with the Team.
As always......THANKS SCOTT!!!!
I read the attached doc you sent which was very good by the way....
Tip #4 TRY TO STICK WITH PCL5 OR POSTSCRIPT 3 -- does that even apply to us? We are currently testing UPD 6.2
So I tried to re-create and have questions. Also, what is your availability next week I would like to get this documented for my team ☺
1) Create NEW virtual queue and then I selected “Add a TCP/IP”
2) I retained the TCP/IP in the TYPE OF DEVICE: so in the hostname or IP Address – do I put the virtual queue name or do I put the name of the printer that I am pointing to?
3) So here I kept the NEW virtual queue name and it took me to Additional port information required: I selected Hewlett Packard Jet Direct
4) In the printer driver window I selected HP Universal Printing PCL v5.6.5
5) In the printer name and printing sharing – what info do I put here? Do I put the NEW Virtual Queue or the name of the printer I am pointing to?
If you guys have some time next week pls let me know so I can document and share.
Rommel Pabellano | Optum Technologies
Sr. IT Systems Management Consultant
EUTS – Systems Management Operations
Managed Print Program
Office # 952-202-3261
Maybe quite late but "better late than later" ;-)
In case of create the virtual queue, I always use the LPT port. After create the printer object on the server, you have to configure the printer (do not touch the port) and share with name as you wish, for example "Mono" or "Color". Do not use long string in name of the queue, for example "virtual queue for Blueprint system". Remember, the shared name will be visible on the work station, where that queue is mapped, so in time of printing the employee will see printer "virtual queue for Blueprint system". Next open the Blueprint Secure queue configurator and assign the new queue as virtual. During this process, Blueprint will assign all the Pharos ports to this queue. After this back to the queue configuration and make sure the "bidirectional communcations" is disabled, as Tim mentioned. So remember the SHARED name is visible for employee, not physical name of the printer object on print server.
Hope this help
Mel is using the HP Universal Driver which, when not preconfigured using the HP utility set for their driver, does require an initial printer connection to take advantage of some of the features that are beneficial in a Secure Release workflow. Using LPT1 for the Lexmark universal driver is completely OK. The rest of your post is correct for any manufacturer's driver.
Thank you for update. You're right, in Lexmark UDO I can enable/disable all needed features manually.
I feel the same way man - better late than later Having said that, apology for not replying to you sooner. I really appreciate you taking some time to provide me guidance.
Thank you very much!
No problem ;-).
Always you can try switch to the Lexmark UPD driver, should work with other vendors too.