Logon of client to domain can take long time

I had this problem running Windows Servers ever since. Some clients take a unreasonable long time to logon. It seems that the delay comes from loading the user profiles. I use roaming profiles which are shared on the server and are being named User$. Most clients work just fine but some take minutes until they log on. After that they work fine.

No problems reported in the Event Log, no network problems, all drives connected, Exchange server works fine, no problems at all. Same thing occurs on the same clients when logging off.

Any ideas?
domimAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
This sounds like classic roaming profiles issues.
Have you looked to see how big they are? Don't forget that they copy everything within the profile backwards and forwards from the server. If they haven't been setup correctly or a user has dumped something large on the desktop then it can dramatically increase the time it takes to login or out while the data is moved.

What are you trying to achieve with roaming profiles? I haven't deployed them since Windows 2000 was released. With careful use of folder redirection, scripts and registry files most of the "benefits" of roaming profiles can be achieved without the slow login times.

Simon.
domimAuthor Commented:
Well, if we take one example of a computer that takes really long the profile size is 17,5MB. I have actually limited them (default 30MB?).

Other (larger) profiles logon much faster...

Actually what I wanted to do is to make sure all profiles are on the server to make backup easier...

Dominik
domimAuthor Commented:
Forgot to add: the delay is not at "Loading your personal settings" but at "Applying your personal settings"...

Dominik
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

SembeeCommented:
The key data that you need to backup can be redirected to the file server. The main things that I worry about are My Documents, Favourites and the Desktop. Favourites is annoying and has to be done with a registry hack in the login script.

The first thing to check is DNS. All machines should be pointing at the domain controllers ONLY for DNS. No external DNS servers should be listed.

Simon.
domimAuthor Commented:
Actually the users that have roaming profiles do not use My Documents nor Favourites and the Desktop contains only links if any.

All clients have only one DNS set up which is the PDC.

What I did not is to edit the Default Domain Policy with that "wait until network blah" enable. Let's see if that helps...

Dominik
Kevin HaysIT AnalystCommented:
I would recommend redirection as stated earlier on the My Documents for sure if you are using roaming profiles.  DNS is the first problem usually with slow login times as Sembee suggested.  How many GPO's have you got implemented?

When a user attempts to login for the first time it will take longer because of all the settings being applied for the first time.  After this when they login it should be much quicker.  If this is not the case I still believe it's a DNS issue or you have a lot of GPO's pushing down.

Are these clients windows 2000 ,xp, xp1, xp2 ?

Kevin


domimAuthor Commented:
I can't find any DNS problem. And these clients do NOT log in for the first time. And there is just a hand full of GPS's (like WSUS config etc.).

All clients are XP2 except for on W2K (which has actually no prob).

Dominik
Kevin HaysIT AnalystCommented:
So you are saying the windows 2000 pc's have no problem with it correct?  

If so, have you turned the firewall off the XP SP2 machines to see if that makes a difference?  XP doesn't fully load all the network stuff (which is why it boots faster) upon startup.

Kevin
domimAuthor Commented:
It's only one W2K client. No problem with that.

Firewall on all XP2 clients is turned off. Even if I wait at the logon screen for some time (until everything has loaded) it still takes a long time on some machines, others logon normally. And again, the delay is at "Applying your Personal Settings", not "Loading..."...

Dominik
Kevin HaysIT AnalystCommented:
Well, going back to the basics here.  Have you created a new user, created a new test OU and slapped that new user in the new OU yet and tried to login as it?  Since you have each client pointing to your internal DNS server login times shouldn't be long as opposed to an external ISP DNS server entry.

Kevin

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
domimAuthor Commented:
Tried it with several users and worked fine...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.