.thinprint bottle necking on terminal server

[TheOriginalDogbyte]

we have sometimes over 60+ people logged into our terminal server running thinprint. sometimes they experience wait times of 15 min plus, and i was wondering other than beefing up the box for faster spooling, or lowering the dpi on each individual client printer to lessen the print job size, how else can i try to lessen the amount of time these print queues grow into during peak hours.

 

[Michael52x]

What printers? How many? Increasing printer memory, upgrading to faster units, initiate printing schedule times for groups, can help.
Are these PDF files? Bloated files with unnecessary info.
A lot of printing could simply be transfered to who needs it other than using paper for everything.


"Impatience will reward you with dissatisfaction" RMS Cosmics'97

 

[TheOriginalDogbyte]

these are individual printers at the desk of all the terminal server clients that work abroad. who dial in from different cities. thinprint pushes it to their default printer that is connected to thier pc in which they are running mstsc. its normal everyday .doc .xls .pdf .tif, this is in the medical field so a paper trail for filing is a definite fact of life.

 

[Michael52x]

Oh, uploading files can be tedious, especially if they have forms, and graphics. You throughput may be limited due to the heavy traffic. So,,,Both ends would have to be upgraded to some extent, but you might think of adding another thin client server.

"Impatience will reward you with dissatisfaction" RMS Cosmics'97