In plain English what does "Startup policy processing wait time" mean???

[kennysarmy]

Had some problems with new fast (w/ SSD's) computers not applying software install policies.

 

When I set the Startup policy processing wait time to 20 seconds all was fine...

 

Read a few forums that this was the fix but I need to know as the explanations were not clear exactly what Startup policy processing wait time does.

 

Thanks

[plexer]

It's a delay time before processing the startup side of any group policy.

 

Ben

[Hedghog]

If I remember correctly the wait time is there to allow the policy to completley down load before it is processed. There is a danger that if the policy has not fully downloaded when processing sarts you will be left with an incomplete policy or at worst the policy will fail altogether. I do think though that this was related to network issues rather than PC issues. I suppose that if you have a very fast PC and a slow network this work make the situation worse.

[kennysarmy]

What I don't understand is if the default wait time (which I think it is for win7) is 30 seconds, how shortening the time makes the policies apply, I would have thought giving a longer time would be necessary so I am slightly confused....*again!

[sparkeh]

What I don't understand is if the default wait time (which I think it is for win7) is 30 seconds, how shortening the time makes the policies apply, I would have thought giving a longer time would be necessary so I am slightly confused....*again!

Shortening it doesn't help, it makes it worse.

You need to make it longer.

Windows 7 Clients intermittently fail to apply group policy at startup

The value specified should be sufficiently long enough to ensure that the connection is made. During the timeout period, Windows will check the connection status every two seconds and will continue with system startup as soon as the connection is confirmed. Therefore, erring on the high side is recommended. But be advised, if the system is legitimately disconnected (i.e., disconnected network cable, off-line server, etc), Windows will stall for the entire timeout period.

[kennysarmy]

That's what I thought but setting it to 20 seconds solved my issue:

 

And here also:

Group Policy software installation fails to install on Windows 7

Check the last posts by users "btenney" and "FDDCH"

[Manny21555]

Hi All,

 

We have a similar issue here - can i ask what policies you had issues with?

 

We also installed some new SSD's this summer (also upgraded RAM) and since then one policy does not apply (internet settings), the fix i have for short term is to run a gpupdate /force when this happens (a teacher or student will log on and receive no IE settings, after the gpupdate all is fine until the next student/teacher logs on - sometimes it wont happen for a while and then the next day it will be each person that logs onto that PC).

 

Also i have found 2 gpo's that might help (i'm testing one now) both of Computer policies. 1) Always wait for the network at computer startup and logon 2) Specify a startup policy process wait time (same one you are using but i haven't tested this yet).

 

I was thinking what else could be the issue and it might be the network card inside the pc, not having enoufh mbps? or if you have a "link" (pc to phone to rj45 connection on the wall) it could be any of them that has the issue.

 

Could you guys help? In principle you have the same issue as we do...

 

Cheers,

Manny

[snagrat]

I know he default is 30 seconds but I've had it before where I had to set the value to 30 rather than relying on it.

 

Did you actually try setting value to 30?

[Oaktech]

It's weird isn't it!

 

I was having a problem where the PC was just skipping over applying software intall GPOs. I changed the Policy to 10 seconds and it all began to apply...

[kennysarmy]

Good 'ole Microsoft....

 

I can't add any more to the thread than my previous posts I'm afraid....

[Manny21555]

I haven't tested the policy (set time one) just yet as i said in the previous thread i am testing the always wait for the network at computer startup and logon.

 

You think its worth a shot enabling both and using a set time to 20 or 30 seconds?

 

Cheers,

Manny

[Mustang]

30 seconds is not the default although this is the default when you configure the policy and if you read the description of the policy.

 

Here is the official wording.

"if neither manual or group policy setting has been defined then the value is picked from the following registry location:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History

 

Since there is no time out period defined, the system now uses its own algorithm to calculate and arrive at an Average time out period and this value is stored in the above registry location. This could vary system to system and depends on various factors like previous login attempts. "

[Manny21555]

Hi All,

 

Just a quick update on whats happened within our network I have found a fix for my GPO settings

 

I found this guide online & followed the registry steps:

 

How to apply “The content of IE Settings” in GPO (which used IEM (IE Maintenance) before IE10) to IE10+ Version since IEM have been deprecated from IE10 - AsiaTech: Microsoft APGC Internet Developer Support Team - Site Home - MSDN Blogs

 

Thanks for the guidance!

 

Manny