Microsoft KB Archive/232300

= Startup Script Does Not Run on a Domain Controller =

Article ID: 232300

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



This article was previously published under Q232300



SYMPTOMS
A startup script that you created with group policy to be run on a domain controller may not be run when you restart the domain controller. When this occurs, the following message may appear in the system event log:

EventID: 1000

Type: ERROR

Source: Userenv

Description: Failed to access the registry information at

\\ domain.com\SysVol\domain.com\Policies\(Guid Number for Policy)\Machine\registry.pol with 53

However, logon and logoff scripts for users work correctly.



CAUSE
This behavior can occur if there is only one domain controller in the domain. Because scripts are run from the Sysvol share, the Sysvol share must be available. Startup scripts are run very early in the startup process, and if there is only one domain controller, the Sysvol share is not available until the startup process is finished.



RESOLUTION
To resolve this issue, install another domain controller in the domain so that the Sysvol share is available during domain controller startup.

Keywords: kbenv kbprb KB232300

-

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

© Microsoft Corporation. All rights reserved.