Sunday, February 17, 2013 3:16 PM
I have a Windows 2012 server with all the relevant RDS roles installed and a Windows 2012 file server.
I wish to use Group Policy to set romaing profiles for all RDS users, the policy in question is:
Computer Configuration > Admin Templates > Windows Components > Remote Desktop Session Host > Profiles > "Set path for RDS user romaing profile"
I have set the profile path to be \\TTLCloudFP01\profiles$
This does not seem to create a profile, even after I have logged off and rebooted the server to make sure the GPO is in effect. If I create the profile path in AD profiles section it does create a roaming profie but, if I do this in AD in the Remote Desktop Services section it does not.
No event logs are generated on either the RDS server of my file sever. I am stuck! Can anyone suggest any further trouble shooting I can do to resolve this? I have this exact same configuration working at other sites, but it is all server 2008 R2, I wonder if this is an issue specific to 2012.
Any help would be much appreciated.
Sunday, February 17, 2013 5:20 PMIf all users don't share the same profile, you may want to add %username% after profile$. Or this case collection may help too:
Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on
Monday, February 25, 2013 2:21 AMModerator
You need to move all RDS servers to one OU, and apply the GPO you created. For detailed Group Policy troubleshooting steps, I would recommend that you repost at Group Policy Forum.
For more detailed information about Terminal Server profile, please refer to the following articles.
Manage User Profiles for Remote Desktop Services
User Profiles on Windows Server 2008 R2 Remote Desktop Services
Best Practice: Roaming Profiles and Folder Redirection (a.k.a. User State Virtualization)
If you have any feedback on our support, please click here
TechNet Community Support
- Marked As Answer by Aiden_CaoMicrosoft Contingent Staff, Moderator Wednesday, February 27, 2013 7:35 AM