Why does this happen?

Problem: Boot GPO's fail to run.
Solution: MS has a reg fix, to make the GPO implementation wait until the network initialization completes.
https://support.microsoft.com/en-us/kb/2421599

I am having a discussion with a coworker, and the question is "Why is this happening?"  and how would I do further investigation on "Exactly what is going on?"

Note: Spanning tree on the switch is enabled, this is network wide, and there are no network errors.
LVL 11
loftywormAsked:
Who is Participating?
 
loftywormConnect With a Mentor Author Commented:
SO, I want to close this up.
This is not a spanning tree issue or even a switch issue.  I believe (70%) that this is a AV Symantec issue.  In essence, there is a 3rd party program that is controlling the network connection.  In this case the Symantec Firewall.  This is where the delay is coming from. I have past the political hurtle and am moving forward with the fix I originally stated.  TY all for you assistance.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you force a GPO update on the Client, does it give you any error messages ?

have you also looked at the event logs on the DCs and Workstations ?
0
 
loftywormAuthor Commented:
1) no error messages after boot.  the gpupdate /force works with no issues (because the network is up and all is working)
2) there is an event in the boot up event logs, that match the KB from MS, the GPO failed to run

One more addition as will, an updated Network driver (all drivers) has no effect (and flash of all bios)
Another symptom can be seen, when you login right away, the network drives all have that red X, but go away when you navigate them, again pointing at the network.

Perhaps I should look more closely at the spanning tree???  Could the network be holding up the NIC from starting?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
GPO updates are working, and being applied to all workstations correctly ?

it's just this update which is not working ?

do you have a different network interface or switch to try ?
0
 
loftywormAuthor Commented:
1) no they are not.  there are some specific boot GPO's that will not run.

No I don't.

But I think the issue is being missed.  I know how to fix it.  The question is why is this happening?
I am getting some beurocractic blowback, and I need to say "because this and this log says so", or something to that effect.  The windows event log shows there is an error, but not why the network card is not booting as fast as the OS.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Sorry, I'm a little confused, do GPO updates work in your organisation, ANY?

lets just park this specific update.
0
 
giltjrConnect With a Mentor Commented:
... "but not why the network card is not booting as fast as the OS. "

The OS must get up and running before it can set the network settings for the network card to use.  So the OS will be up and running prior to the network card.

How are the switch ports configured?  Access, trunk, or dynamic?  Are the switch port/network card configured as fixed speed/fixed duplex or learn?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
We experience this, with MDT deployments, on our new i7 Desktops, MDT BOOTS so fast, the network interface has not initialized, and therefore fails obtaining a DHCP lease, and MDT has already booted, and trying to map to Network Share. if we then wait 60 seconds, and hit Retry it works, but this does not help, as PXE/MDT deployments are supposed to be automatic!....

and this was with an Intel Network Interface on the motherboard, if we switched to the RealTek, it solved the issue for us!

Motherboard has two nics, strangely an Intel and Realtek, this is on a customer site, which has HPE networking.
0
 
Craig BeckConnect With a Mentor Commented:
Spanning tree on the switch is enabled, this is network wide, and there are no network errors.

In Cisco-speak, we enable spanning-tree portfast to enable the port to forward frames instantly.  If STP is enabled and portfast isn't enabled, the device won't be able to pass any traffic for around 30s after the link is established.  This is why the wait for network GPO needs to be applied.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
no firewalls here on our workstations, and it happens!
0
 
Craig BeckCommented:
Check portfast, Andrew :-)
0
 
loftywormAuthor Commented:
solution found
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.