For the past week my users have been experiencing extreme logon times. They are generally in the 20 minute range or more. I will lay out my research below to see if anyone may know how to find the root cause.
Terminal Server:
- x2 Quad core Xeon 2.6Ghz processors
- 16 GB ram
- x2 300GB SAS drives in Raid1
- Gigabit Lan
- Windows 2k3 Enterprise
- Average users connected 23
Domain Controler:
- Windows 2k3 Enterprise
- Gigabit lan
- Also stores roaming profiles
Most of the information I have gathered has been from parsing the USEREVN.log file. I wrote a custom parsing tool to try and glean as much information as possible from logging the users login processes. Here are some stats from those logs.
- The single most logged routine is ReconcileFile
- The most time spent total is on the routine ReconcileFile
- There is no single routine that is taking an extreme amount of time.
- ReconcileFile and RecurseDirectory take 7 times longer than GPO processing
- The average time spent per ReconcileFile routine is 223 milliseconds with normal user load
- the average time spent per ReconcileFile routine is 220 milliseconds when only 1 user is accessing the system
- From a user prospective the average execution time of a thread handling a routine for that particular user can be upwards of 1 second, though, the average time per routine still may be about 223 milliseconds.
- A particular user may have routines being executed to log them on over a 20 minute period but actually only have around 2 minutes of execution time devoted to their login.
Having gathered all that diagnostic data I still can't find the root cause of the issue. The servers resources have not changed between this week and last. So, I'm at a loss of were to look next.
USERENV.LOG
to be frustratingly verbose but low on detail. If I were you, I'd also run a Process Monitor trace on a user logging-on to see how that looks, too. I suspect that's going to help you pinpoint the root cause.