Understanding gpedit and gpo

  • Thread starter Thread starter icccapital
  • Start date Start date
I

icccapital

I have a more detailed question below but maybe if someone can answer this
part I can solve my problem. What is the difference between the group
policies when I right click and properties in the AD and then edit it and
when I type gpedit.msc in run? gpedit.msc has policies locked to
administrator and the other doesn't. Thanks.

We are running windows server 2003 with terminal server enabled

We have purchased software and are trying to get it running on our terminal
server for remote use. It runs fine under the administrator login but we are
having trouble with other user logins. The software has some settings that
they say need to be set, one of which is the local policy in "User Rights
Assignment". I added the user to this policy under the properties of the
computer in the AD under the gpo, but to no success. So I then started
gpedit.msc, but in here the security settings|local policy|User Rights
Assignment has a lock next to it and I can't change the same policy setting
to include this user.

I guess I am trying to figure out which policy the program might be working
under when the user logs into this server and if I need to unlock these
policies how do I do it? Thanks for the starting thoughts.
 
On Jul 13, 12:12 pm, icccapital <icccapi...@discussions.microsoft.com>
wrote:
> I have a more detailed question below but maybe if someone can answer this
> part I can solve my problem. What is the difference between the group
> policies when I right click and properties in the AD and then edit it and
> when I type gpedit.msc in run? gpedit.msc has policies locked to
> administrator and the other doesn't. Thanks.
>
> We are running windows server 2003 with terminal server enabled
>
> We have purchased software and are trying to get it running on our terminal
> server for remote use. It runs fine under the administrator login but we are
> having trouble with other user logins. The software has some settings that
> they say need to be set, one of which is the local policy in "User Rights
> Assignment". I added the user to this policy under the properties of the
> computer in the AD under the gpo, but to no success. So I then started
> gpedit.msc, but in here the security settings|local policy|User Rights
> Assignment has a lock next to it and I can't change the same policy setting
> to include this user.
>
> I guess I am trying to figure out which policy the program might be working
> under when the user logs into this server and if I need to unlock these
> policies how do I do it? Thanks for the starting thoughts.

Using gpedit.msc is editing the server's local Group Policy. These
settings are overridden by the flow of GPO's in the domain. The order
of precedence is (from lowest priority to highest priority) Local ->
Site -> Domain -> OU. Settings in local group policies that you can
change will be editable, if it isn't editable then it is being applied
at a lower level in the hierarchy explained before. Install the Group
Policy Manangement Console, it is a very nice way to see how your
GPO's are being applied throughout your domain and you can quickly see
the settings being applied by each one.
 
Back
Top