Cannot edit Allow log on through Remote Desktop Services

Allow log on through Remote Desktop Services

Is this page helpful?

Yes No

Any additional feedback?

Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.

Submit

In this article

Applies to

  • Windows10

Describes the best practices, location, values, policy management, and security considerations for the Allow log on through Remote Desktop Services security policy setting.

30 Replies

· · ·

Cannot edit Allow log on through Remote Desktop Services

Poblano

OP

Michael9006 May 20, 2013 at 16:08 UTC

If I'm following your question correctly, I think you may need to do thefollowing:

1) Set up a group and add those users to it. (We user a group called "Remote Users."

2) Add your new Remote Users group to the Remote Desktop Users group on your terminal server.

Does that make sense?

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Poblano

OP

GrayBeard

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:11 UTC

Michael,

I will try your suggestion but I find it odd that I already have a "remote desktop users" group in AD and even though I can add users to that group I still receive the error message like they don't have permission. I have also added each user individually under the "remote settings" tab on the server.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Poblano

OP

GrayBeard

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:15 UTC

I still receive the error message "you must be granted the All logon through terminal services right"

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Jalapeno

OP

Talk Nerdy 2 Me May 20, 2013 at 16:23 UTC

Check these:

Computer management - users properties - Terminal Services Profile - Deny logon to Terminal Server.
If it is domain user, go to AD for user properties and check the same.
Secpol.msc - user rights assignments - allow logon through terminal services.

1

· · ·

Cannot edit Allow log on through Remote Desktop Services

Habanero

OP

Sean Donnelly

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:24 UTC

Check out your Group Policy in this path Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections and Enable "allow users to connect remotely by using Remote Desktop Services".

1

· · ·

Cannot edit Allow log on through Remote Desktop Services

Poblano

OP

GrayBeard

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:32 UTC

talk nerdy,

the secpol.msc allow logon option has the list of three users but the option to add users is greyed out. there seems to be another policy at work here.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Habanero

OP

Sean Donnelly

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:34 UTC

mrtimyork wrote:

talk nerdy,

the secpol.msc allow logon option has the list of three users but the option to add users is greyed out. there seems to be another policy at work here.

That would most likely be group policy, do you have RSAT installed on your PC that could allow you to access Group Policy Management Console? If on a domain I believe this will take precedence and you need to manage through this way. Otherwise if you do not you can access on your domain controller and do as listed above.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Poblano

OP

GrayBeard

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:36 UTC

Sean,

I do not see Remote desktop services, only Terminal Services

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Poblano

OP

GrayBeard

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:41 UTC

sean,

I was able to set the policy to "enable" and did a gpupdate on the server. still receiving the same error regarding the allow logon through terminal services right.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Habanero

OP

Sean Donnelly

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:41 UTC

That should be it if under Windows 2003 domain

Computer Configuration, Administrative Templates, Windows Components, Terminal Services, double-click the Allow users to connect remotely using Terminal Services = Enabled

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Jalapeno

OP

Talk Nerdy 2 Me May 20, 2013 at 16:49 UTC

mrtimyork wrote:

talk nerdy,

the secpol.msc allow logon option has the list of three users but the option to add users is greyed out. there seems to be another policy at work here.

Are you on a domain?

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Habanero

OP

Sean Donnelly

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:52 UTC

Try to do a gpupdate /force to do a background and foreground refresh and then try using RDC to the server.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Poblano

OP

GrayBeard

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 16:55 UTC

yes

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Jalapeno

OP

Talk Nerdy 2 Me May 20, 2013 at 17:01 UTC

OK then you need to make these changes at the domain level. Let me be more specific so we know we are in the right place.


Open gpedit.msc

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.

Also, keep in mind that users will not be allowed to Remote Desktop to a domain controller. Only Administrators can do this. This is by design. If you need to get around this, I may be able to help you.


You can also control this Local Group by using Group Policy restricted groups feature.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Poblano

OP

GrayBeard

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 17:07 UTC

talk nerdy,

I am there but "add user or group" is still greyed out. i see two additional users listed her besides the administrator and i need to add two more.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Jalapeno

OP

Talk Nerdy 2 Me May 20, 2013 at 17:12 UTC

Are you on the domain controller?

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Jalapeno

OP

Talk Nerdy 2 Me May 20, 2013 at 17:17 UTC

Run "rsop.msc" on the Terminal Server. Then change the "Allow log through terminal services" settings.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Ghost Chili

OP

Semicolon

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 17:24 UTC

If the option is greyed out it is most likely because a group policy has been applied to the server whereby remote desktop users is a restricted group for which membership can only be controlled in that group policy.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Jalapeno

OP

Talk Nerdy 2 Me May 20, 2013 at 17:27 UTC

Exactly. If you use RSOP.msc the "Precedence" TAB will tell you which policy you need to edit.

1

· · ·

Cannot edit Allow log on through Remote Desktop Services

Habanero

OP

