Networknet archive Blog

Windows Server: Allow support users to connect remotely to a domain controller

Originally published 7 comments

Active Directory Domain Services (AD DS) is an important Windows infrastructure role. In some environments, helpdesk or support staff need Remote Desktop access to domain controllers. I needed a plan for staff who were not Domain Admins to connect to our branch-office domain controllers.

Configure the security group and policy

In my configuration, I created a security group and changed the "Default Domain Controller" Group Policy to allow these users to connect remotely.

Without these changes, a user may receive the following connection-denied message:

Remote Desktop Connection: The connection was denied because the user account is not authorized for remote login.

Start by creating a Windows security group.

New-Group-Object

Add the required user accounts to the new security group, then add that group to the built-in Remote Desktop Users group. This membership is needed for the users to connect through Remote Desktop Protocol.

Remote-Desktop-Users-Group-Add

Open Group Policy Management Editor and edit the "Default Domain Controller" policy. Find the "Allow log on through Remote Desktop Services" user right under Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\. Add the new security group and close the management console.

Group-Policy-User-Rights-Assignment

If you try signing in with a support account before the policy has been applied, the domain controller may display this message:

To log on this remote computer, you must be granted the Allow log on through Terminal Services right. By default, members of the Administrators group have this right. If you are not a member of Administrators group or another group that has this right, or if the Administrators group does not have this right, you must be granted this right manually.

Error-Allow-Log-on-through-Terminal-Services

Wait for the Default Domain Controller policy to be processed, or run gpupdate /force. I ran gpupdate and then signed in with a support account. The Remote Desktop connection worked, and the account was not a Domain Admin.

Remote-Desktop-Connection

Related links

7 comments

Comments from the original WordPress site, kept read-only.

  1. Chris

    I'm trying the other way around, remote log in from Win Server 2008 R2 to Win 7, as a domain administrator, and I get the "...Allow log on through Terminal Services..." window. Domain admin is a member of the local Administrators group, and I also added it to the Remote Desktop Users group.

  2. Jeevan

    Hi,

    Your answer is correct, but when allowing domain users for RDP they are also getting admin rights so that they can create modify and delete any data on the server which should not happen.

    Please do revert...

  3. Chris

    Hi Jeevan, I don't understand your reply. Please elaborate?

    This is a controlled environment, not an enterprise setup, only I use this setup. I just want to know how to alleviate the restriction.

  4. 屋頂農場

    When someone writes an paragraph he/she retains the thought
    of a user in his/her brain that how a user can be aware of it.
    So that's why this article is outstdanding. Thanks!

  5. Tommy

    Note - You need to add domain\Adminstrator to the list or the adminstrator won't get RDP access