GPO not being applied

  • Thread starter Thread starter Climberpm
  • Start date Start date
C

Climberpm

I've created a GPO and linked it to an OU, added a user group to the
Security Filter but it isn't being applied. I have a Default Domain policy
and a different user group policy that are being applied but for some reason
this newly created policy is not.

I ran the Group Policy Results report and it says the same that the GPO
isn't being applied.

What else could it be ?

The policy is supposed to run a logon/logoff script when users logon to our
terminal servers. I've tried logging on locally also and the script doesn't
run then either.

Thoughts ?

Thanks

Paul
 
Hi,
I've created a GPO and linked it to an OU, added a user group to the
Security Filter but it isn't being applied.
Click to expand...

I can´t. Group Policys are only applying on User/Computerobjects.
So, if there is no User object inside the OU it cant´t work.
Security filtering only helps to decide which user object inside
the OU is filtered, but if there is no object there is still
no effect. Doesn´t matter what filter you definie, if there is no
destination there is no hit ...

Mark
 
If you want User Configuration settings in a GPO linked to an OU with
computer accounts in it to run when a user logs on to one of those computers
(e.g. Terminal Servers), enable loopback processing.

See Method 2 in http://support.microsoft.com/?kbid=260370.

You might want to use Security Filtering on the GPO to prevent the User
Configuration settings from being applied to Administrators (add check mark
to the Deny column for the domain group containing your Terminal Services
Administrators).

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.
 
Back
Top