Sean Donnelly

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 17:29 UTC

Can we check something to see if your policy is being applied on the server? Go into regedit on the affected server and then locate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server and then the DWORD value of fDenyTSConnections, to enable it should be set 0 to deny it should be 1, what do you see?

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Jalapeno

OP

Talk Nerdy 2 Me May 20, 2013 at 17:29 UTC

It should in most cases be "Default Domain Controllers" policy. This may differ if you have created a custom policy or if you have a dedicated Terminal services server, which is probably best practice but not the most common. Most 2008 networks have the Domain controller configured as the primary services provider for just about every service including Terminal services.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Jalapeno

OP

Talk Nerdy 2 Me May 20, 2013 at 17:32 UTC

SeanMD wrote:

Can we check something to see if your policy is being applied on the server? Go into regedit on the affected server and then locate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server and then the DWORD value of fDenyTSConnections, to enable it should be set 0 to deny it should be 1, what do you see?

He hasn't gotten that far yet. He is still unable to add the users he needs to the allow logon policy. This is likely due to attempting to edit the policy on the local machine instead of the terminal server or from a custom GPO instead of the default one for that server.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Ghost Chili

OP

Semicolon

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 17:33 UTC

SeanMD wrote:

Can we check something to see if your policy is being applied on the server? Go into regedit on the affected server and then locate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server and then the DWORD value of fDenyTSConnections, to enable it should be set 0 to deny it should be 1, what do you see?

It should be 0 - because he's actually getting a connection; just unable to login.

0

· · ·

Cannot edit Allow log on through Remote Desktop Services

Ghost Chili

OP

Semicolon

Cannot edit Allow log on through Remote Desktop Services

This person is a verified professional.

Verify your account to enable IT peers to see that you are a professional.

May 20, 2013 at 17:39 UTC

None of the settings referenced above are going to grey out the "add/remove" function from the local Remote Desktop Users group.

In your group policy management console, you'll want to review the Group Policy Results for the subject server. Review any configured settings in the following area:

Computer Config -> (Policies ->) Windows Settings -> Security Settings-> Restricted Groups

You should see an entry somewhere for "Remote Desktop Users," when you find this setting, you will need to add the appropriate Domain account/groups here, or un-configure the setting so that the Local Add/Remove Users/Groups box is available for selection and you can apply these restrictions on a server by server basis.

Additionally, on the server you could go into the local policy on the server in question, (gpedit.msc) and manually adjust these settings (I wouldn't recommend it, just because if it's not in the Domain GPO, somebody's going to forget about this setting)

Computer Config -> (Policies ->) Windows Settings -> Security Settings-> Local Policies -> User Rights Assignment: "Allow log on through remote desktop (terminal) services," and add the users/groups in this box.

1

  • prev
  • 1
  • 2
  • next

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Allow logon through Remote Desktop Services

In most cases the system admins prefer configure Allow logon through remote desktop services using local policy. This is done using Start > Administrator Tools > Local Security Policy > Local Policies > User Rights Assignment. Edit the policy setting “Allow log on through remote desktop services” and add the user group to allow RDP access.

Cannot edit Allow log on through Remote Desktop Services

Allow log on through Remote Desktop Services – This security setting determines which users or groups have permission to log on as a Remote Desktop Services client.

Most of all you can also achieve this by creating a new GPO and applying it to required organizational unit. I prefer using a group policy than editing local policy on domain controllers.

Cannot edit Allow log on through Remote Desktop Services

‘Allow log on through Terminal Services Right’ error message

Complete error message: “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.”

You’ll find several articles on the internet telling you to make the user a member of the Remote Desktop Users group, but that’s not the whole story. Setting the user to a domain admininstrator will solve the problem, but you may not want to give the user these permissions!

Herehowwe fixed the ‘Allow log on through Terminal Services Right’ error message:

  • Add the user to the Remote Desktop Users group by editing the ‘Member Of’ list in their Active Directory Properties:
Cannot edit Allow log on through Remote Desktop Services
Active Directory User Properties, Member Of tab
  • Click Start | Runand execute gpedit.msc (Group Policy Object Editor).
  • Expand Local Computer Policy –> Computer Configuration –> Windows Settings –> Security Settings –> Local Policies –> User Rights Management
  • Find the ‘Allow log on through Remote Desktop Services’ right.
Cannot edit Allow log on through Remote Desktop Services
Group Policy Object Editor, Allow log on through Terminal Services
  • Double click the policy to edit it, or right click and select Properties.
  • Add the User (or Group) you would like to have remote access into the box.
Cannot edit Allow log on through Remote Desktop Services
Allow log on through Terminal Services Properties
  • Click ‘Apply’ followed by ‘Ok’ and the user will now be able to log into Terminal Services.

Hope this all helps! If there’s anything we’ve missed, then please let us know and help other people log in and use Terminal Services.

Note: instructions and screenshots created from a Windows Server 2003 operating system.