?
Solved

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

Posted on 2012-04-03
6
Medium Priority
?
2,276 Views
Last Modified: 2012-04-23
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?
0
Comment
Question by:jpletcher1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 25

Accepted Solution

by:
Coralon earned 2000 total points
ID: 37806819
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.

Coralon
0
 

Author Comment

by:jpletcher1
ID: 37811411
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?
0
 
LVL 25

Expert Comment

by:Coralon
ID: 37812320
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.

Coralon
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 

Author Comment

by:jpletcher1
ID: 37812351
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...
0
 
LVL 25

Expert Comment

by:Coralon
ID: 37812484
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.

Coralon
0
 

Author Closing Comment

by:jpletcher1
ID: 37881859
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.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

718 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question