Logon Times

[mhchs]

Hi

I have a network of about 200 users and 500 PC's. i user ranger on all of my curriculum PC's which is about 400 give or take. Logon times can vary from 1 minute to 2 and a half minutes. i know that the gap will depend on a lot of things, but i was just wondering what other peoples log on times are like?? and if this is an exceptable time for logon or not?

we use roming profiles but the students cant change theirs.
I also have PCE installed on the network.

[Gibbo]

From CTRL-ALT-DEL and the user pressing enter after typing in their username and password, I'd say about 20 seconds (mandatory profiles)

They then get about 10-20 seconds of usable time before the Securus screen pops up and they have to click ACCEPT.

[Disease]

Mine can be around 1.5 to 2 mins, but we are using raoming profiles, I really need to make the move to mandatory ones

[Michael]

I would say up to one minute is an acceptable logon time to process scripts, policies and anything else you have set. It can depend how you've set certain policies, for example do you process logon scripts synchronously or not. This can make a difference.

Other considerations are the age/speed and memory of the machines and whether they're wired or wireless.

[danrhodes]

There has been much talk of this @ Minimising student logon times

[webman]

RM CC3 network with roaming profiles - logon for a new clean profile takes a maximum of 35 seconds. Cached profiles usually take about 15 seconds or less depending on workstation specification.

[Technical-Edge]

About a minute first logon then 10 seconds on subsequent logons. HP Xeon 2003 server, xp pro client, 2.4g 512m. All folder redirected Very happy with this!

Hi all btw

[jsnetman]

Here for pupils on MAN (winxp) profiles 6 seconds and for win7 12 seconds. You can reduce your logon times by getting rid of the setting up desktop applet that appears in the top left corner at logon. The thing causing this is the stubpath entries in the registry (you can delete them, I was a bit hesitant and tried it on one machine first). But of course it also depends on your network we are gigabyte to desktop.

I would say that anything over 30 seconds is unacceptable, and anyone using roaming profiles in a school environment is not doing it right, because people are moving frequently between machines roaming is a bad idea.

I also tried roaming on staff laptops and they just get screwed up with all the teachers put in their profile, now I use local profiles for laptops.

[PiqueABoo]

anyone using roaming profiles in a school environment is not doing it right

I think folk who can't make roaming work (it does have some advantages) aren't doing it right ;b

I also tried roaming on staff laptops. <snip> now I use local profiles

Yeah, if you're letting them install random on those laptops you've got to do it that way.

--

I tend to worry more about "cold-boot > logon-ASAP > working-desktop" times. Have quite a lot of GPOs and some work to do at startup - can do that on a few years old (not flash at the time) box in around 150 secs.

The logon part which has it's fair share of user policies and roaming profiles is something like 20 - 30 secs. Note I've excluded various profile folders from roaming and also use folder redirection for my docs, favourites, app data etc.

It's worth adding that AV can have a very significant effect on boot/logon times.

[alfatec]

We use local profiles and have a script that clears them at the end of terms. We use Ranger 7 and our first login is approx 30 seconds and subsequent logins
are approx 15 seconds. Biggest problem I always find is old desktop icons and start program menus point to old resources.