>I think this is where we differ, we require re-certification at every
login.

>I imagine you not?  (I'm curious how you are doing it, since they are
always better   way's to do things, and always new things to learn)

We started out doing re-certification once everyday (during the test
phase).  We then moved to every three days for the second phase (summer
students only).  The problem with this is we could not tell the students
when they would get "kicked".  So we set it to once a week on Mondays at
4am.  The idea was that if the students had serious problems we had all
week to help them fix the problems, as opposed to leaving the students
stranded during the weekend (we have limited support on weekends).  This
has been acceptable to the students and allows automatic updates to take
effect without Clean Access enforcement.  If a problem exists in the
update problem we know about it early Monday morning and can try to fix
it before too many students notice.  Security and usability is always a
balance and for us this has been a good compromise.

Martin D. Flagg
Network Engineer/Administrator




-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List
[mailto:[log in to unmask]] On Behalf Of King, Michael
Sent: Tuesday, September 13, 2005 10:09 AM
To: [log in to unmask]
Subject: Re: Specific Windows Update failures

 

> -----Original Message-----
> From: Perfigo SecureSmart and CleanMachines Discussion List 
> [mailto:[log in to unmask]] On Behalf Of Flagg, Martin D.
> 
> You can avoid the issue of updates happening in the "middle of class" 
> by requiring re-certification once a week Monday morning at 4AM.  Our 
> students are now used to this and the helpdesk is fully staffed on 
> Monday in case of problems.  I think manually doing the updates is 
> great, but until I have a problem, I think I will let Cisco do my 
> work.
>