RDP Clients cannot connect drives but Terminal Server Group policy objects missing
Posted on 2006-05-31
RDP clients cannot connect local disk drives.
I have two servers only and they are both acting as domain replicas and global catalog servers.
First is a Windows 2000 SBS and the second is a Terminal Server configured also as a domain controller.
All is, and has been working well for remote connectivity until I now need to allow a remote user to have access to their local drives. "Automatic Printer Mapping" from remote sessions works, but "Connect Client Drives at logon" and "Drive Mapping" is greyed out in the Terminal Server's RDP configuration manager on the "Client Settings" tab. (As is audio mapping which is fine with me.) So, I can't uncheck it.
The local computer policy of the Terminal Server has NO Terminal server settings at all in it. So I cannot see where or how to set anything there. All the relevant registry settings in the terminal server seem correct but I beive are being over-ridden by group policy.
I assume this is because a group policy somewhere is set this way. I can log in to the domain controller and open the default domain policy. Under Computer,Administrator Templates, Windows Components,Terminal server, Client/Server Data Redirection, I have set the "Do not allow drive redirection" to DISABLE (meaning drive redirection should be possible in all cases.) Ran secedit /refreshpolicy /machine_policy and it looked good in the log. No other unusual events in my logs. Still doesn't work - client drives cannot connect, despite the client end having the "Local Drives" checked under local resources..
Where should I be looking?