LLTI Archives

May 2004, Week 3

LLTI@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
LLTI-Editor <[log in to unmask]>
Reply To:
Language Learning and Technology International Information Forum <[log in to unmask]>
Date:
Tue, 18 May 2004 14:19:56 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
--- Forwarded Message from David Kanig <[log in to unmask]> ---

>Date: Tue, 18 May 2004 12:12:57 -0400
>To: [log in to unmask]
>From: David Kanig <[log in to unmask]>
>Subject: Windows updates and disk image management.

We've been using DeepFreeze on our lab machines so that changes users
make occur only in a shadow file, and on restart the machines go back
to an inviolate, constant image.  Under the protection of DeepFreeze,
we've been forgoing updates both to Windows and virus definitions.
However, between DeepFreeze refreshes our machines are vulnerable to
temporary infections, making them vectors for the spread of worms,
and risking automatic filtration from our network by IT scanners.

We want to be free of the labor of having to perform many Windows
updates.  We can't automate middle-of-the-night updates because on
restart by DeepFreeze in an unfrozen state, our machines require
authentication through Novell before anything can be launched.

More importantly, we want our machine configurations to be stable and
predictable through the academic year.  In the past, one or more
Windows updates has caused a third-party program to fail,
interrupting course work.

How do you manage the conflicting goals of keeping disk images stable
and responding to the deluge of Windows updates?
--
~~~~~~~~~~~~~~~~~~~~~~
David Kanig
Manager, Technical Services
Language Resource Center
Box 1935
Brown University
Providence, RI 02912

(401) 863-7090

ATOM RSS1 RSS2