About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The Remote Desktop client shows this message when the account reached the server but does not hold the "Allow log on through Remote Desktop Services" user right there. The right comes from membership of the Remote Desktop Users group (or Administrators), and a Group Policy object (GPO) can override what the server's own settings say.
Work from the server outwards: confirm group membership, find which policy decides the right, look for a Deny entry, and, in a collection, check the user groups. Microsoft says a change to a user right takes effect the next time the account signs in, and no restart is needed.
What the error means
Microsoft's RDS troubleshooting page lists "To sign in remotely, you need the right to sign in through Remote Desktop Services" as one of the access-denied messages. It associates this message with connections to a Remote Desktop Services farm rather than a standalone RDP connection, and its remedy is to make sure the user's account belongs to a group that has the right to sign in remotely.
Two policy settings decide this, both under Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment:
- Allow log on through Remote Desktop Services (constant SeRemoteInteractiveLogonRight) decides which users or groups can reach the sign-in screen of a remote device through a Remote Desktop Services connection.
- Deny log on through Remote Desktop Services (constant SeDenyRemoteInteractiveLogonRight) blocks users. Microsoft states that it "supersedes" the Allow setting when an account is subject to both.
Microsoft's defaults, from the policy pages: members of Administrators hold the Allow right on domain controllers, workstations and servers. Remote Desktop Users also holds it on workstations, stand-alone servers and member servers. On a domain controller the effective default is Administrators alone. The Deny right is not defined by default.
Microsoft's guidance adds that to use Remote Desktop Services to sign in, the user or group must be a member of Remote Desktop Users or Administrators and be granted the Allow right. A user can open a Remote Desktop Services connection to a server and still be unable to sign in to its console.
Group Policy order matters. Microsoft lists local, site, domain and organisational unit (OU) policy settings in that order, with later ones overwriting the local computer's settings at the next policy update. Its troubleshooting page also states that "Group Policy settings override Local Security Policy settings".
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Account is not in Remote Desktop Users or another group that holds the right | One user fails; colleagues in a listed group succeed | Group membership on the target server |
| A GPO defines the Allow right and the list omits the user's group | Every user outside the listed groups fails after a policy refresh | Resultant policy shows the Allow right with a winning GPO |
| The user's group appears in Deny log on through Remote Desktop Services | The Allow right is present, yet the user is refused | The Deny list in the same report |
| The collection or RemoteApp assignment excludes the user | The server accepts the user when connected directly, but the farm refuses | The collection's User Group list and each app's User Assignment |
| Target is a domain controller | Only members of Administrators succeed | Microsoft's domain controller default for the right |
| The "Network access: Restrict clients allowed to make remote calls to SAM" policy is enabled (Windows Server 2016 and later) | Users cannot connect although the right and groups look correct | The policy's status under Security Options |
Microsoft's page also describes a separate message, "Account restriction is preventing this user from signing in", and ties it to Credential Guard. That is a different fault.
Prove the cause before changing anything
All of these only read. Run them on the target Remote Desktop Session Host, in an elevated window.
List the members of the local group:
Get-LocalGroupMember -Group "Remote Desktop Users"
Microsoft documents Get-LocalGroupMember as a command that gets members from a local group. If the user or a group that contains the user is missing, that is the first cause. Microsoft's page frames the group check "at the forest level" in Active Directory Users and Computers (domain node, Built-in, Remote Desktop Users, Properties), and in Local Users and Groups (lusrmgr.msc) when the remote computer is not a domain member. It does not say which of the two applies to a domain-joined member server, so check the local group first and then the directory group.
Next, write the resultant policy to a file:
gpresult /h c:\gpresult.html
Microsoft's general RDP page uses this form for the "Allow users to connect remotely" policy and tells you to read the setting and its Winning GPO entry. Using the same report for the user-right entries extends Microsoft's example. Open the file, find the computer settings for User Rights Assignment and read the Allow and Deny entries and the GPO that supplies each. If neither appears, the right is not set by a GPO and comes from the local policy.
To read the effective right as a plain file, export the merged policy:
secedit /export /mergedpolicy /cfg c:\user-rights.inf /areas user_rights
Microsoft's secedit page documents /mergedpolicy ("Merges and exports domain and local policy security settings"), /cfg and /areas user_rights. The command writes a new text file. Look for the lines that start with SeRemoteInteractiveLogonRight and SeDenyRemoteInteractiveLogonRight. A good result lists the group the user belongs to on the first line and no matching group on the second. A bad result omits the group, or lists it on the Deny line. The page does not show the output format, and entries may appear as names or SIDs.
If the target is part of a collection, in Server Manager open Remote Desktop Services, then Collections, then the collection, and read the User Group item in Properties. For a RemoteApp program, right-click it and choose Edit Properties, then User Assignment.
Example (illustrative): rds01 sits in a CONTOSO OU whose GPO "RDS Hosts" sets Allow log on through Remote Desktop Services to CONTOSO\Domain Admins only. The local group Remote Desktop Users on rds01 holds CONTOSO\Sales-RDS, which has 38 members. After a policy refresh, all 38 receive the message because the GPO's list wins over the local setting. Three servers share the GPO, so 3 x 38 = 114 user-and-server combinations are affected. The fix is to add CONTOSO\Sales-RDS to the GPO's Allow list, not to edit each server.
Fix
Fix the cause the checks found, and change only that.
User missing from the group. On a domain-joined member server, add the user or a group to Remote Desktop Users. For a local change, Microsoft's page names the Local Users and Groups tool (lusrmgr.msc). In PowerShell, Add-LocalGroupMember takes a -Group and a -Member, and Microsoft's example shows a domain group written as CONTOSO\Domain Admins.
Add-LocalGroupMember -Group "Remote Desktop Users" -Member "CONTOSO\Sales-RDS"
Disruptive step: this grants Remote Desktop sign-in on that server. Microsoft warns that on a Session Host running in Application Server mode, only users who need access should belong to Remote Desktop Users, because the group holds the right by default. To back out, remove the member in the Local Users and Groups tool.
GPO list omits the group. In the Group Policy Management Editor, go to the Allow log on through Remote Desktop Services setting in the GPO that the report named, and add the group, or add the user to a group already listed.
Disruptive step: editing a GPO changes every computer in its scope. Note the full current list before editing. To back out, put the original list back. Microsoft's policy pages say the change applies at the account's next sign-in.
Group in the Deny list. Remove the account's group from the Deny setting only if that group was added by mistake. Microsoft describes the countermeasure as assigning Deny to the built-in local guest account and all service accounts, and warns that a Deny entry on a group that includes real administrators blocks them.
Disruptive step: removing a Deny entry opens remote sign-in to everyone in that group. There is no undo other than re-adding the entry, so confirm with the policy's owner first.
Collection or app assignment. Add the user to a group already listed, or add a group in Tasks, Edit Properties, User Groups. For one app, use its User Assignment page.
Disruptive step: adding a group to a collection, or to an app's User Assignment, grants every member of that group access to the collection or app. Note the current list first. To back out, remove the group again from the same list, and check that nobody who needs access is removed with it.
SAM restriction. If the "Restrict clients allowed to make remote calls to SAM" policy is on, Microsoft's page refers you to the policy article, which describes an audit-only mode for testing.
After a GPO edit, gpupdate /target:computer /force on the server applies it immediately.
Risk: gpupdate /target:computer /force reapplies all computer policy settings, not only the changed ones. Run it on one server first. There is no undo, but it applies the same policy the server would receive anyway.
Confirm the fix
Have the user sign in again, because Microsoft says a user-rights change becomes effective the next time the account signs in. Run gpresult /h again and check that the Allow entry now lists the group and that the Deny entry does not. Test with one account before announcing the change to the group.
If the same message returns after the refresh, a different GPO is winning. Read the Winning GPO name again and edit that one.
What to watch afterwards
- Manage access through the Remote Desktop Users group, as Microsoft's best-practice note advises, rather than adding single accounts to the policy.
- After any new GPO is linked to the OU, repeat the resultant policy check on one server.
- Keep Deny entries narrow. A Deny entry on a broad group can lock out administrators.
Read next
Related articles you may want next.
- Troubleshooting"Remote Desktop can't connect to the remote computer": work from the listener outwardsRemote Desktop says it can't connect for one of three reasons and gives no clue which. Check the server is running, prove the RDP listener is up, test the network path and port, then check what else is on port 3389.Read article
- TroubleshootingRemote Desktop "An internal error has occurred": certificate, security layer and service checksA direct Remote Desktop connection fails with "An internal error has occurred" before or after you enter credentials. Rule out the network, test the security negotiation, then check the server's Remote Desktop certificate, key permissions and listener.Read article
- Troubleshooting"This could be due to CredSSP encryption oracle remediation": update both ends instead of lowering the policyRemote Desktop fails with "An authentication error has occurred" and a CredSSP encryption oracle remediation message. Find which end is missing the CredSSP update or a restart, fix it there, and keep the Encryption Oracle Remediation policy at a safe setting.Read article
Risks and limits
These commands have not been run or lab-tested. The Allow and Deny pages are Windows 10 and Windows 11 policy pages that carry tables for servers and domain controllers, and their text shows no differences for other server versions. The RDS troubleshooting page states its scope as Windows Server 2012 and later.
The troubleshooting page also says that only members of Domain Admins can use RDP to a domain controller, while the policy page lists Administrators as the default holder of the Allow right on domain controllers. These statements are not reconciled on either page, so check the effective right on your own domain controllers. Giving ordinary users the right on a domain controller is a security decision, because any account with the right can reach the device's sign-in screen.
Sources
- Troubleshooting access denied and user not authorized issues in RDS — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
- Allow log on through Remote Desktop Services — Microsoft Learn, page dated 2017-04-19, accessed 18 November 2026
- Deny log on through Remote Desktop Services — Microsoft Learn, page dated 2017-04-19, accessed 18 November 2026
- General Remote Desktop connection troubleshooting — Microsoft Learn, page dated 2026-02-12, accessed 18 November 2026
- secedit export — Microsoft Learn, page dated 2024-02-16, accessed 18 November 2026
- gpresult — Microsoft Learn, page dated 2024-11-01, accessed 18 November 2026
- gpupdate — Microsoft Learn, page dated 2023-02-03, accessed 18 November 2026
- Get-LocalGroupMember — Microsoft Learn, date not shown, accessed 18 November 2026
- Add-LocalGroupMember — Microsoft Learn, date not shown, accessed 18 November 2026
This article was originally published on .