Vista domain logon slow

Identify start and stop times where CPU activity is high. Identify start and stop times where CPU activity is low, which could indicate a deadlock condition or network delay or simply the absence of work that is, the OS is waiting for user input such as the user logon or a credential popup.

It may be helpful to review CPU utilization in summary tables right click on CPU Sampling by Process pane once you have cloned in on a time window that you want to review in more detail. Similar to CPU Review the disk utilization over the duration of the trace and make a mental note about overall disk utilization. Note the start and stop times where disk utilization is high.

Open summary tables and note which files were read from or written to and whether that activity represented a significant amount of the overall disk activity, especially on a busy disk.

Review disk activity once you have cloned or zoomed in on one or more time periods of interest. Look for long running child processes within the autostart parent.

To identify root cause, you will likely need the drill down into the supporting stack trace data. When booting with a mechanical hard drive however, the Readyboot pane should identify that a certain portion of the OS load was pre-cached.

A large number of cache misses could indicate non-default Readyboot service start, invalid registry values, or a bug where a large number of restore points disables the Readyboot plan, resolved by KB Longer execution times may indicate the existence of network delays or code defects which are typically resolved by post RTM service packs and QFEs. Dode defects in Windows are typically resolved by post-RTM service packs and hotfixes.

The network infrastructure should also be evaluated as a potential source of delays. The Profile service loads both the user profile and user home directories. Long execution times may indicate a problem with either operation, or a delay in an upstream operation, including a delay in the autostart phase in the services pane or a delay in network startup.

Repeat for each additional instance. Everything above is used to identify the process ID, thread ID and time window where delays occurred there may be more than one.

Delays are typically exposed by: The long running child operation in the Autostart phase. Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. This setting is enabled by default in Windows 7, but needs to be specified for Windows XP. To add to what others have posted, I've seen this sometimes when the client machines DNS are set to something other than an AD server or internal DNS server , this is especially true if your local domain is using a.

Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Asked 8 years, 11 months ago. Active 2 years, 7 months ago. Viewed k times. We are racking our brains trying to figure this problem out an are currently stuck! Improve this question. Daryl Liney Daryl Liney 1 1 gold badge 1 1 silver badge 3 3 bronze badges. Do you guys have an ntp server, and sync all your clocks with this ntp-server? I nearly lost my mind because we didn't have an ntp Server and all our AD Maschines where slightly out of sync and this causes insane network traffic and really long authentification times.

You could also try to configure DNS entries on a local system. Mark Russinovich has some great links for troubleshooting slow logons. You may consider starting there to gather some more information about your specific problem.

I have two questions about the problem : Are you sure that you don't download the entire user directory at login files, documents, music, etc. Is the logout slow too? CHeck Network traffic. Show 1 more comment.