• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 271
  • Last Modified:

Windows 2008 R2 Terminal Server Client Resources Not Redirecting

No matter what I do, none of the client resources (ala printers, disks and sound) are being re-directed to from any machine to the terminal server.

I have tried from my laptop (no in the domain), thin clients (in the domain) and desktops (in the domain) and nothing re-directs.

I am not getting any errors and everything appears to have started.

Help!
0
Leadit
Asked:
Leadit
  • 3
  • 3
1 Solution
 
Red_TechCommented:
Do you have Group Policy settings (restrictions) in place for your Remote Desktop Servers?
0
 
LeaditAuthor Commented:
Nope, or at least none that I believe effects this :-)

Attached is a screenshot from my terminal server policy.
TS-Printer-Policy.PNG
0
 
gortm001Commented:
Regardless of your policy, you can still disable client redirection in the server it self. Open Administrative tools, Remote Destop Services , configuration Hostserver Remote desktop sessions. You will see a frame with Connections at the top (i'm translating my Dutch version here on the fly, so the text may be not completely be accurate ;-) )

In it you will see the RDP-Tcp connection.  Rightclick with your mouse on ths connection and choose Properties. Find the tab Client settings (or properties). In the lower half you will see a list with functions you can disable in the redirection. In your case Station (diskdrive) and printer may be selected. If it is, you can policy until you are blue in the face, but it will allways be overruled by this.

If that is not the case, I see that you are using Loopback Policy processing, and you merge it. That means that the policy you define here will be merged with the user policy in general that is valid for your users. Merging means that the most restrictive one wins. So if in your normal user policy this is disabled it stays disabled. You could run a gpresult to see. The other option you have with policy loopback, is that you can choose replace. I would go for that one, because usually you want a complete different limitation of user rights and possibilties thean you would have on a normal workstation.

Hope this helps,

KG
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Red_TechCommented:
gortm001 is right about being able to disable/enable it on the server without group policy, but if you had GP enabled your server settings themselves wouldn't matter, as the GP would override the server settings.
0
 
Red_TechCommented:
Leadit have you had any luck with getting this to work?
0
 
LeaditAuthor Commented:
None of the above suggestions worked and I had to end up reloading the server.

I think at the end of the day it resided on how I setup .Net and I think something became corrupt.

In the future I am applying .Net 3.5 before I apply any other roles to my systems!
0
 
LeaditAuthor Commented:
This is the only thing that worked!
0
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.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now