Member server takes 20 minutes or more to log on to the domain in Windows Server 2003 (884054)
The information in this article applies to:
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry SYMPTOMSMicrosoft Windows Server 2003-based member servers that do not have a locally cached profile may take 20 minutes or more to log on to the domain.
Additionally, during startup, the "Applying computer settings" screen appears and remains for longer than you expect. CAUSEThis problem occurs because two or more computers have the same registry value in the GUID entry. The GUID entry is located in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Important This problem is typically caused by computers that are set up by using the Sysprep tool.
RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesNo prerequisites are required. Restart requirementYou must restart your computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes. File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003
Date Time Version Size File name
--------------------------------------------------------------
16-Sep-2004 16:18 5.2.3790.211 90,624 Srvsvc.dll
Windows Server 2003, 64-bit edition
Date Time Version Size File name
--------------------------------------------------------------
16-Sep-2004 17:20 5.2.3790.211 192,000 Srvsvc.dll
WORKAROUNDWarning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To work around this problem, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters - In the right pane, right-click Guid, and then click Delete.
- Click Yes, and then quit Registry Editor.
- Restart your computer. The GUID entry and value will be re-created when the Windows Server 2003-based computer restarts.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 6/1/2006 |
---|
Keywords: | kbQFE kbHotfixServer kbBug kbfix kbWinServ2003preSP1fix KB884054 kbAudITPRO |
---|
|