Drive mapping in Terminal services part 2

This is one of those quirky issue that will not go away. As we noted in my steps from an earlier post Drive mapping in Terminal services this should have let your user be able to connect via an RDP session and use the clinet mapped drives. As some you have noted this doesn’t always work. I’ve done a bit more research and found that sometimes you need to take an extra step. Please note that this requires a registry hack. If you are not confortable please use backup or find someone who is more capable to give you a hand.

Problem: Original Drive mapping in Terminal services steps still don’t show mapped drives
Fix: Open you registry editor on the server using ‘regedit’. browse to the following key:
‘HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWdsrdpwdfEnablePrintRDR’. change the value from 0 to 1.

I’m not sure why changing the print redirector has any bearing on this particular problem, but it seems to do the trick once you log off and log on once again.

About the Author

Leave a Reply

%d bloggers like this: