[258] in Kakapo Windows Team
Meeting Thursday 1/8/04 10:00am W20-PDR3 & FW: Last meeting notes
daemon@ATHENA.MIT.EDU (Brian Murphy)
Wed Jan 7 09:45:09 2004
Reply-To: <bmurphy@MIT.EDU>
From: "Brian Murphy" <bmurphy@MIT.EDU>
To: <kakapo@mit.edu>
Date: Wed, 7 Jan 2004 09:45:02 -0500
Message-ID: <003901c3d52c$d4ff3c00$a200bb12@bmurphy>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Happy New Year everyone,
Below are the notes from the last meeting (Thanks Richard). Also at the
last meeting we had a general consensus to change the Kakapo meeting
time to Thursday mornings from 10:00-11:30. I have reservedW20-Pdr3 for
tomorrow morning. If there is any major conflict with this time please
let me know. The agenda items that Richard had proposed are included at
the bottom of this message. Please review them and let us know if there
is a topic anyone is inclined to go off and research. Thanks....Brian
-----Original Message-----
From: Richard Edelson [mailto:redelson@MIT.EDU]
Sent: Tuesday, January 06, 2004 4:06 PM
To: bmurphy@mit.edu
Subject: Re: Last meeting notes
Kakapo 12/18/03
We spent some time discussing various details of closing week.
Chad brought up the question of RIS for EECS laptops (about 100
machines).
Because of the special conditions of the network they will be using, he
will not use RIS for these machines, but will join them instead.
We discussed the status of the external review report.
Theresa presented a document on the status of NT 4 > Windows 2000 domain
migrations. And an overview of where we are at this time.
Chad has been in contact with Sloan regarding their win.mit.edu
evaluation.
They are considering migrating some lab/public machines to the central
domain. Sloan has also asked about the availability of Exchange in this
environment in the context of a larger migration, but it is not certain
at
this time that Exchange will be one of their requirements.
Proposed agenda Topics:
1). SLA's for win.mit.edu customers. General SLA for the service and
possibly some more specific ones for some customers.
2). Event Management: Response times, Levels of events, Escalation
3). Change Management: Patching, time windows, notification policies,
testing criteria
4). Roles of support groups
5). Software distribution: web, msi's
6). Application support: Enterprise apps, Desktop apps
7). Release Engineering
8). Documentation
9). Support Model
10). Scope of central domain, purpose of independent domains
11). Evaluation: Review of new Windows service offerings / extended
services
12). Security: Model/distribution. How proactive should IS be. can we
provide more granular choices to customers. Review of processes, i.e.
how
patches are evaluated.
