Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

(232300) - 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...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks
Article ID: 232300 - Last Review: February 27, 2007 - Revision: 2.2

Startup Script Does Not Run on a Domain Controller

View products that this article applies to.
System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center
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.
Back to the top

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.
Back to the top

RESOLUTION

To resolve this issue, install another domain controller in the domain so that the Sysvol share is available during domain controller startup.
Back to the top
APPLIES TO
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
Back to the top
Keywords: 
kbenv kbprb KB232300
Back to the top
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting