We have just had a new batch of computers that have come in with 2.6 dual core processors and 2 gig ram and a 1 gig network card from stone and they are that fast that the computers process the os startup so fast that group policy does not get applied and you get event ID 5719 and event ID 1054 errors on the event log.
After a lot of playing and talking to other technicians and a senior stone engineer I have found this solution that works.
Group Policy may not install the PolicyMaker Software Update client on a Windows XP Service Pack 2-based computer, and event ID 5719 and event ID 1054 are logged
ive found on occasion intel cards connected to hp switches do this. Flash the hp switch to a newer version problem often goes away or making the pc wait longer with the following reg file has solved similar problems for me in the past
Code:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "GpNetworkStartTimeoutPolicyValue"=dword:0000003c
I dont have hp switches but the registry setting looks like the one used in the Microsoft article.
You would have thought that microsoft would have thought and prepared for this.
What network cards do you have? Are they upto date with the drivers?
have you go tthe group policy enabled that waits for the network on startup?
They are an intel pro 1 gig and yes they have the latest drivers. I have tried older driver but they do the same.
Where is the setting in group policy and I will check?
There might be a local policy at work here. Fire up gpedit.msc and check on:
Computer Configuration\Administrative Templates\System\Logon
There should be an option to "Always wait for network on computer startup/shutdown"
We got shed loads of Dell Optiplex 760's shipped to us this school year and had nothing but trouble with the 1Gb Intel NIC in these machines. The problem I eventually drilled down to after trying every fix here and on Google was DHCP Media Sensing. The nic driver was resetting the card during bootup and that resulted in the machine not knowing a lick about any GPO's.
The link to the MSKB article is below as well as the registry fix.
How to disable the Media Sensing feature for TCP/IP in Windows
Code:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] "DisableDHCPMediaSense"=dword:00000001
There are currently 1 users browsing this thread. (0 members and 1 guests)