Link to home
Start Free TrialLog in
Avatar of mcse2007
mcse2007Flag for Australia

asked on

Super Extremely Slow Login Process to Domain

Hi,

When we login on to our Domain, it takes so long before the Desktop will appear, it says processing policy then processing desktop.

We have roaming profiles but also quite a lot of group policies for network printers as well.

Where is the best place to try to troubleshoot this problem? I wanted to see what is processing in the background.

Thanks a lot

Cheers
Avatar of Mike Kline
Mike Kline
Flag of United States of America image

There are a lot of methods; check out Matt Reynolds "coffee talks" from TechEd.  He has done them every year for the last few years

http://channel9.msdn.com/Search?term=matthew%20reynolds#ch9Search

Are there any group policy errors in your logs.   It is probably a GPO or profile from what you said but the tools Matt outlined will narrow it down.

Thanks

Mike
Avatar of mcse2007

ASKER

I  am looking for some answer to resolve the problem immediately....not to watch a video....

....next
did you checked you group policy and try to review the same and check. Most of the time group policy takes more time to apply.
Sekar re read the question above again?
How many DC do your have,  how many sites,  does each one have DNS
I'm logging from the head office; my AD account belong in the Head Office AD,
is that happening for all users in the head office, i assume you have dns on the dc.
have you tried removing the policies and add them one by one to see which one is causing the issue.
Some questions before we can start debugging :
1. Is this happening for ALL the users on all the machines ?
2. AFTER you login, can you access all your network drives ?
3. Enable user environment debug logging:
Use Registry Editor to add or to modify the following registry entry:
Subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon

Entry: UserEnvDebugLevel
Type: REG_DWORD
Value data: 10002 (Hexadecimal)
UserEnvDebugLevel can have the following values:
NONE 0x00000000
NORMAL 0x00000001
VERBOSE 0x00000002
LOGFILE 0x00010000
DEBUGGER 0x00020000
The default value is NORMAL|LOGFILE (0x00010001).

Note To disable logging, select NONE (0x00000000).

You can combine these values. For example, you can combine VERBOSE 0x00000002 and LOGFILE 0x00010000 to get 0x00010002. Therefore, if UserEnvDebugLevel is given a value of 0x00010002, LOGFILE and VERBOSE are both turned on. Combining these values is the same as using an OR statement.
0x00010000 OR 0x00000002 = 0x00010002

The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log file
Hello GeoSs,

Some questions before we can start debugging :
 1. Is this happening for ALL the users on all the machines ?

YES

 2. AFTER you login, can you access all your network drives ?

YES,

--
OK thanks, I will give your suggestion a try and report back soon.
I cannot see the above parameters with Windows 7 O/S - see attached.
Capture.PNG
ASKER CERTIFIED SOLUTION
Avatar of George Sas
George Sas
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
tx
What was the problem ? Could you please update us ?