Windows Server 2008 R2 Remote Desktop Services and WYSE Thin Client Printing

We just implemented RDS on Windows Server 2008 R2.  Printer redirection works great for users with computers who connect up.  I'm having difficulty getting an HP printer connected to a WYSE client to show up.  The WYSE terminal sees it fine, and it works with our older Citrix environment, so I was hoping it would work with this new setup too.  Any ideas?  Is there ever a reason/case to install the printers locally on the RDS session servers?  Or put the drivers somewhere?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It depends on the printer and the model of the Wyse client.  You'll want your Wyse to present the printer to the RDS session with a specific driver name, and then use the RDS printing redirection to map that printer appropriately.  

You definitely need the driver on the RDS servers..

I try to avoid having any locally attached printers if at all possible.. even if it is on the user's desk, I try to put the printer on the network, and then use other mechanics to connect the printers.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jpletcher1Author Commented:
We have about 50 remote sites that have a cheaper HP 1012, 1022, etc, printer that is connected via USB, so they have to be local printers.  

I'm not sure I understand RDS Printing Redirection.  How does that work?
I'm guessing at this point.. but I'm assuming it works pretty similarly to ICA client printing (the old style).

When the RDS session is established, the server queries the client for available printers, by name and more importantly by driver name.
It looks to see what drivers are available and if they are available, or the user has the rights to install the driver, then the printer is connected.  This is important because the driver names have to match exactly if the user cannot install the driver.  If they can, then it will install the driver and use it.  

On the Wyse terminals using the WyseOS (or whatever they are calling it these days), it can be set to present a specified driver name and it will be used or installed.  

If they are using embedded Windows, then it is treated just like a normal PC.  

And RDS has it's own universal driver that it can use if available.

IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

jpletcher1Author Commented:
I was told that in Windows 2008 R2 that you can't do the  printer redirecting like you could in the past and that we'd either need to purchase WYSE terminals that have embedded XP or else make all our printers network printers instead of local USB.

I think Windows 2008 still works the old way where you can map printers, but maybe not in R2.  I can't find much info out there on it...
Hmm... that I don't know.. I don't use straight RDS. just using Citrix, so I could easily be wrong with it :-\

I do know that regular RDS has improved capabilities in Win2k8R2, and is not nearly as difficult as it used to be, but I can't speak to the USB capabilities.  I am assuming that they are pretty minimal for direct USB access, while the windows printer redirection is pretty decent.  I'd definitely contact Wyse and talk to one of their field engineers (not sales!) and ask them.

jpletcher1Author Commented:
The ordinary printer mapping worked fine.  The reason I wasn't able to get it to work was due to the file path to the print map file that I was passing to the wyse terminals.  I was giving the full path to the file when all I needed was the file name.  The WYSE clients assume everything they use will be in the same directory, so the full file path was messing me up.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.