Windows 10 waiting for network on boot

[sparkeh]

So apparently "Always wait for network at computer startup and logon" actually means "Only wait for the network at computer startup and logon if I set another policy telling you to wait for 60 seconds."

 

Computer config -> Policies -> admin templates -> system -> Group Policy -> Specify startup policy processing wait time.

 

Default is 30 seconds.

 

Some times just enabling the policy is enough to make it wait, sometimes you might actually have to specify a longer time.

(I have started this thread as an offshoot from the Annoying Things thread)

 

So we have an issue where our SSD machines boot too quickly so the NIC is not initialised, GPOs are not applied at boot and there is a NETLOGON error in the system log (can't contact domain).

 

I have the "Always wait for network at computer startup and logon" setting enabled and "Specify startup policy processing wait time" set to 60 seconds yet still the machines don't wait for the network.

 

Anyone else seeing this?!

[Sagima]

We do have them set with "wait for the network" but when they try to login they sometimes get an error about logon servers not being available which never happened with win10 but I've not got a solution yet (trying to log in again immediately usually works) Edited November 11, 2016 by Sagima
first post read as if written by a loon

[Oaktech]

This may be relevant to some people:

 

Windows 10: Group Policy fails to apply directly after boot, succeeds later - Server Fault

[snagrat]

I've had to set it to 120 seconds in one school