GPO does not apply on one model of computer

[netadmin]

I have three models of computers on my network presently:
-Acer Power S280
-Acer Power S285
-Acer Power FH

I am able to fully deploy GPO changes and GPO software installs on both the S285 system and FH system. However, on the S280 system (all five units from this series), I get the following error whenever I gpupdate /force or restart the computer, attempting to start the software install. It is odd though, because most of the GP settings are still applied (like folder redirection, start menu customization, etc.). It is mainly just the software install that does not work.

Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted.). Group policy processing aborted.

This is a userenv error, code 1054.

I would very GREATLY appreciate any and all advice. I would like to fix this over remote desktop this weekend, but can run commands at the physical machine on Monday, if needed.

Thanks for any advice!

[User3204]

Check the network driver version.

We had a problem with the GPOs not applying on some machines, and it turned out that the network card driver was resetting the card at the point when it was trying to contact the DCs at bootup time.

I'm not sure what the error message was, but it was similar to the one you're quoting. Our policy would apply if we did the "gpupdate /force".

[bishopsgarthstockton]

thats an intresting error. if that dosent work, i would probably try reconnecting them to the domain..

very strange

[FN-GM]

its not a dodgy image is it?

[netadmin]

I'll be looking for a new network driver.

I did try removing the machines from the domain, then rejoining. No luck

This is the same image I used on the 285 and FH, so it should be ok.

Good thoughts. Let me know if you think of any other ideas.

[FN-GM]

have you tried using an older network card driver? Also i would try it using a PCI network card.

[leon]

Do those 3 models use the same driver? Weird that everything else works. Will the settings apply from a fresh policy?

Try deleting the OU policy association and recreating it. Occasionally I get something that doesn't apply properly, and that's sorted it in the past. Admittedly that's when it's not applying to everything...

[Iain]

Sounds like the group policy is timing out before the network adaptor has finished initializing. Take a look in the Userenv.log logfile for any specific errors. You could try increasing the time windows will wait while trying to apply group policy by adding a DWORD registry entry GpNetworkStartTimeoutPolicyValue to the key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon

or

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System

The value of this entry defines the number of seconds windows will wait before timing out when trying to apply group policy.

For more detailed information take a look at KB840669. [Scroll to the bottom for XP instructions]

I had a similar problem with a batch of new laptops failing to apply group policy over a wireless connection, due to the long initialization time of the adaptors. Setting this entry fixed the probem.

Hope this is of some help,

Iain.

[netadmin]

Unfortunately, I have no extra NIC cards. I may buy one myself later, if it turns out this is needed.

Each of the 3 models use different NIC drivers. After I reimage the machine, sysprep runs and does auto driver setup. I have tried reinstalling the driver on these, and it does not make a difference.

I increased the GpNetworkStartTimeoutPolicyValue and am now getting a different error. I'm guessing this might be good??

I attached a screenshot of the error. I also turned on debug mode for userenv and attached the log. All the restarts after GpNetwork... were around 10:10-10:17AM, so some of the other log entries may be from awhile back.

If anyone has thoughts, let me know, please. Thank you!

[FN-GM]

can you do gpupdate?

[ajbritton]

Had a GP problem on Viglen PCs. Problem was driver for the SIS900 chipset. I reverted to the driver supplied with XP and the problem went away.

[ianniow]

I had a problem with gp and made the following change in the registry
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters]
"DisableDHCPMediaSense"=dword:00000001
That did the trick
Can't remember where I found that though

[Geoff]

Can't remember where I found that though

TechNet?

[Shuriken1]

I know this is a years old thread but just wanted to put my thanks on it. The GpNetworkStartTimeoutPolicyValue reg fix sorted this problem for me where plenty of googles and microsoft kb browsing didn't so thank you.

Here is the adm file I created to apply this reg change across my domain (first time of making an adm so excuse any mistakes, seems to work though):

CLASS MACHINE
CATEGORY "Windows Customizations"
KEYNAME "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"
POLICY "Set GpNetworkStartTimeoutPolicyValue"
PART !!NetworkStartTimeout     NUMERIC REQUIRED SPIN 1
     DEFAULT 60
     MAX    600
     MIN    30
     VALUENAME "GpNetworkStartTimeoutPolicyValue"
END PART
PART !!Description TEXT END PART
END POLICY
END CATEGORY

[strings]
NetworkStartTimeout="Network Start Timeout (seconds):"
Description="Use this to change the Timeout delay when computers start up."

Thanks again,

Shuriken1.

[ricki]

Hi

I know this will sound daft but did you ghost these machines. If you did did you do a sysprep or a new sid before joining them to the domain.

Richard