Fix you need the right to sign in through Remote Desktop Services
Remote Desktop Protocol (RDP) is a Microsoft protocol that enables users to connect to and control a a PC remotely. It does this by providing a graphical interface that enables interaction as if the user were physically present. In this article, we shall discuss the steps to fix you need the right to sign in through Remote Desktop Services. Please, see How to Grant Local Admin Permissions to a Group [Part 1], and How to Grant Local Admin Permissions to a Group [Part 1].
The below error implies that the user account you are trying to use for a Remote Desktop (RDP) connection doesn’t have permission to log in via Remote Desktop Services on the PC.
To sign in remotely, you need the right to sign in through Remote Desktop Services. By default, members of the Remote Desktop Users group have this right. If the group you’re in doesn’t have this right, or if the right has been removed from the Remote Desktop Users group, you need to be granted this right manually
Also, see “Is RDP enabled? Enable and disable Remote Desktop in Windows 10 for all users or selected users“. Here is how to set Pleasant User Group Permission and User Access, and Log Off: How to sign out of Windows Server 2012.
Grant Standard Domain Users Access to RDP
To grant a user RDP (Remote Desktop Protocol) access. You will need to enable Remote Desktop on the target computer. Then, add the user to the “Remote Desktop Users” group or local GPO policy.
By default, only members of the Administrators and Remote Desktop User Groups have RDP access.
Therefore, you will be able to fix this issue locally if you explicitly add the user to the Remote Desktop Users group or add the users directly to the “Allow logon through remote desktop services”.
Via the Local Group Policy
In a follow-up guide, I’ll show you how to fix this issue by configuring the appropriate domain Group Policy settings
To fix this issue locally on the device and not from the domain. Login locally to the PC with the Administrator’s account.
Search for GPO or gpedit.msc and click on open.
Navigate to Computer Configuration, Windows Settings, Security Settings, Local Policies, and User Rights Assignment.
Next, double click on “Allow log on through Remote Desktop Services” and click on Add users.
Now add the desired users or groups.
Click on OK to complete this step.
Apply the new group policy settings with the following command “gpupdate” or gpupdate /force.
Alternatively, you will need to log out of the local administrator account as shown below. Then, sign in with one of the user account you have just added.
Please, see How to fix “Unable to Sign In: Domain Not Available”, and “How to fix Remote Desktop can’t connect to the remote computer for one of these reasons“
Via the Local Users and Groups (lusrmgr.msc)
As discussed above, you could also add the users to the Remote Desktop User Group.
In Windows, there are numerous ways to launch the Computer Management Console. Here, you should simply type computer management in the search window and click open as shown below.
Navigate to Local Users and Groups, expand Local Users and Groups and click on Groups. Next, locate the Remote Desktop Users and add the desired users by clicking on the add button, as shown below. When done, click on OK.
Please, see the Full Integration Guide on how to Add Nutanix AHV to Veeam, and “Guide to Remote Desktop Connection Properties for Secure Access“. Also, see BitLocker behavior when MBAM agent is removed: No Uninstall Option in Control Panel.
Via the”Remote Desktop Users” Group
If you wish to use this method, simply login as a local administrator or a domain user account on the device and launch the “SystemPropertiesRemote” and press Enter. There are different ways to initiate this window also in Windows.
Under Remote Desktop, click Select Users and add your desired users.
When complete, click on OK.
I hope you found this article on how to fix you need the right to sign in through Remote Desktop Services very useful. Please, feel free to leave a comment below.
