GPO for Computer Restriction Policy Stopped Working

I have a computer restriction policy defined to certain computers in an OU.  This policy has been working for months.  This policy is marked enforced.  The policy restricts these computers from using Internet Explorer (path rule C:\Program Files\Internet Explorer\IEXPLORE.EXE).  This week, the policy stopped working.  All of the computers in the OU can now use Internet Explorer.  I have verified that the policy has not changed and nothing on these computers looks any different (33 computers).

I deleted the current policy and recreated it; however this had no effect.
DeathblowAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
kristinawConnect With a Mentor Commented:
death,

check your perms on the group policy and make sure 'apply group policy' is checked as well as 'read'.

kris.
0
 
mikeleebrlaCommented:
if the OS of the clients is XP run gpresult to see if the GPOs are even being pushed down to the clients
0
 
DeathblowAuthor Commented:
GPRESULT is showing that this policy is not getting pushed the clients.  We checked this; however, this was not the case as of last week.  This problem started this week.
0
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
mikeleebrlaCommented:
well if the policy isn't being pushed to the clients then that is where you need to start,,, of course the policy will not be in effect if its not even being applied
0
 
DeathblowAuthor Commented:
That is why I asked my original question.  What may be causing this to happen?
0
 
mikeleebrlaCommented:
can you copy and paste the result of the gpresult??
0
 
wlandymoreCommented:
we had a problem like this on a DC, where something became corrupt with the OS on that machine and then the policies after that weren't applied in the right order, if at all. In this case, replication was also a problem spot.
0
 
mikeleebrlaCommented:
kristinaw is right,, that is one of the most often overlooked things when setting up GPOs,,, why they aren't turned on by default ill never know
0
 
DeathblowAuthor Commented:
This wasn't overlooked orginally because it worked for months; however, it appears that the permissions had been removed from authenticated users to apply group policy.  I'll have to do some internal research to see how that happened.  I am testing this now to see if this resolves the problem.
0
All Courses

From novice to tech pro — start learning today.