Letโs first create a security group that will be added as a member. This way, you can create multiple groups if needed and organize user access more efficiently.
Option 1: Using the Active Directory Users and Computers Console
Navigate to the Active Directory OU container where you want to create the new security group. In this example, weโll select the Users OU.
Click the New Group button.
On the New Object > Group window, type the group name, select the group scope, select Security as the group type, and click OK.
Once the security group is created, you can add the members (users and groups) to it. These members are the intended Remote Desktop Access users.
After adding users and groups as members, click OK to save the changes and close the group properties window.
Option 2: Using PowerShell
To create the Allow RDP Users group using PowerShell:
Log in to the server and open an elevated PowerShell session.
Run the following command to create the security group. This command creates the security group named Allow RDP Users inside the Users OU:
New-ADGroup -Name 'Allow RDP Users' -GroupScope Global -Path "OU=Groups,DC=domain,DC=com"
Get-ADGroup -Identity 'Allow RDP Users'
Note. In single-domain environments, a Global security group is usually sufficient for managing Remote Desktop access. In larger multi-domain environments, you may want to follow the AGDLP model (Accounts โ Global Groups โ Domain Local Groups โ Permissions) and use Domain Local groups in order to assign resource access.
Using Group Policy Preferences (Recommended Method)
While Restricted Groups is a supported and commonly used method, you can also prefer to manage local group membership using Group Policy Preferences (GPP). Unlike Restricted Groups, Group Policy Preferences allows you to add/remove members without replacing the entire group membership.
This method helps you to prevent accidental removal of existing local admins, service accounts, or other users that may already belong to the local group.
To add an AD security group to the local Remote Desktop Users group using Group Policy Preferences, follow the steps below:
Open the Group Policy Management Console (GPMC).
Create a new GPO or edit an existing one.
Go to Computer Configuration โ Preferences โ Control Panel Settings โ Local Users and Groups.
Here right-click Local Users and Groups and select New > Local Group.
Select Update as the action.
Choose Remote Desktop Users (built-in) as the group name.
Under Members, click Add.
Add your AD security group (for example, Allow RDP Users).
Save the policy and allow it to replicate.
After Group Policy refresh, members of the specified AD group will be added to the local Remote Desktop Users group without affecting existing group members.
Note. Unlike Restricted Groups, the Group Policy Preferences method does not enforce an exact group membership list. Existing members remain unchanged unless explicitly modified by the policy.
Add AD Group to the Remote Desktop Users Local Group using GPO
Group Policy Object (GPO) is a powerful tool that allows administrators to manage settings for multiple users and computers in an organization. One of the settings that can be controlled using GPO is the remote desktop users group membership.
Weโll configure the Remote Desktop Users policy item in this example using the GUI.
Open the Group Policy Management Console (GPMC) on the domain controller by running the command:
gpmc.msc
Right-click the domain and click Create a GPO in this domain, and Link it here. Note. You can also create and link the new GPO in a specific OU.
Type Remote Desktop Users Policy as the policy name and click OK.
Right-click the new policy and click Edit.
Navigate to Computer Configuration > Policies > Windows Settings > Security Settings.
Right-click on Restricted Groups and click Add Group.
On the Add Group dialog box, type Remote Desktop Users and click OK. Note. Do not click Browse. You will not see the Remote Desktop Users in the Active Directory because it is a local group on each computer. Important note. Keep in mind that the Restricted Groups policy enforces the exact membership of the group. It means that any existing members that are not listed in the policy will be deleted from the group after policy refresh.
The Remote Desktop Users Properties window opens. Under the Members of this group property, click Add.
Browse for the security group you created earlier (Allow RDP Users) and save it as a member of the Remote Desktop Users group. Note. You can also add domain users to the Remote Desktop Group.
Click OK on the Remote Desktop Users Properties to save the changes.
Close the Group Policy Editor and the Group Policy Management window.
After the GPO has replicated between DCs, the target machines will apply the policy during their normal Group Policy refresh cycle. On client machines and member servers, this normally occurs every 90 minutes with a random offset of up to 30 minutes. You can apply the policy immediately by running the following command:
gpupdate /force
Note. Adding users to the Remote Desktop Users group does not enable Remote Desktop itself. You need to ensure that Remote Desktop is enabled on the target machines and that Windows Firewall allows RDP traffic. You can enable Remote Desktop through Group Policy under Computer Configuration โ Policies โ Administrative Templates โ Windows Components โ Remote Desktop Services โ Remote Desktop Session Host โ Connections โ Allow users to connect remotely by using Remote Desktop Services.
Verify the group membership: Option 1. PowerShell Remoting Letโs check on one of the computers if the Allow RDP Users group is now a local Remote Desktop Users group member. If PowerShell Remoting (WinRM) is enabled, connect to the computer using:
Note. If users are members of the Remote Desktop Users group but still cannot connect through RDP, you need to check Allow log on through Remote Desktop Services user right assignment. You can config this setting through Group Policy under Computer Configuration โ Windows Settings โ Security Settings โ Local Policies โ User Rights Assignment.
Also don’t forget to check the Deny log on through Remote Desktop Services policy. In case a user/any group they belong to is included in this policy, the user will be denied RDP access even if they are a member of the Remote Desktop Users group. You should remove the user or group from the Deny log on through Remote Desktop Services policy if appropriate.
Thatโs it! The policy is now configured.
At this point, all Allow RDP Users security group members can log on through RDP, provided that Remote Desktop is enabled on the target machine, Windows Firewall allows RDP traffic, and the user is allowed to log on through Remote Desktop Services. If a user who isnโt a Remote Desktop Users group member tries to RDP, they will get a message like the one below.
So an administrator has to add the user as a member of the Remote Desktop Users through the Allow RDP Users security group.
Special Considerations for DCs
The methods described above are primarily intended for workstations and member servers. On AD Domain Controllers, Remote Desktop access is handled differently. DCs do not maintain a separate local SAM database, and the Remote Desktop Users group is stored in AD rather than as a local computer group.
If you plan to grant RDP access to DCs, you need to make sure you also review the settings located here Computer Configuration โ Windows Settings โ Security Settings โ Local Policies โ User Rights Assignment โ Allow log on through Remote Desktop Services.
Note that membership in the Remote Desktop Users group alone may not be sufficient to allow RDP access to a DC if this user right assignment is restricted.
You should always test Domain Controller RDP access carefully and review any GPOs linked to the Domain Controllers OU before modifying Remote Desktop permissions.
Add Users to the Remote Desktop Users Group using PowerShell
You can also add users to Remote Desktop Users using PowerShell using the Add-LocalGroupMember cmdlet.
Run the command below to add a user to the Remote Desktop Group locally on a computer.
Note. A GPO configured for Remote Desktop Users will automatically overwrite the Remote Desktop Usersโ group membership every time the computer updates the group policy. Only use this method if the RDP access is needed temporarily or if no GPO is configured for Remote Desktop Users.
Wrapping up
Managing user access is an important task for system administrators, and adding Active Directory users to the remote desktop users group is just one aspect of this task. By using GPO and PowerShell, administrators can easily manage user access to remote desktops.
By following best practices and regularly reviewing access, you can ensure their environments are secure and only authorized users have access.
For enterprise environments, using an AD security group together with Group Policy Preferences provides you with a scalable and centralized way to manage Remote Desktop access.
The Restricted Groups policy enforces exact group membership. Any existing members of the Remote Desktop Users group that are not defined in the policy will be removed during the next Group Policy update.
I enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion.