thats very good!
Typically it takes around 10 - 40 seconds on our network. Children use mandatory roaming profiles and staff just normal roaming profiles. In my experience keeping roaming profiles as small as possible (typically under 3MB) is important otherwise logon time will lag. We run our workstations at 100Mbps speeds and once logged into XP, file transfers and browsing network drives are fast. Bearing in mind most of my machines are 5 years old I'd like to think I've done a good job
thats very good!
quackers - roger that and thanks for the help :-)
We're a primary school and each year group has it's own logon name with a mandantory profile. Staff have their own roaming profiles. Different year groups need to have different profiles (they are differentiated - e.g. reception don't double click).
Pupil logon is 45sec total: 15 sec loading profile (1mb) and 30 applying personal settings. This is the same on new and 5 yr old machines. (can be longer over wireless loading profile).
The slow bit is applying personal settings. This seems to be caused by group policy. When I disable the policy it is really quick but I loose folder redirection and some restrictions. Is there anyway of making it save all the policy info in the user.man file? Then I could disable the policy.
This is a very interesting thread and it would be great if Quackers created a wiki on how he shortened the logon process.
We have mandatory profiles and group policies in a SErver 2003/XP domain. Logons take about 55 seconds, which people do complain about. I followed the instructions to use the default local profile instead of mandatory - but that just dropped the logon from 55 to 51 seconds.
I then removed the policies and the logon was 11 seconds.
Removing the policies AND the mandatory profile dropped the logon to 9 seconds.
So, clearly it's the group policies that are causing the major part of the delay in our instance. I guess that there is nothing we can do about that is there?
Is it folder redirection thats causing your delay? I get this too if i use them, but only on SP2 XP PC's. So i just manually set them in the user.dat ?
The more group policies a client machine has to process the longer it'll take to startup and login. You might want to see if you can combine some related group policies together.
hmmm, yes, we do use folder redirection alright and when I removed the policies that would have been removed too. I will give that a go. CheersOriginally Posted by Quackers
Yep, I had to go through all those a few months ago and combine them into a "Pupil" policy instead of one policy for every configuration/restriction - that knocked about 15 seconds of the logon time I think.Originally Posted by Geoff
Have you got any policies defined that do the same as not configuring - if you know what I mean!? :P
We've only got one user-side policy and that's taking 30 secs to load.Originally Posted by Geoff
Something is hillarious broken then. I suspect DNS. How many domain controllers do you have? Are they setup correctly? What does DCDiag think? What about your clients? Are you using DHCP and pointing them to the Windows AD DNS Server(s) correctly? What does the GPMC think? Does GP Results/Modelling show errors?
In my experience there is a gpo setting that introduces a delay on logon. I have yet to identify which one though (not enough time). I even went as far as capturing the network packets during the pause, I didn't notice anything odd, it just stops and waits or does something. My personal policy has fewer settings and logs in fast, another for students is slow. My profile creator account is fast and uses most of the settings used by the students.Originally Posted by Geoff
This is from a good clean install of a 2003 domain and server, it has always been this way, machine speed doesn't affect the pause.
DNS is fine, DCdiag, Netdiag all report no problems.
1 - Windows 2000 Server.Originally Posted by Geoff
I think soAre they setup correctly?
All tests passed, including dns one.What does DCDiag think?
What can I test here?What about your clients?
Yes. I remember having it wrong once and it took 3 minutes to logon.Are you using DHCP and pointing them to the Windows AD DNS Server(s) correctly?
How do I test this?What does the GPMC think? Does GP Results/Modelling show errors?
The client equivalent of DCDiag is NetDiag. Use it.Originally Posted by eean
As its W2k you can only do the results. Login to a problem workstation with a user. Then load up the GPMC on one of your admin PCs. At the bottom there's a Group Policy results section. Add the User/Computer combo as a report to this bit. It'll list any problems coming up when that user logs on to that computer. What Polices are processed. Event Log items. Etc.. Just go through everything looking for anything unusual.Originally Posted by eean
BTW. You might want to consider an upgrade to W2K3 server at some point. It's really much nicer.
There are currently 1 users browsing this thread. (0 members and 1 guests)