Printing on Wyse S10 Thin Clients...

Soldato
Joined
16 Nov 2002
Posts
11,290
Location
The Moon
Hi all, just wondering if anyone has any experience of doing this?

I know I can set up the printer so it is available to print from within their RDP session but I would like to get it working so that the printers are set up on the Wyse client itself as we are having too many instances of people setting a default printer at one office then going to one of our other offices and not checking the printer which they are sending prints too and documents coming out all over the place!

I've tried to get item level (IP) targetting working in group policy so that it only maps the printers that each user actually needs when they log in but I can't get it to work properly so this is my last effort at getting printing sorted!
 
I don't have experience of Wyse thin clients but I have done this on HP thin clients in the past. You will need to install the print driver(s) on the thin clients and have a login script that maps the relevant printer(s) at logon.
 
Well the Wyse S10 can link to a network shared printer which it then maps through to your RDP session when you log in. Ive managed to get it to do that, however it only seems to be a basic print driver and is only printing text.
 
I use the item targeting to add printers but i do it off a group. Which means that IT have to manually move users around floor groups, which won't work in your case. Have you tried any other item targeting than IP address. Its possible you might be able to find some other unique identifier than you can use to add printers.

This is why followme type printing works great in these sorts of instances. That way when they send a print it stays in the queue until they go to the printer of their choice any where in the company and release the jobs.

safecom, equitrac doe these sorts of solutions, something to consider. They can often latch on to any existing print system by installing some card swipes on the printers and setting up a new server.

Law firms like them because it allows more security when printing, as jobs are not left in trays all day and people often get all their printing from the day at one specific time, so prevents people from hogging the printer that you just sent a job too, as you can use any one to release jobs. Also as there is only one printer added to everyones pc called "follow me printer" it is super easy to administer. It also adds more reporting features so lawyers like it as they can a charge their clients for printing copies. Yes bill £400 an hour then charge £10 for a copy, only lawyers.
 
Last edited:
we had quite a few wyse terminals and printing on them using terminal services was a pain in the bum, in the end we just let the users add the printers at that site.
 
Pass through printing is unreliable at best in my experience with HP Thin Clients. Try and sort it out via RDP into the print server if possible.
 
Well I got item level targetting to work via IP so that it would only map specific printers I'd set depending on the IP range from which the client logged on. The problem I was having was that it wasn't removing the printers if they moved site (which I wanted it to do!)

Eg...

Site A - user logs on, gets Site A's printer mapped because they are in the correct IP range.

User goes to Site B - user logs on gets new printer mapped but old printer is still in list of printers.

I want a seamless system whereby the only printer the user gets is the one specific to that site and remove any old ones so they can wander between sites as much as possible and they will only have the one correct printer to print too!

I've followed a few tutorials on it which specifically look at users with roaming profiles but still had no joy. It can be done, so not sure if i'm just making a silly mistake somewhere!
 
Last edited:
Back
Top Bottom