Dear Customer,
Thank you for posting in newsgroup. And thanks to members for the
contribution.
According to the description, this seems to be a Windows client logon hang
issue. If I have any misunderstanding, please feel free to let me know.
To troubleshoot the issue, I would like to confirm some information with
you firstly.
Information Needed:
======================
1. Did these problematic computer take a long time to logon the domain with
domain user credential or logon to the local computer?
2. If the problematic computer logon the domain with hang issue, did you
configure some group policy to apply on the container of the problematic
clients? If so, please try disable the corresponding group policy on the
domain controller and then run "gpupdate /force" both on the domain
controllers and the problematic clients, then you may restart them to see
if the issue will re-occur.
Analysis and Suggestions:
========================
Since the Windows logon hang issue may be cause by lots of possible reason,
in order to narrow down the cause of the issue more efficiently, please
refer to the following steps to perform a Clean Boot and restart these
problematic computer to see if the hang issue will re-occur.
1. Perform a Clean Boot
a. Click "Start", go to "Run", and type "msconfig" in the open box to start
the System Configuration Utility.
b. Click the "Services" tab, check the "Hide All Microsoft Services" box
and click Disable All (if it is not gray).
c. Click the "Startup" tab, click "Disable All" and click "OK".
d. Then, restart your computer. When the "System Configuration Utility"
window appears, please check the box and click "OK".
2. Since you mentioned that you suspect that the local user profile is
corrupt, please try restarting the problematic system, logon as the
administrator credential, remove the problematic user profile, then logoff
and logon as another new domain user to see if the hang issue will be
re-occur.
3. Collect Userenv.log
Please do as following steps on these problematic computer to obtain
detailed troubleshooting information from the user environment debug log.
a. Start Registry Editor.
b. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon
c. Right-click and new add DWORD(32-bit) with the Value of
"UserEnvDebugLevel"
d. Type in 100002(Hexadecimal) or 65538(Decimal) in the Value data box, and
then click OK.
e. Reboot the problematic computer to make the change take into effect.
Please note: the Userenv.log is located in the folder:
%SYSTEMDRIVE%\Debug\UserMode\
4. Collect Winlogon.log
Please do as following steps on these problematic computer to enable
winlogon.log as the delay occurs during computer startup:
a. Start Registry Editor (Regedit.exe)
b. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon\GPExtensions\{827D319E-6EAC-11D2-A4EA-00C04F79F83
A}.
Please note: The above registry key is one path; it has been wrapped for
readability.
c. Edit the following registry value:
Value name: ExtensionDebugLevel
Data type: DWORD
Value data: 2
d. Quit Registry Editor
e. Reboot the computer
Please note: the Winlogon.log file is created in the folder %systermroot%
\Security\Logs
You may send the logs to (e-mail address removed) and we will discuss it with
that.
Reference:
============
How to enable user environment debug logging in retail builds of Windows
http://support.microsoft.com/kb/221833
How to Enable Logging for Security Configuration Client Processing in
Windows 2000
http://support.microsoft.com/kb/245422
I look forward to your reply and thank you for your time.
David Shen
Microsoft Online Partner Support