Windows Forum

Ask something
Discussion Locked

Policies for Terminal Services

0 helpful
3 replies

by nateh 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi all,

I have a small client that is running Win2003 Server with Terminal Services on one machine. They have 10 thin winterm clients attached to that machine and all is running well.

My issue is in how to create group policies for the Winterm clients without affecting the Admin account on the server.

I want to limit what the clients can do (these are public terminals), but what I am finding is that any policy I set also limits the Admin account since this is not a "domain". I can't seem to limit the policies to the clients only.

So, for instance, in the Local Computer Policy, I restricted access to the Control Panel. But now the Admin account can't get to it either.

Is there a way to "unrestrict" only the Admin account?

3 replies

by cg it

normally, what you would do is create an OU, collect either users or computers into that OU, create a group policy object [a GP] then attach that GP to the OU.

non domain GP is usually associated on a per machine basis when you

by cg it

normally, what you would do is create an OU, collect either users or computers into that OU, create a group policy object [a GP] then attach that GP to the OU.

non domain GP is usually associated on a per machine basis when you

by cg it

have a workgroup. Since this is neither one, you would create a OU on the server, collect the user accounts [use a security user group instead of individual]on the server into the OU, create a GPO [not using the default local machine GP] and assign the GPO to the OU. you do not collect the admin security group into the OU.

The GP is applied as local, site domain and OU. in this case the local GP will be applied then the OU will be applied.

This discussion is closed to new replies.