Unable to access usb key from thin clients on 2008 R2 RDP server

I know this problem was marked as answered in a previous question (http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_25987228.html), but the solution doesn't work in my environment, and the conditions may not be the same.

I am trying to connect older Wyse thin clients to a new 2008 R2 RDP server and allow users to access usb keys that are attached to the thin client.  If the key is attached when the connection to the server is made, the "Files on WBT00806440262D" shows up in the Computer window under Other drives, and that can be expanded to show the "Removable Storage" folder which *should* show the files on the key, but when you click on the Removable Storage folder you get the error message "\\tsclient\Files\Removable Storage is not accessible.  You might not have permissions to use this network resource.  Contact the adminstrator of this server to find out if you have access permissions.  The file exists."

The usb is accessible from the same thin client when connecting to a 2003 R2 terminal server, so there is no problem with the thin client, usb key, or permissions.  I have read that there is a problem with the protocol when using RDP 5.2 to connect to the new RDP service on the 2008 R2 servers.  The solution addressed in the previously mentioned question doesn't work in my testing.  I am unable to update the RDP client on the thin clients as Wyse doesn't support these models any longer.  I have also read another article that suggests that there is a QFE that can be included in the core build on the thin client that will fix the problem, but I don't have access to the build and again, Wyse doesn't support these any longer so they aren't going to do it either.

Is there a solution on the RDP server to allow full compatibility with older versions of RDP?  This seems to be the root cause of the problem as it used to work on the older TS servers, and only fails with the newer version.

Thanks for any help!
Who is Participating?
Cláudio RodriguesFounder and CEOCommented:
Sorry but I do think there is no solution for you. The only one would be to upgrade the firmware on the thin client, what Wyse clearly is not doing. That is the #1 reason why I tell all my customers if they do want to use thin clients, make sure they get the ones with Windows Embedded (XPe the older, WES the new one) as these use the exact same RDP client as Windows so an upgrade can be done. The Linux/Other OSs thin client do NOT have a fully supported, and more than that, official, RDP client so you get into issues like this.
One option you could try is to get the 2X ThinClient Server product and try their OS build on your Wyse terminals to see if that helps.

Cláudio Rodrigues
Microsoft MVP - RDS
Citrix CTP
Felix LevenSenior System and DatabaseadministratorCommented:
Ok, there are changes in Drive redirection handling since 2008 Terminalserver:

This thread should give you some more information and a possible workaround:

Please report back, cause I didn't know about this changes too.
runByAuthor Commented:
Unfortunately, I have already seen the link you provided and the proposed solution doesn't seem to be working.  That article was written 2 years ago and is with 2008, not 2008 R2 so things may have changed since then.

I have already set the Group Policy for drive redirection to "disable the do not allow drive redirection"  group policy setting which *should* mean that it allows the drive redirection.  However, I still have the problem.  I also notice that even with this policy set, I can still change the setting locally on the server to disable drive redirection.  local rdp settings
The other odd thing is that when the drive redirection is either allow or disallowed via GP, the folders show up in explorer, but can't be access, but when they are disallowed on the local server, there is no folders at all in explorer. screenshot
I am still looking into which registry keys are supposed to be affected by these settings and setting them manually.
Dr. KlahnPrincipal Software EngineerCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.