Question : Problem: Local Mapped Drives not available on Terminal Services

I have an issue with Terminal services:

We have set up a Terminal Services profile that is pretty locked down for some users who are running a app remotely. Everything seemed ok until we found out that users could not map their local drives or printers in the RDP session. I checked the client settings, those were set to map the printers and drives. I then checked the domain settings and the TCP-RDP settings on the terminal server itself and in both places the settings should allow a user to connect.

Even with all those settings in place I still cannot log in using a locked down profile. If I log in with my domain admin account, I can map drives, but with the term services profile I cannot no matter what settings i loosen. Other than the three places I mentioned, what else might affect the ability to map local resources in an RDP term services session?

Answer : Problem: Local Mapped Drives not available on Terminal Services

Found the problem:

The profile appeared to be corrupted. After deleting the profile and re-crating it on the server and using that user profile directory as my template that fixed the problem.