When using the thinlocal queue from a Windows Terminal Server, it needs to send the print job to the ThinLinc server. Currently, we recommend using IPP, and to create a "static" machine-wide queue. There are a few drawbacks with this: * The printer queue gets very ugly, and it seems impossible to rename the queue. * Editing cupsd.conf is necessary. Another solution is to use the RDP printer redirection feature. In this case, one special queue is created for each RDP user. Some customers are more used to this method, since this is what Tarantella/Citrix/MS-WTS uses. Another advantage is that the queue is automatically default for the user. And, no configuration at all is required on the WTS. I've tested RDP printer redirection on my laptop. It seems to work with just adding "-r printer:thinlocal" to rdesktop_args. I don't now how stable the printer redirection feature is, though. Probably, IPP+CUPS is little more stable. I guess we could document both methods, and let the customer choose which one to use. Perhaps "-r printer:thinlocal" could be default, though. This issue applies to the nearest printer as well.
Time estimation covers testing the feature and modifying tl-run-rdesktop. If it turns out that there are major glitches in the functionality, the time est. will not hold.
*** Bug 174 has been marked as a duplicate of this bug. ***
Rudimentary version without support for per-printer-specific driver on WTS moved to bug 2786. Moving milestone of this one.
rdesktop (and associated tools) is being removed from the ThinLinc product.
