Microsoft KB Archive/933458

= 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 =

Article ID: 933458

Article Last Modified on 3/9/2007

-

APPLIES TO


 * PolicyMaker Software Update 1.0
 * PolicyMaker Software Update 2.0

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
When you try to use Group Policy to install the PolicyMaker Software Update client on a Microsoft Windows XP Service Pack 2 (SP2)-based computer, Group Policy may not install the update as expected.

When you view the log files in Event Viewer in this situation, you see that the following Error events are logged:

Event ID: 5719

Source: Netlogon

Type: Error

Description: No Domain Controller is available for domain DTS-LAB due to the following: There are currently no logon servers available to service the logon request. . Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.

Event ID: 1054

Source: Userenv

Type: Error

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



CAUSE
This problem may occur if the Group Policy engine times out as it waits for the network to start.



RESOLUTION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.To resolve this problem, add the GpNetworkStartTimeoutPolicyValue registry entry on the Windows XP SP2-based computer. This entry specifies the number of seconds that the system waits before it tries to run the Group Policy startup script again. To find the value that will work for your configuration, define a decimal value of 60, and then incrementally increase this value until the problem is resolved.

To add the GpNetworkStartTimeoutPolicyValue registry entry and to define the value, follow these steps:  Click Start, click Run, type regedit, and then click OK. Expand the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

 Right-click Winlogon, point to New, and then click DWORD Value. To name the new entry, type GpNetworkStartTimeoutPolicyValue, and then press ENTER. Right-click GpNetworkStartTimeoutPolicyValue, and then click Modify. Under Base, click Decimal.</li> In the Value data box, type 60, and then click OK.</li> Close Registry Editor, and then restart the computer.</li> If the Group Policy startup script does not run, incrementally increase the value of the GpNetworkStartTimeoutPolicyValue registry entry until the problem is resolved.</li></ol>

Keywords: kbtshoot kbexpertiseinter kbprb KB933458

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.