Article ID: 884054
Article Last Modified on 7/24/2007
APPLIES TO
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- 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
SYMPTOMS
Microsoft 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.
CAUSE
This 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.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This 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
WORKAROUND
Warning 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.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
812599 Opportunistic locking may not be granted if Windows is installed by using Sysprep
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: Oplock Applying computer settings", registry.pol, 2 byte chunks, EnableOpLocks , GPO, Group Policy,
Keywords: kbqfe kbhotfixserver kbbug kbfix kbwinserv2003presp1fix KB884054
