Group Policy not filtering down

Morning!!,

OK checked all of those and all OK:

scope = applied to student user group, sec filtering = authenticated users, wmi filtering = none.

both users and computer config enabled

linked GPO - OK and enforced
gp inheritance = 1=pupils 2= default domain policy.

Any other ideas?

cheers

Manick

Morning.

I will not be beat on this one :wink:

Have the machines that are not applying the policy been imaged recently?

About 3 months ago they were!!, I've been fiddling with policies since then, trying to lock the school down!!!

Cheers

manick

P.S. I'm glad you won't be beat one this one, me neither, I'm googling my ass off, looking for this RPC server error!

RPC error usually means the PC is turned off or it's firewalled.

Quote:

---

Originally Posted by Geoff

RPC error usually means the PC is turned off or it's firewalled.

---

Very good point Geoff. Are you using the windows firewall?

Lo.

yes firewall is running, but having just compared machines that are working against those that aren't, there isn't any difference between the exceptions apart from RemoteExec is allowed on those that are picking up GP (or appear to be).

Bit of confusion here though, earlier someone said that the pupils policy should show in both computer config and user config, however it isn't showing in computer config, but is applying all the settings???

manick

If there are no computer settings in the pupils GPO then it'll be skipped.

Just a thought but how many DC's do you have in the domain. I had a nightmare with GPO not applying on some PC's a while back and it turned out to be a screwed sysvol folder on one of the DC's and replication was not functioning.

I am sure I had the same RPC error on the client.

I've made quite a few changes in the computer config part of the pupils gpo, but they haven't taken on around half of the machines.


manick

I've made quite a few changes in the computer config part of the pupils gpo, but they haven't taken on around half of the machines.

We have two DCs, I'll look into the Sysvol idea.


manick

Its a long shot but we are running out of ideas. What was happening at the client's site was some of the clients were not getting updated GPO settings these were obtaining GPO from the stuffed DC that wasn't replicating and generating RPC errors.

Let us know how you get on

You can use Sonar to troubleshoot and search replication problems.

http://www.microsoft.com/downloads/d...DisplayLang=en

Hi again,

here is the state of play, replication Ok, firewalls OK.

It looks like the policy isn't set right somewhere, but I don't know where. I copied the policy and set up a new user and put them in their own group used the policy, this works fine, but the original group doesn't.

I'll nail it one way or the other.

manick

Since it works with a new user I have another thought. Have you tried deleting the test users profile on the client?

Yup afraid so!! still no joy.!!

manick