Can't logon to Domain Controller through Terminal Services
hi,
because of a pending hardware maintenance on one of our domain controller i edit the "Default Domain Controller Security Policy" so that the Group Server Operators can log on through Terminal Services.
After the Maintenance successfully finished i reseted the Policy Right and set the Log on through Terminal Services Policy to the original state (not defined).
Now no one can log on through terminal services to all Domain Controllers. Even the Domain Administrators can.
Gpupdate doesn't help. I have taken this change 4 hours ago.
Thanks for your assistence.
because of a pending hardware maintenance on one of our domain controller i edit the "Default Domain Controller Security Policy" so that the Group Server Operators can log on through Terminal Services.
After the Maintenance successfully finished i reseted the Policy Right and set the Log on through Terminal Services Policy to the original state (not defined).
Now no one can log on through terminal services to all Domain Controllers. Even the Domain Administrators can.
Gpupdate doesn't help. I have taken this change 4 hours ago.
Thanks for your assistence.
DanielWillmott
Exactly which section of the policy were you modifying?
ASKER
Under
Default Domain Controller Security Policy --> Security Settings --> Local Policies --> User Rights Assignment --> Allow log on through Terminal Services
I added the Group "Server Operators"
Now I switched back to "Not Defined"
Default Domain Controller Security Policy --> Security Settings --> Local Policies --> User Rights Assignment --> Allow log on through Terminal Services
I added the Group "Server Operators"
Now I switched back to "Not Defined"
Double check on this:
For domain controller, by default, the "Domain Policy" and the "Domain Controller Policy" of the "allow log on trhough Terminal Services" are set to "Not Defined" which means only Administrator can logon remotely.
Also, by default the local policy of the Domain Controllers(if ran gpedit.msc) of the "Allow log on through Terminal Services" is open to the "Administrators" and "Domain Admins" group.
If you find any of the setting that is different then the default, then someone must have changed, either intentionally or not fully understand the different between a Domain Controller when compare to the member server.
For domain controller, by default, the "Domain Policy" and the "Domain Controller Policy" of the "allow log on trhough Terminal Services" are set to "Not Defined" which means only Administrator can logon remotely.
Also, by default the local policy of the Domain Controllers(if ran gpedit.msc) of the "Allow log on through Terminal Services" is open to the "Administrators" and "Domain Admins" group.
If you find any of the setting that is different then the default, then someone must have changed, either intentionally or not fully understand the different between a Domain Controller when compare to the member server.
User rights assigment settings tattoo. That is, if you apply a setting via a GPO, then set that GPO to 'Not Defined' (as you have), the setting actually still stays on the machine's local policy. It's doesn't revert back to a default. This isn't how it is for all policy settings but it is true for User Rights Assignments. In addition, these rights are defined locally on the DC, not via group policy (at least not by default)
Did you by any chance just add the one group into the policy? This would make ONLY that group able to log in remotely, overwriting the local policy. Now the GPO setting is not defined, the usual Domain Admins, and Administrators groups are still absent. If you want to add a group to these settings via a GPO, you have to be careful that you also include the groups/users given the right locally.
Like Americom has said, if an RSoP (rsop.msc) query tells you that no GPO is setting this policy on the machines (I think by default they shouldn't be - this is usually a local setting out of the box), then edit the local policy (gpedit.msc). Add your groups back into the policy and you should be good to go. If the RSoP shows that a GPO is defining the settings, edit this GPO.
Did you by any chance just add the one group into the policy? This would make ONLY that group able to log in remotely, overwriting the local policy. Now the GPO setting is not defined, the usual Domain Admins, and Administrators groups are still absent. If you want to add a group to these settings via a GPO, you have to be careful that you also include the groups/users given the right locally.
Like Americom has said, if an RSoP (rsop.msc) query tells you that no GPO is setting this policy on the machines (I think by default they shouldn't be - this is usually a local setting out of the box), then edit the local policy (gpedit.msc). Add your groups back into the policy and you should be good to go. If the RSoP shows that a GPO is defining the settings, edit this GPO.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.