Prevent Active Directory group policy getting applied

I would like to know whats the options possilbe in preventing AD Group Policy getting applied to a computer or user.

The reason is we have few users who is having local admin rights on the machine and they are removing Domain Administrators from Local admin group. I am running a login script as part of GPO to add the Domain Admin back to the local admin group everytime they login and i know that its failing. For Group Policy everything else is fine, like networking OU's etc.

So i want to know what are the options they have to prevent GP script getting applied and work that way. Our setup is Win 2003 AD with XP SP3 and SP2 machines.


Who is Participating?

Improve company productivity with a Business Account.Sign Up

Mike KlineConnect With a Mentor Commented:
For more information about security filtering look here:
...but that is really not your issue because you want the policies to apply to the users
If they are local admin rights they can add and remove to the local machines at will.  First thing is maybe take their rights away.  They should not be doing that.
Have you thought about using restricted groups for your admin groups?
Mal OsborneAlpha GeekCommented:
Add the users to a Group, then in the security tab on the GPO properties, Tick the "deny" box under "apply group policy"  for that group.
qman2007Author Commented:
Hi Malmensa & Mike,

Thanks for your replies. But as i said in my post they are not letting the Group Policy to be executed and becuse of that i cant add Domain Administrator to Local Admin group.

Any suggestions on how users can block Group Policy Getting executed

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to and use offer code ‘EXPERTS’ to get 10% off your first purchase.

Frank McCourryV.P. Holland Computers, Inc.Commented:
Go back to your policy in Group Policy Manager and make sure it is "Enforced"
Mike KlineCommented:
How do you know they are not letting it execute?  It could execute then they could just go remove the Domain Admin group.  The script won't run again
Frank McCourryV.P. Holland Computers, Inc.Commented:
Create a Policy that defines your users in the policy instead of using the script.  The policy need to have these settings:
Computer Configuration
      Windows Settings
            Security Settings
                Restricted Groups
Under restricted Groups add "Administrators"  Right click on the group and the properties.  Add the domain accounts that need administrator access and remove any that don't.

Save the policy, apply it to the OU and set it to enforced.  use gpupdate /force /wait:0 to apply it immediatly.  Users will have to log off then back on for it to take effect, but then you won't have to worry about it again.

BTW you can do this with power users and other groups too.

qman2007Author Commented:
Hi Guys,

Thanks for your replies. The problem is my Group Policies are not getting applied.

Mike, you asked me how do i know that policies are not getting applied. I checked on 1 - 2 machines and found that its not applied. What i mainly want to know is, is there a way in Windows XP where a user can stop Group Policy getting applied eventhough he logs to domain.


you can do a gpupdate /force on the windows client to force it to refresh the policy locally otherwise you may not  be waiting long enough time interval for syncronization? Some policies would force a logoff and logon to fully take affect but you should be notified when running this command from a prompt.
Frank McCourryV.P. Holland Computers, Inc.Commented:
If a policy is not being applied, it most likely not caused by anything the user is doing.  The whole purpose of policies it to force settings that the users cannot change.  If they are not being applied, it is because of a security error, possibly because the computer SID does not match or because of a networking problem such as the time on the server is drastically different from the PC's.  

As techexperts said, you may not be waiting long enough for synchronization to occur.  Just to add to his comment, if you add the /Wait:0 to the gpupdate command you will not have to wait.  the full command would be gpupdate /force /wait:0.  the caveat is that this has to be run from each workstation, which may take you longer than 15 minutes anyway.  You could put it in their logon script however.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.