Is this correct? Slow logon issue explanation...

[cyberspace]

So heres the scenario...

A colleague of mine today told me that for a long long time that is takes at least 10 minutes to log in in the mornings (or indeed at any time where she logs in).

So I got on the case.

I was looking at the settings in her AD profile.

When this account was set up (not by me), whoever did it didnt follow the usual office convention of the ForenameSurename format for the login name...in this case, the login name was just Forename.

HOWEVER - on the "Profile" tab of the AD properties for this user, the profile setting was \\Server\profiles$\ForenameSurename

Now, am I correct in thinking that the reason that the logon was taking so long, was that the machine was attempting to load a non-existant profile, which eventually timed out, and then loaded a default profile or the last used (im not sure which, hopefully someone can tell me). As soon as I removed this line, the logon was at normal speed.

So thats obviously the cause, i'm just keen to know if my analysis is correct...

Of couse I am now a hero to the person in question as apparently its been like that for over 6 months! I would have went mad long before now lol.

'When all else fails.......read the manual'

 

[rvnguy]

You must be on a MS Server OS...

quick solution, delete this user, find a similar user(same types of permissions) clone this user to create a new user for the deleted one.

This doesn't let you find the problem but will let you quickly correct the problem

rvnguy
"I know everything..I just can't remember it all

 

[cyberspace]

Thanks for the reply, although as I mentioned the problem was solved by removing the entry for the profile path.

I just wanted to know if my reasoning was correct.

'When all else fails.......read the manual'

 

[rvnguy]

Missed that....

rvnguy
"I know everything..I just can't remember it all

 

[gbaughma]

That sounds like a reasonable assessment.

The only other thing that I've found really slows down AD user logins is if the first DNS entry is not pointing to your AD server.



Just my 2¢

"In order to start solving a problem, one must first identify its owner." --Me
--Greg

 

[wvajenm]

I may be mistaken, but doesn't windows just create a profile under the name that is specified in the profile path? It doesn't have to be the same as the login name, as long as you've told it where to look, in this case under the profile directory, then the ForenameSurname directory. I'd be far more likely to suspect something was fouled within her profile, and the problem was actually solved when you directed her to a new, blank default profile, rather than changing the name of the directory where the profile was stored.

 

[BadFrog]

The only other thing that I've found really slows down AD user logins is if the first DNS entry is not pointing to your AD server.

Can you please expand on that some? Are you referring to the advanced TCP/IP settings?

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[TheLad]

I have also seen slow logins when some dopey user decides on keeping a 500Mb folder on the desktop, which in turn gets downloaded during login and uploaded on logout as part of the profile

------------------------------------------------------------------------------------
"Life is like a box of chocolates, you never know what you're gonna get!"
------------------------------------------------------------------------------------

 

[gbaughma]

Quote:
The only other thing that I've found really slows down AD user logins is if the first DNS entry is not pointing to your AD server.


Can you please expand on that some? Are you referring to the advanced TCP/IP settings?

No... in the regular TCP/IP properties. I had an AD installation where everyone's workstation was taking like 10 minutes stuck on the "loading your personal settings" screen. When I changed the primary DNS server to point to my AD controller, it was instant logons.



Just my 2¢

"In order to start solving a problem, one must first identify its owner." --Me
--Greg

 

[cyberspace]

wvajenm - That's a very sensible explanation aswell....I think that's more likely actually

Thanks

As for the DNS - Yes, the first entry should always be for the AD Domain Controller

'When all else fails.......read the manual'

 

[BadFrog]

I had an AD installation where everyone's workstation was taking like 10 minutes stuck on the "loading your personal settings" screen.

Would that happen everytime they logon, or just the first time they logon to a PC where it has to create a local profile?

Thanks for your help.

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[gbaughma]

It was happening every time.



Just my 2¢

"In order to start solving a problem, one must first identify its owner." --Me
--Greg

 

[BadFrog]

Thanks gbaughma, we have a similar situation that only effects the initial logon, ie: profile creation. After that the logon runs at normal speed. If anyone has any suggestions for that I'm all ears! Thanks.

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[ghstinshll]

SO, my DHCP, DNS, SRV Records, and profiles are all perfect, but this is happening to my client.

When I go through DNS mgmt on the server it seems to delay in pulling up th e information. Is there some sort of repair functin I can do on DNS to the DNS server?

1. DHCP does not dish out any other DNS servers than the AD/DNS server
2. DNS shows a SRV record everywhere in the _tcp folders throughout the tree stricture
3. roaming profiles are all small in size.

Next thoughts?