home folder, slow login, alternatives?
-
Friday, December 23, 2011 9:39 PM
I have a laptop, joined to a domain, with a very slow logon when offline (45 seconds). I investigated a million possible causes, tried every single group policy and network setting I could find on the web, analyzed logs and everything, and found that my problem is the home folder set in AD, which is a network folder (H:, the folder includes the username). We also assign a common file share to all users via group policy and that doesn't cause a problem (S:, same for everyone). Offline logon is slow for all users except one. I did check and he does have the usual AD home folder, too. I guess I did most of the work already, because turning off the home folder for myself solves the problem, but I still need a better solution but I guess I got tired of searching for 30+ hours already.
So the first question: is there a way to have the home folder as is without the slowdown? I know it's possible, I just don't know how that user did it.
Second question: do we need the home folder at all? We do not have folder redirection or roaming profiles or anything, users put stuff there but Windows doesn't. It's a private folder that's available from all workstations and that's just nice. I could remove the homeFolder attribute for all users and set up a group policy to map this folder, just like the common fileshare, I believe I could use the username in a common GPO setting. What would be the difference? What does Windows use the home folder for?
Third question: where does Windows cache the homeFolder attribute? I'm absolutely sure that it does somewhere. In the SAM file I guess. Is there a way to make Windows forget that setting? I also know that it resync's that setting when it gets connected to a DC, so this would be a perfect solution.
- Edited by fejesjoco Friday, December 23, 2011 9:41 PM
All Replies
-
Friday, December 23, 2011 10:07 PM
Try converting your profile to local
system properties - advanced - user profiles
-
Saturday, December 24, 2011 7:20 AM
It is local. I explicitly said we don't have roaming profiles.Try converting your profile to local
system properties - advanced - user profiles
-
Tuesday, December 27, 2011 8:09 AMModerator
Hi,
These files need to be indexed. this is the biggest difference between normal fileshare and it.
If it could be set as a sharing folder, please try.
Juke Chou
TechNet Community Support
- Marked As Answer by Juke ChouMicrosoft Contingent Staff, Moderator Thursday, January 05, 2012 8:02 AM
- Unmarked As Answer by fejesjoco Thursday, January 05, 2012 8:36 AM
-
Thursday, January 05, 2012 8:37 AMSorry I must have missed the notification that you replied. I'm sorry I don't completely understand what I should do. Should I set up indexing for the home drive? Will that help when I'm logging on?
-
Thursday, January 05, 2012 8:46 AMModerator
Hi,
Based on my experience, this delay should be expected.
Juke Chou
TechNet Community Support
-
Thursday, January 05, 2012 10:05 AM
Hi,
Based on my experience, this delay should be expected.
Juke Chou
TechNet Community Support
With a 7+ experience index? :) I'm sorry, but really, I wouldn't mind if my PC was an old junk, but I spent a hell of a lot money on this PC, and having to wait a minute after typing my password is completely unacceptable.
I'm still trying to figure out why it's not slow for my colleague who also has the same home drive setup. At least I know now that if I just disable my home drive, it will be as fast as it should. But I still wouldn't like to close this thread either as ansewered or unanswerable.
-
Thursday, January 05, 2012 10:30 PM
Juke,
I have to say that does not make alot of sense. If every domain user that that issue when they were off the domain, there would be a massive uproar.
Feje,
no tash manager *conflicts* occuring at startup? Check the task scheduler to make sure you do not have any program "triggered" to run a script or execute during startup. this is not msconfig or anything like that.
In the event log, under Application & Services, Microsoft, Windows, Diagnostic-Performance, Operational - any event ID 101 should show you startup degredation in milliseconds and what the offending service is. I know you said its the home folder but it would be interesting to see if a program, driver or anything is part of the reason you are having isues with this. - Also, and I am sure you probably did this, but disable your AV for a startup and see what happens. Its amazing how AV can muck up the works at times!
-
Thursday, January 12, 2012 4:12 AMfejesjoco, I am also having the same problem! I have been looking for a fix for a while also. If the laptop is not connected to a network or connected to the domain network the logon is fast, if I am connected to a network that is not the domain, the logon stalls extra time. I too have home drives and drive mappings with GPO.
-
Sunday, February 05, 2012 2:27 PM
Im also having the same problem.
Before ctrl-alt-del it waits 45 seconds, and when logging on it waits 30 seconds.
-
Saturday, April 28, 2012 5:30 AM
Another long weekend, fed up with the slow login again, started searching again, and I found the answer!
It was proposed here: http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/613d039b-1754-4978-b535-3fcbd29610f1/
Policies>Computer Configuration>Administrative Templates>System>User Profiles>Set maximum wait time for the network if a user has a roaming user profile or remote home directory
The moment I even saw the name of this setting, I knew this was exactly what was happening. It doesn't need roaming or redirection as it was suggested as a cause, it even waits for a simple home folder like in my case. So I set it to 5 seconds, and yes, the login is fast now!
- Marked As Answer by fejesjoco Saturday, April 28, 2012 5:30 AM
-
Tuesday, January 29, 2013 5:23 PM
I solved this by enabling IPv6 on a Win2008 R2 server
.png)
