schultetg
asked on
Apply Remote Desktop & Allow Log on through Terminal Services Policy
I created a group policy which I thought would add a group to the Remote Desktop Users on all servers and Allow log on through Terminal Services for group (ISADMIN). I created a new GPO (RemoteDesktopUsers-Server
1) Computer Configuration-->Policies--
Allow log on through Terminal Services = DomainName\ISADMINS
2) Computer Configuration-->Windows Components-->Remote Desktop Services-->Remote Desktop Session Host/Connectionsshow
Allow users to connect remotely using Remote Desktop Services = Enabled
3) Preferences--> Control Panel Settings --> Local Users and Groups --> Group
(Name: Remote Desktop Users (built-in))
Remote Desktop Users (built-in) (Order: 1)
Local Group
Action Update
Properties
Group name Remote Desktop Users (built-in)
Delete all member users Disabled
Delete all member groups Disabled
Add membersCORE\ISAdmin
See attached policy export.
After this policy was applied to Domain Controllers and our Servers OUs the Domain Administrator was unable to log into the DCs unless added to the ISAdmin group and only the ISAdmin security group was left or shown under the Local Policies on those domain controllers and servers. The Domain Admin could still log into the other member servers without joining the ISadmins group however.
Does this policy somehow delete or break the Adminsitrators and Remote Desktop Users Builtin groups permissions to RDP to the DCs and servers? Do I need to explicitly specify the Administrators and Remote Desktop Users built-ins in the Allow Log On Through Terminal Services and Remote Desktop Users - Local Groups?
Mixed Environment PDC = 2012DC, DCs are 2008, 2008R2 and 2003R3, Member servers are also same mix of 2012DC, 2012, 2008, 2008R2 and 2003R2. Functional Level of forest and domain is 2003. Recently Promoted 2012DC and assigned all roles.
Any help would be appreciated.
Thanks
Tom
1) Computer Configuration-->Policies--
Allow log on through Terminal Services = DomainName\ISADMINS
2) Computer Configuration-->Windows Components-->Remote Desktop Services-->Remote Desktop Session Host/Connectionsshow
Allow users to connect remotely using Remote Desktop Services = Enabled
3) Preferences--> Control Panel Settings --> Local Users and Groups --> Group
(Name: Remote Desktop Users (built-in))
Remote Desktop Users (built-in) (Order: 1)
Local Group
Action Update
Properties
Group name Remote Desktop Users (built-in)
Delete all member users Disabled
Delete all member groups Disabled
Add membersCORE\ISAdmin
See attached policy export.
After this policy was applied to Domain Controllers and our Servers OUs the Domain Administrator was unable to log into the DCs unless added to the ISAdmin group and only the ISAdmin security group was left or shown under the Local Policies on those domain controllers and servers. The Domain Admin could still log into the other member servers without joining the ISadmins group however.
Does this policy somehow delete or break the Adminsitrators and Remote Desktop Users Builtin groups permissions to RDP to the DCs and servers? Do I need to explicitly specify the Administrators and Remote Desktop Users built-ins in the Allow Log On Through Terminal Services and Remote Desktop Users - Local Groups?
Mixed Environment PDC = 2012DC, DCs are 2008, 2008R2 and 2003R3, Member servers are also same mix of 2012DC, 2012, 2008, 2008R2 and 2003R2. Functional Level of forest and domain is 2003. Recently Promoted 2012DC and assigned all roles.
Any help would be appreciated.
Thanks
Tom
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I guess I misunderstood the definition that the Administrators group and Remote Desktop users had access by default to mean it was implicit and did not need to be explicitly specified in the policy.
The reason for creating this new policy was due to an anomaly in GP: the ISAdmins group was a member of the Administrators group but one member recently added to the ISadmins group did not have remote desktop access to any servers (or DCs). When the user was added to the local remote desktop users group on DCs they obtained access to each DC, but still not able to access any other member servers. When I removed this new policy from the Servers (and Domain Controllers) OUs the user was now able to acess all member servers. It seems as though a previous policy may have been "hung up" preventing the new user from accessing these member servers (even though they were members of the Administrators group) and the policy some how reset itself after this new policy was removed, reverting back to the local policy setting (defaulting Administrators & Remote Desktop USers)...... I guess.
The reason for creating this new policy was due to an anomaly in GP: the ISAdmins group was a member of the Administrators group but one member recently added to the ISadmins group did not have remote desktop access to any servers (or DCs). When the user was added to the local remote desktop users group on DCs they obtained access to each DC, but still not able to access any other member servers. When I removed this new policy from the Servers (and Domain Controllers) OUs the user was now able to acess all member servers. It seems as though a previous policy may have been "hung up" preventing the new user from accessing these member servers (even though they were members of the Administrators group) and the policy some how reset itself after this new policy was removed, reverting back to the local policy setting (defaulting Administrators & Remote Desktop USers)...... I guess.
ASKER
I have not received a more complete explanation
Yes you need to explicitly allow administrators and domain admins the right to log on through terminal services..