Re: [suse-linux-uk-schools] XP Boot and network Logon times
Aplogies for not replying earlier but BT have had us disconnected yet again for a few days - power surge at the exchange apparently!!! Ok - straight in - boot up of Unix and Linux thin clients - max. 15 seconds - boot up of XP clients - max. 45 seconds. Logon to thin client - max. 10 seconds including running of script to link local printer, check folders, etc. - Logon to XP client varies depending upon age, location and use but never more than 90 seconds. We have a central Unix server, one W2000 RAID fileserver, One Unix / SAMBA audio/ video fileserver, 1 Unix backup server, 1 IIS server for those little things that MS make so difficult otherwise, 1 printserver, 4 application servers - we don't use roaming profiles because they are a pain in the backside in a school and we use Citrix XP to deliver it all to the desktops - locked down XP desktop delivered to the XP machines, shadowing built in to Citrix XP - own intranet / extranet on the Unix server - a forum, e-mail - and shortly staff / pupil work delivery and 97 / 98% usability throughout the school. Rooms are open most of the day and break, lunchtime and after school equipment is in use most days. Security is very high - virus infestation almost nil - and administration can be from any thin client anywhere in the school. We feel that a little extra cost is offset by availability, security and many other useful features like central web based administration and shadowing (one local school which is RM and XP only locks all ICT rooms and log in is so slow that most non-ICT staff have given up - personal mailboxes - forget it). Anyone who wants to look can come and see. We don't really need Windows now - a friendlier front end to MySQL and we could do most of what we do now - the rest could be sorted with emulation, except music. We still run Windows to keep all the other staff happy because that's what they have at home and they just want to use it. If you want real support and an excellent system then we use Precedence Technologies of Cambridge - never heard of them - course not - their system works - no moaning to fill the air waves - they are usually just inside the door at BETT.
Not directly related to Linux, but hopefully the feedback you give might help me to persuade this school I am working with to explore the Linux server route.
At present this school has some 200 oe so XP-Pro based workstations that have a modest but not inadequate spec. At the server end they are running three well speced Xenon based Raid-5 systems. The server software is RM CC3 (Community Connect Three), which is based on Windows Server 2000 with RM's ageing proprietary management / security overlay.
Now here's the problem: Workstations take about 2.5 minutes to boot up to the Login prompt -- apparently the CC3 workstation overlay does loads of checking with the server to implement security settings etc before the user can log in. Now when I say 2.5 minutes to reach a Login prompt ...well that's on a good day. On a bad day this can take a good ten minutes or even longer.
As for the time it takes to get from logging in to being presented with a usable XP 'Start' menu, well this takes at least another two minutes ...again on a good day. In practice it sometimes takes between a quarter-of-an-hour and twenty minutes to get from 'power on' to a usable 'Start' menu.
OK. So the two managed service providers involved in supporting this school's site are playing 'pass the buck'. Meanwhile the school management is gradually waking up to the fact this level of performance isn't actually normal!
So what I want to know from the good members of this list is how long in practice does it take you to boot a networked XP workstation to Logon and thereafter to a usable menu ...talking to either a Linux (Samba) server or a Windows 2000 / 2003 server? Note that all users of this school network use 'roaming profiles'.
Also if anyone on this list can get access to a RM CC3 based network, what sort of boot / logon / Start Menu times are you commonly achieving with this setup in practice?
Thanks in advance.
David Bowles
-- If this e-mail contains anything that the recipient takes exception to, please contact: The Headteacher, Maidenhill School GL10 2HA UK (+44) (0) 1453 822469
Not directly related to Linux, but hopefully the feedback you give might help me to persuade this school I am working with to explore the Linux server route.
At present this school has some 200 oe so XP-Pro based workstations that have a modest but not inadequate spec. At the server end they are running three well speced Xenon based Raid-5 systems. The server software is RM CC3 (Community Connect Three), which is based on Windows Server 2000 with RM's ageing proprietary management / security overlay.
Now here's the problem: Workstations take about 2.5 minutes to boot up to the Login prompt -- apparently the CC3 workstation overlay does loads of checking with the server to implement security settings etc before the user can log in. Now when I say 2.5 minutes to reach a Login prompt ...well that's on a good day. On a bad day this can take a good ten minutes or even longer.
As for the time it takes to get from logging in to being presented with a usable XP 'Start' menu, well this takes at least another two minutes ...again on a good day. In practice it sometimes takes between a quarter-of-an-hour and twenty minutes to get from 'power on' to a usable 'Start' menu.
OK. So the two managed service providers involved in supporting this school's site are playing 'pass the buck'. Meanwhile the school management is gradually waking up to the fact this level of performance isn't actually normal!
So what I want to know from the good members of this list is how long in practice does it take you to boot a networked XP workstation to Logon and thereafter to a usable menu ...talking to either a Linux (Samba) server or a Windows 2000 / 2003 server? Note that all users of this school network use 'roaming profiles'.
Also if anyone on this list can get access to a RM CC3 based network, what sort of boot / logon / Start Menu times are you commonly achieving with this setup in practice?
Thanks in advance.
David Bowles
Apologies, I'm new to the mailing list and missed the original e-mail. I can't offer much advice, we neither run Windows 2000/2003 as a backend nor do we run a Samba server, being a Novell based network. The only thing I can comment on is your mentioning of roaming profiles. In our experience under win2k and XP-Pro, which are used cross-campus on all client machines, log in times are pretty bad when roaming profiles are used. We did a check around on the users home directories at the profile directory and discovered these averaged between 50mb and 150mb, depending on the range of programs the student used in lessons. Being academia, we've got 20+ people logging in at the same time point, near the start of a lesson, and there is no way you can pass that much info out with any great speed to that many clients immediately. We can theoretically have anywhere up to probably 280 class-room machines logging in within the same 5 minute time slot, that's at best 13gb of data we're throwing around every period! Needless to say when as soon as we switched roaming profiles off we found the logging in sped up phenomenally. Other than faster log-ins we haven't had any comments from either the staff nor the students about any loss of functionality, so we figure they can't actually be missing their profiles all that much. Paul Graydon Network Technician mailto:graydpau@hhc.ac.uk ; http://www.hhc.ac.uk The human mind is like an umbrella, it functions best when open.
On Monday 14 June 2004 09:04, Paul Graydon wrote:
We did a check around on the users home directories at the profile directory and discovered these averaged between 50mb and 150mb, depending on the range of programs the student used in lessons.
At the last setup I was involved with (GNU Linux servers, NT4, W2K and LTSP clients), the originally huge size of the roaming profiles was due to the user's desktop folders being part of the profile. We improved matters massively by configuring the desktop folders to be in the users home directory, (i.e. not part of the profile) and then served a single, small mandatory profile to all student users. Cheers -- Phil Driscoll
On Monday 14 June 2004 09:42, I wrote:
... was due to the user's desktop folders...
Don't let my appalling punctuation lead you to think that there was just one user :) I should have said ... was due to the users' desktop folders... Cheers -- Phil Driscoll
Not directly related to Linux, but hopefully the feedback you give might help me to persuade this school I am working with to explore the Linux server route.
At present this school has some 200 oe so XP-Pro based workstations that have a modest but not inadequate spec. At the server end they are running three well speced Xenon based Raid-5 systems. The server software is RM CC3 (Community Connect Three), which is based on Windows Server 2000 with RM's ageing proprietary management / security overlay.
Now here's the problem: Workstations take about 2.5 minutes to boot up to the Login prompt -- apparently the CC3 workstation overlay does loads of checking with the server to implement security settings etc before the user can log in. Now when I say 2.5 minutes to reach a Login prompt ...well that's on a good day. On a bad day this can take a good ten minutes or even longer.
As for the time it takes to get from logging in to being presented with a usable XP 'Start' menu, well this takes at least another two minutes ...again on a good day. In practice it sometimes takes between a quarter-of-an-hour and twenty minutes to get from 'power on' to a usable 'Start' menu.
OK. So the two managed service providers involved in supporting this school's site are playing 'pass the buck'. Meanwhile the school management is gradually waking up to the fact this level of performance isn't actually normal!
So what I want to know from the good members of this list is how long in practice does it take you to boot a networked XP workstation to Logon and thereafter to a usable menu ...talking to either a Linux (Samba) server or a Windows 2000 / 2003 server? Note that all users of this school network use 'roaming profiles'.
Also if anyone on this list can get access to a RM CC3 based network, what sort of boot / logon / Start Menu times are you commonly achieving with this setup in practice?
Thanks in advance.
David Bowles
Just curious... what is the need for CC3 on their network? Surely anything that can be done in RM software can be done through properly set up user and group policies? Win 2k and XP can be locked down very tightly if someone is willing to spare the half hour or so to think logically through all the settings. As part of our upgrade last summer to 2k we created new profiles from scratch and spent most of a morning deciding what to lock down, though mainly that was deciding on policy issues rather than whether we thought it'd stop the machine from working. We went from the basis of deny all, allow grudgingly. The result is nicely locked down workstations throughout the building with only a couple of complaints about certain restrictions (soon fixed), and very little in the way of issues in comparison to previous years spent forever fixing things students messed up under Windows 95/98. I just timed a Celeron 700 box with 256mb RAM here, booting up into XP and onto our Novell network, 28seconds to log in prompt 20 seconds to start menu. Paul Graydon Network Technician mailto:graydpau@hhc.ac.uk ; http://www.hhc.ac.uk The human mind is like an umbrella, it functions best when open.
A BIG thank you to everyone who has gotten back to me with information on boot times. This is just the evidence I need to persuade the school's management their network boot times are not normal.
Just curious... what is the need for CC3 on their network? Surely anything that can be done in RM software can be done through properly set up user and group policies? Win 2k and XP can be locked down very tightly...
Well the reason for this is largely political, not least because this is a PFI (Private Finance Initiative) school. So the school were pushed into updating their Win-98 based network (it's in the PFI contract so they godda do it). Mow the PFI supplier's 'facilities management' arm want's as easy a job as they can get away with. So they push the school into continuing down the RM route. Why? Well my guess is #1 the RM is locked down so tight the PFI Facilities Management arm will have almost nothing to do maintenance wise, other than occasionally shove the 'security update' CDs from RM into the server. Now this makes what they are doing very profitable, for they are paid a substantial premium for 'Network Administration', yet in practice they've gone for a premium priced supplier 'turn-key' systems supplier, RM, that ultimately the school pays for. This is basically what an old friend of mine would call a 'nice little earner'. Incidentally, in the school's contract with their PFI supplier the section on 'Maximum lengths of vegetation in the school ground at various times of year' as far longer than the section on the 'Performance specification for and maintenance of the school network, PCs and software'! Furthermore when I benchmarked this 'Performance specification...' against the National Curriculum ICT attainment targets, it was clear the people who wrote this spec were operating at around level three. In other words, their level of understanding and proficiency was what one might expect of the average seven-year-old at the end of Key Stage One! My 'mission impossible' ...should I chose to accept it, is to impose some 'reality therapy' on this school's management. However given I'm only a volunteer I'm balking at the prospect. Wish me luck! David Bowles
participants (4)
-
David Bowles
-
G.Harris
-
Paul Graydon
-
Phil Driscoll