Laptops not picking up new OU

[witch]

I am slowly upgrading our yoga laptops to Office 2016. I have created an OU that will install Office 2016 and in most cases,when I move the laptop into the OU, all works fine.

But I have several laptops that just won't play. I have gpudated them, taken them off the domain and put them back, and even changed their names in some cases, with no luck at all. I have them on AC power, and with or without an ethernet connection.

Occassionally, after the nth reboot, one will pick up the OU. Can anyone think of how to get this to happen a bit quicker, or give me an insight into why it isn't happening?

thanks

[newpersn]

Event log? Anything about it after a GPupdate /force?

[sted]

do you have them set to always wait for network in group policy (local or domain) and sometimes esp with ssd pcs you need to extend even that of the pcs gives up looking for policies too soon

[witch]

the event logs are showing that the laptops in question aren't picking up all the policies. But I have no idea why it would affect around 6 of the 70 we have, all of which are identical.

I even re-imaged one and it still won't do it

[Tefters]

Windows 8.1 or 10 on the off chance? Computer GPO as well?

Had this issue ever since Windows 8 and it p*sses me off no end, PC's not picking up Computer GPO's properly, if you leave it on for about 2 hours, then restart it your usually lucky and it manages to get the GPO eventually yet it's sporadic and very random.

 

In my case it's usually default app associations as a computer GPO. Some machines get it and some don't. The ones that don't I leave for an hour then go reboot and voila!

Great when URL links open in bloody edge when you know your GPO should be setting IE.

Edited September 20, 2016 by Tefters

[witch]

8.1

[sted]

try adding/editing this to the registry of an affected pc it should make it wait up to 60 seconds before it gives up looking for a network

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "GpNetworkStartTimeoutPolicyValue"=dword:00000019

[3s-gtech]

This can be done in Group Policy - Computer Configuration | Administrative Templates | System | Group Policy | Specify startup policy processing wait time

[sted]

This can be done in Group Policy - Computer Configuration | Administrative Templates | System | Group Policy | Specify startup policy processing wait time

I find it better to set in the registry as if the pc isn't picking up polices in the 1st place it wont find that setting that might help either

[3s-gtech]

True of course - but often these policies will be picked up when the machine does a normal background refresh and applied then. Startup scripts and MSI installers are not applied during a background refresh though, so in theory this should help after another restart. I have just implemented it myself to try to help the same issue - my Office 2013 install script is flaky on laptops, but reliable when wired. I also have some logon issues in one part of the school that this may help.

[witch]

I'll try it

but.....why do the other 60 odd pick up the stuff fine?????

[pete]

Drivers with terrible power saving implementations on the network interfaces (both wired and wireless)? Especially if there's Realtek in them.

 

Turn off WiFi and Ethernet power saving options, see if a gpupdate becomes more reliable. If it does, hunt for better drivers, possibly on the ethernet adaptor manufacturer's website.

[mukz]

This has worked for us on a similar issue:

 

1) move laptop to computers ou where no gpo applied

2) gpupdate /force /boot that damn thing!

3) move into correct ou again

4) gpupdate /force /boot that damn thing one more time

5) hopefully should be voila!

 

If all else fails i usually reimage!

[sted]

I'll try it

but.....why do the other 60 odd pick up the stuff fine?????

 

look at it this way if it was always predictable and always worked you wouldnt have a job lol