Hi Craig, If by local, you mean network printers, then yes. If by local you mean physically attached to the SRSS server or WTS, then no. And yes, I am sending the specific printer driver name to the WTS. As I said, most of the time things work.
My understanding of the SRWC is that it "tricks" the WTS into thinking that the connection is always there. This should mean that once the uttsc connection is made, the WTS redirects the printers then should never change the redirect number unless I log out and log back in. As I hotdesk, the SRSS connection to the DTU should follow the card but the backend uttsc connection should look constant to the WTS. Am I wrong on this? As I hotdesk, sometimes the printers do not move. But I am not logging out, I am simply going to a different DTU. If I move in a Solaris or Linux session, non-kiosk, the network printers move just fine. I am not clear as to why that should change with kiosk mode and uttsc. Thanks! /paul On Fri, May 27, 2011 at 1:56 PM, Craig Bender <craig.ben...@oracle.com>wrote: > You are mapping locally connected printers? And you are providing the > names of specific Windows Printer drivers? > > When you hotdesk, Windows doesn't know you moved, and since the printer > mapping is made before the connection to the Terminal Server, it's going to > want to use the initial connection. > > One way to handle this is to use follow me printing, but that just gets you > to the right queue from a Solaris/Linux perspective. Windows is still going > to try to use the specific windows driver that was initially mapped. > > If all your printers are postscript capable, then drop the windows printer > driver and implement the follow me printer solution here: > http://wiki.sun-rays.org/index.php/SRSS_Addon:_Follow_Me_Printing > > If you must use specific windows drivers, then you are going to need to > kill the connection on hotdesk and reconnect. If you only have one WTS, > this is not a big deal because you'll always find your session. If you have > more than one, you are going to need a session directory. > > > > On 5/27/11 9:26 AM, Paul Whitener wrote: > >> Greetings all, >> >> I am seeing some inconsistent behavior with printer redirects using >> uttsc. Any input would be greatly appreciated. My configuration is as >> follows: >> >> latest SRSS/SRWC on RHEL5.4 with 5 network attached printers installed >> and working. The SRSS is in kiosk mode enabled for card users only. >> 13 SR3 DTUs >> Win 2008R2 Terminal Server, at remote location, with proper print >> drivers installed and working. The WTS is only serving one >> application. No desktop. >> Windows laptops, both XP and Win7 >> >> When a user inserts their card into a DTU, it does an automatic redirect >> to the WTS using uttsc. I pass the printers on the uttsc arguments >> line. Printers do redirect and populate the printer dialogue box on the >> Windows session most of the time. And if they show up, I can print. So >> in the print dialogue I see "laser (redirect 5)" and "lexmark (redirect >> 5)" as I would expect. >> >> If that same user pulls their card and goes straight to another DTU and >> inserts their card, they must retype their Win credentials and the app >> pops up still running and usable. But if I pull up the printer dialogue >> box, sometimes the printers pop in slowly, with the correct "redirect >> number" (redirect 5 in the above example), but sometimes the printers do >> not move to the new DTU. The printer dialogue box is empty. If I go >> back to the original DTU, the printers are usually there and work. If >> the printers do not show up on the move, waiting does not solve the >> problem. If I jump around to enough DTUs, sometimes one of the printers >> may pop in to a previous DTU that had none. >> >> Next scenario: When I pull that same session to a laptop, sometimes the >> printers show up with the same "redirect 5" but sometimes they get a new >> number from the WTS. Then there may be multiple "redirect numbers" in >> the print dialogue box on the laptop. If I pull back to a DTU, then >> sometimes I see multiple "redirect numbers" or sometimes things pop in >> slowly. >> >> I know this is all very confusing. The vendor of the WTS app we are >> using normally puts a piece of software on the WTS made by Elusiva and >> then a piece on the Win clients that makes printing work Win-2-Win every >> time. Problem is, when its on the WTS, it prevents uttsc from seeing >> the printers at all. And they don't make a Linux client for printing. >> >> Any wisdom on this would be greatly appreciated! >> >> /paul whitener >> Wake Forest University >> >> >> >> _______________________________________________ >> SunRay-Users mailing list >> SunRay-Users@filibeto.org >> http://www.filibeto.org/mailman/listinfo/sunray-users >> > _______________________________________________ > SunRay-Users mailing list > SunRay-Users@filibeto.org > http://www.filibeto.org/mailman/listinfo/sunray-users >
_______________________________________________ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
