Otherwise the RDP-Tcp setting won't take effect right away.Īll users that are part of the Remote Desktop Users group and Domain Users group should now connect. Then you have to go to services on the Terminal Server and restart the Remote Desktop Services service. Then from your Terminal Server: Start - Administrative Tools - Remote Desktop Services - Remote Desktop Session Host Configuration - RDP-Tcp - rt clk - properties - security - Add - Domain Users - Grant then User Access and Guest Access - OK. Add "Remote Desktop Users" to this policy. In my case I added the needed users to Remote Desktop Users group on the DC and then set the Domain Policy in Group Policy Management Console - Group Policy Objects - rt click your default domain policy - edit - Computer Configuration - Policies - Windows Settings - Security Settings - Local Policies - User Rights Assignment - Allow log on through remote desktop services. If they can then you just need to worry about a local setting on that Terminal Server. First thing to do is see if a non domain admin can RDP to and different server. I was having the same problem and it was killing me. Checking the Remote Desktop Services service is very important and also helps to restart it. Your user account is not authorized to access the RD Gateway Was kinda strange because i was pretty sure the user account was added to the CAP and RAP policy on the server hosting the remote desktop gateway server role.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |