|
If you would like to speak with one of our engineers, please Submit a Question or give us a call at the phone number here. In North America, To route your phone support request directly to a technical support engineer, call toll-free 1-888-382-1583 or 1-440-646-3434, select Option 3 (Technical Support), then select Option 5 (More Options). When prompted, enter the ThinManager Direct Dial Code 201. |
Difference between revisions of "Allow log on through Terminal Services"
(Created page with "http://scorpiotek.com/blog/?p=742 How to grant ‘Allow log on through Terminal Services Right’ To log on to this remote computer, you must be granted the Allow log on thro...") |
|||
| Line 4: | Line 4: | ||
To log on to this remote computer, you must be granted the Allow log on through Terminal Services right. By default, members of the Remote Destop Users group have this right. If you are not a member of the Remote Desktop Users group or another group that has this right, or if the Remote Desktop User group does not have ths right, you must be granted this right manually. | To log on to this remote computer, you must be granted the Allow log on through Terminal Services right. By default, members of the Remote Destop Users group have this right. If you are not a member of the Remote Desktop Users group or another group that has this right, or if the Remote Desktop User group does not have ths right, you must be granted this right manually. | ||
| − | I was setting up remote access for a user on a domain controller for some tests. This user was not an admin (but belonged to the Remote Desktop Users) and kept getting the same error message above. Setting this user to domain admin solved the problem, but of course I did not want to make any remote user a domain admin. | + | <BLOCKQUOTE>"I was setting up remote access for a user on a domain controller for some tests. This user was not an admin (but belonged to the Remote Desktop Users) and kept getting the same error message above. Setting this user to domain admin solved the problem, but of course I did not want to make any remote user a domain admin. <br/> |
| − | It so happens that it is not enough for a user to belongs to the Remote Desktop Users to gain the rights it needs. Here is how you fix this: | + | "It so happens that it is not enough for a user to belongs to the Remote Desktop Users to gain the rights it needs." </BLOCKQUOTE> |
| + | |||
| + | Here is how you fix this: | ||
Open gpedit.msc (the local group policy editor) | Open gpedit.msc (the local group policy editor) | ||
Revision as of 19:24, 7 November 2012
http://scorpiotek.com/blog/?p=742
How to grant ‘Allow log on through Terminal Services Right’ To log on to this remote computer, you must be granted the Allow log on through Terminal Services right. By default, members of the Remote Destop Users group have this right. If you are not a member of the Remote Desktop Users group or another group that has this right, or if the Remote Desktop User group does not have ths right, you must be granted this right manually.
"I was setting up remote access for a user on a domain controller for some tests. This user was not an admin (but belonged to the Remote Desktop Users) and kept getting the same error message above. Setting this user to domain admin solved the problem, but of course I did not want to make any remote user a domain admin.
"It so happens that it is not enough for a user to belongs to the Remote Desktop Users to gain the rights it needs."
Here is how you fix this:
Open gpedit.msc (the local group policy editor) Expand Local Computer Policy –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> User Rights Management Look for the setting on the right called Allow log on through Remote Desktop Services Double click this policy Add the user/group you would like to have remote access to the box. Once this was done, the user was able to connect w/o hassles.
