need help to solve slow logon issue
hi all,
the situation is that winxp machines in a domain environment are all experiencing slow logon issue.
after enter user name and pwd then hit enter, applying computer setting and personal settings are taking some time( still reasonable ) but after that, no icon no window is appearing on screen (only wallpaper is shown). in task manager, i can see userinit.exe is running. this will take some time untill explorer.exe loads.
i suspect that winxp is trying to access some network shares during userinit.exe
is there anyway to find out what network shares winxp is trying to access during userinit process? and along with time spent ?
is there any tools??
note: i want to know what network shares not what processes that are running during userinit.exe
the situation is that winxp machines in a domain environment are all experiencing slow logon issue.
after enter user name and pwd then hit enter, applying computer setting and personal settings are taking some time( still reasonable ) but after that, no icon no window is appearing on screen (only wallpaper is shown). in task manager, i can see userinit.exe is running. this will take some time untill explorer.exe loads.
i suspect that winxp is trying to access some network shares during userinit.exe
is there anyway to find out what network shares winxp is trying to access during userinit process? and along with time spent ?
is there any tools??
note: i want to know what network shares not what processes that are running during userinit.exe
Who is Participating?
Open regedit
Navigate to HKEY_LOCAL_MACHINE\Softwar
Fi the reg key below does not exist already then create it
Entry: UserEnvDebugLevel
Type: REG_DWORD
Set the value to UserEnvDebugLevel to 0x00030002
Now reboot and log in. Once login process has finished examine the log file.
%Systemroot%\Debug\UserMod
If you cant make any sense of it, paste the section of it from the time you start to login to the end on hear.
Navigate to HKEY_LOCAL_MACHINE\Softwar
Fi the reg key below does not exist already then create it
Entry: UserEnvDebugLevel
Type: REG_DWORD
Set the value to UserEnvDebugLevel to 0x00030002
Now reboot and log in. Once login process has finished examine the log file.
%Systemroot%\Debug\UserMod
If you cant make any sense of it, paste the section of it from the time you start to login to the end on hear.
Thanks for the input guys I will try
And these don't show me which network shares machine try to access
And these don't show me which network shares machine try to access
This one should show you network access....
Process Monitor can enable boot logging, so you can see whats happening in EXTREME DETAIL............
Troubleshooting with Process Monitor
http://blogs.technet.com/b/askperf/archive/2007/06/01/troubleshooting-with-process-monitor.aspx
Options>Select Enable Boot Logging, and reboot.... After reboot, launch Procmon to compile the logs.....
Then you can look at the times to see where your delays are......
This one is not nearly as complex...
Boot Log XP
http://www.greatis.com/utilities/bootlogxp/
Process Monitor can enable boot logging, so you can see whats happening in EXTREME DETAIL............
Troubleshooting with Process Monitor
http://blogs.technet.com/b/askperf/archive/2007/06/01/troubleshooting-with-process-monitor.aspx
Options>Select Enable Boot Logging, and reboot.... After reboot, launch Procmon to compile the logs.....
Then you can look at the times to see where your delays are......
This one is not nearly as complex...
Boot Log XP
http://www.greatis.com/utilities/bootlogxp/
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
Also make sure that the health of the DC is ok.Ran dcdiag /q and repadmin /replsum on the DC to check the same.
On one of the client PC try this method.
Type Regedit on the run task, then located this path HKEY_LOCAL_MACHINE\SOFTWAR
2. HKEY_LOCAL_MACHINE\SOFTWAR
3. Restart your PC and check.