Good old 'Computer Configuration GPO not applying at startup' again

[mikkydoos]

Hey all,

 

Computer settings not applying on startup.

 

Rsop errors are:

 

Then network is not started.......

 

or

 

Core failure of group policy.....

 

 

Now, this only applyies to one particular hardware setup.

 

Any other machines I have in that OU work fine. Same software image, different hardware.

 

I'm also using the same group policy objects in other OU's which work fine.

 

'Wait for the network at startup' is enabled.

 

User config applies fine.

 

 

Motherboards are Asus H81T, i3, m-sata SSD's and 8gb RAM.

 

 

 

I've had this for ages. 3 out of 25 behave themselves, the rest don't. All setup identically, BIOS and everything.

 

Please don't post about DHCP, DNS etc etc because I've been through it with a fine fine tooth comb and it's spot on.

 

The problem isn't at the DC end. I am certain.

 

 

I am stuck. Any idea's??

Edited November 11, 2015 by mikkydoos

[sted]

try setting the network cards in one of the iffy ones to a fixed speed rather than auto negotiate (for testing id start slow and work up) ive seen it on occasion where it takes so long to negotiate a network speed the pc decides there is no network. Theres also a reg hack to make pcs wait longer before giving up but off hand cant remember what it is and iirc varies with %windows version%

[mikkydoos]

Tried. No joy.

 

Got an error in the logs that says - cannot contact a domain controller, network not available.... the GP processing errors. Net connection is there though and the user settings are applying.

[Oaktech]

Can you increase the GP processing timeout...

 

Computer config -> Admin Templates -> System -> Group Policy -> Specify startup policy processing wait time

 

Trial and error increase it until it behaves as you expect. I have mine set to 15 seconds.

[ITGuyWestMidlands]

I had this on a few asus biards in a room wherethe cat5 cabling was never tested and so some took ages to pick up an ip and were often too late. Check your wiring is straight

[mikkydoos]

I had this on a few asus biards in a room wherethe cat5 cabling was never tested and so some took ages to pick up an ip and were often too late. Check your wiring is straight

 

Wiring is fine. They're PC that replaced others over the summer. Never had a prob with the other ones.

 

Actually, the problem is a bit random. I went to one that was playing up yesterday and it rsop'd fine. Did a reboot and then error'd.

 

Most odd.