RD 2008 R2 and remote printing
Looking for some suggestions.....We have recently moved one of our clients into our private cloud running 2008 R2 servers. We have a Remote Desktop Farm with 2 RDSH, 1 Connection Broker which is also a DC, 1 Gateway server and 1 Web App server. We have published applications on all the client machines, it should be noted that all of the client machines are remote to the RD Farm. They are also connecting through the Gateway. Everything is working as expected with the exception of SSO which is a completely different story and we don’t care to much to get this working at the moment (but have a ticket open with Microsoft to troubleshoot)
The issue we are seeing is that Easy Print seems to be really slow no matter what setting you choose, drivers, gpo policies etc. Easy Print does work but the client business model requires that printing be somewhat efficient due to part of their business process. When using Easy Print jobs can take up to 8 to 12 minutes to print. These are large jobs (10 to 12 MB) and contain everything from graphics to different fonts etc.
We have recently installed the printers on the RDSH servers and used Isolated Driver mode and print jobs are now completing within 2 to 3 minutes which is great BUT it appears that when printing in this manner the print jobs are consuming much more bandwidth and bring the internet to a slow crawl thus making all published apps fail/timeout.
Client bandwidth at the remote sites are around 15 down/up and the latency looks really good as well. With the limited info provided above does anyone have any suggestions, configuration tuning around printing. Seems to be tha printing in RDSH is a real nightmare when you need performance.....
thx for your time.
The issue we are seeing is that Easy Print seems to be really slow no matter what setting you choose, drivers, gpo policies etc. Easy Print does work but the client business model requires that printing be somewhat efficient due to part of their business process. When using Easy Print jobs can take up to 8 to 12 minutes to print. These are large jobs (10 to 12 MB) and contain everything from graphics to different fonts etc.
We have recently installed the printers on the RDSH servers and used Isolated Driver mode and print jobs are now completing within 2 to 3 minutes which is great BUT it appears that when printing in this manner the print jobs are consuming much more bandwidth and bring the internet to a slow crawl thus making all published apps fail/timeout.
Client bandwidth at the remote sites are around 15 down/up and the latency looks really good as well. With the limited info provided above does anyone have any suggestions, configuration tuning around printing. Seems to be tha printing in RDSH is a real nightmare when you need performance.....
thx for your time.
ASKER
The printer they are using are Lexmark T650/T640, mid-sized company printers. i would think that these are middle grade printers and they are 100% supported on 2008 R2 running RD roles according to their specs and Microsoft HCL.
http://www1.lexmark.com/US/en/view/Printers%20&%20MultiFunction/Lexmark-T650n/catId=cat170005-category&prodId=4643-product
So my question is are there any perfomance tuning options that anyone recomends to improve printing performance or should i try and go back to Easy Print Driver as this is what Microsoft recomends in the first place.
So far Direct IP printing with the standard Raw protocol seems to be the most efficient method when you need print jobs quickly and Easy Print is the preferred method when performance is not of concern.
http://www1.lexmark.com/US/en/view/Printers%20&%20MultiFunction/Lexmark-T650n/catId=cat170005-category&prodId=4643-product
So my question is are there any perfomance tuning options that anyone recomends to improve printing performance or should i try and go back to Easy Print Driver as this is what Microsoft recomends in the first place.
So far Direct IP printing with the standard Raw protocol seems to be the most efficient method when you need print jobs quickly and Easy Print is the preferred method when performance is not of concern.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just ned to close the ticket
Printers/drivers vary in intelligence, and generally the cheaper the printer, the less RAM and CPU power it has to do the job. Is this one of those $99 printers, or one that has built-in postscript capability?
A course of action is to get a printer that doesn't let the windows printer driver do all the work. That requires going back and forth. Get a smarter printer that speaks native postscript. Such a printer is told what to print, where to put it, and then the printer just figures out the rendering.