Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

When loggging into our domain, after entering account credentials the log in process takes around 1-2 minutes before it gets past the User Profile Service, the rest of the process takes 2-3 secs.

This effects all machines running Windows 7 Enteprise 32-bit and is on fairly high spec laptops (SSD drives, i5 2.93Ghz CPU, 4GB memory).

Is there any way to speed this up or is this time delay acceptable?

Thanks in advance.

share|improve this question
Are you using network profiles or folder redirection? –  jscott Dec 15 '10 at 20:38
This is often indicative of a DNS problem –  Mark Henderson Dec 15 '10 at 21:00
@jscott folder redirection –  Chris Dec 15 '10 at 21:17
is this logging into the domain for the 1st time on a given workstation or everytime? –  tony roth Dec 15 '10 at 23:21
Why not fire up a sniffer and see what is going on. –  Zoredache Dec 16 '10 at 1:04
show 1 more comment

5 Answers

Have you looked for Event Log errors during the time of logon on these workstations? Also, I'd recommend turning on Verbose messages via GPO for some workstations you can troubleshoot on to see where it is taking the longest.

In a Computer GPO: Administrative Templates\System\Verbose vs normal status messages - enable. Run GPUPDATE /force and reboot. Now when you logon you'll get more descriptive messages to help in troubleshooting where the delay is.

share|improve this answer
add comment

We have got the “waiting for the user profile service” problem solved.

For our case, we are not using roaming user profile but we have found that our AD users have specified Home Drive in network drive. So we just changed the AD user home drive to “Local” (with no drive specified)

To validate where is your home drive and home path is just execute SET command in CMD and browse for HOMEDRIVE and HOMEPATH. For our case, we want to ensure that it's D:\ and \Users\xxxx

Good Luck. I am Number 9

share|improve this answer
add comment

Mark probably has it right, about 99% of the time I've seen this the root cause has been something with DNS.

Edit: Heres some basic tips to troubleshoot this particular problem.

Try and ping the server using the FQDN. This should let you know whether or not you've got your local DNS configure correctly.

Verify that you've got the correct dns settings in your local profile. If you don't know what they should be check a PC that is working correctly and just mimic those settings.

If you've got the right DNS server configured one thing that I've often seen has been either a missing or mismatched computer account on the domain. Verify this by comparing the local PC name to what the account is on the server.

I've also had some luck just leaving and rejoining the domain.

@Corey S. - Thanks for the nudge :)

share|improve this answer
That's wonderful, but what about throwing him a bone in terms of what to look for in way of DNS issue? –  Corey S. Dec 15 '10 at 22:43
add comment

It is taking bit long in logging becuase it is going to find profile on server. Assign your server IP as DNS on Windows 7 pc. So it will faster able to search server and logging process will be even faster.

share|improve this answer
add comment

Verify your workstations have DNS IP pointing to your AD servers and not some external IP's.

For example if your internal DNS IP is and You can't use something like google DNS So make sure you use internal DNS servers only and that those DNS servers are Active Directory aware. Having external DNS on your Workstations (even as 2nd IP) can cause serious delays (exactly what you are seeing now).

share|improve this answer
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.