[124] in Kakapo Windows Team

home help back first fref pref prev next nref lref last post

Minutes from 10/02 Kakapo mtg.

daemon@ATHENA.MIT.EDU (Brian Murphy)
Mon Oct 6 08:50:50 2003

Message-Id: <5.0.2.1.2.20031002125917.01591560@po12.mit.edu>
Date: Mon, 06 Oct 2003 08:48:41 -0400
To: kakapo@mit.edu
From: Brian Murphy <bmurphy@MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Attending:

Brian M. Phil, L. Tom T. Chad D. Jonathon W. Jonathan H. Paul H., Kerem, Tom C.

The general topic of conversation was how to ensure Kakapo dealt with the 
appropriate issues and did not re-hash topics from other meetings. There 
was general agreement that we would serve a more useful purpose by dealing 
with higher level issues as opposed to technical solutions to specific 
problems.

There was agreement that we need to develop a presence on the web and begin 
to create polices as issues arise. Some details of the conversation are below.


Kerem to have domain and owners page list by tonight
3-down type of communication vehicle would be helpful.

We still need a list of all windows services offered. We have some but not all.
There is some inconsistency in information being put out as well as 
possible holes
(Things not covered or assigned to anyone or team in particular)

WEB IS Topics would be a logical starting point for a Kakapo link.

Oliver/Brian work on prototype for web

List of issues:

Container Request: MechE
Run by 3rd yr phd student
run their own domain
8-9 machines
SW installers for 30 machines
Chad spoke with them.
Turn existing domain server into member server
Profile management issues - Need developers time/resource
Should we address these issues now or later. How much  cleanup if later?
If they use our MSI's it's better for everyone.
Dept's have option to load their own sw and image their own machines.
Need mechanisms to cleanup corrupted profiles (web service)
Need faculty sponsor/involvement Chad to get the name of sponsor, otherwise 
approved.

What is our level of commitment if not a pilot.
WIN domain no longer a pilot (Once Jim presented to Treasurer)

37 we have implied some long term commitment but need to come up with long 
term policies such as  who can teach, who supports what SW etc..

Recommend Dept's install our software (the ones we have)
Who maintains new MSi for new versions of our software - we'll look into it 
as new versions come out. Who is we?
Tell DUSP thier software (even if we helped) is there responsibility.
List our sw and make a recommendation of who and how to support it. Chad to 
come up with the list of sw we need to consider.

Joe Calzerreta patched retail cd SP1 latest pacthes

Distributed through volume distirbution

Students will need license key

Testing next week.

Help Desk needs tool to identify owners and other information of 
win.mit.edu machines. Kerem to get together with Oliver and get list of 
what info the Helpdesk needs.


Laptops - Tom distributed draft version. More detail documents forth 
coming. People can comment on draft.
Are we willing to offer laptop support service officially?  Full document 
expected this month we can decide after reviewing full document.

Closing announcement for domain project coming out next week.
Phil and Theresa will be the request points for new domain members.


home help back first fref pref prev next nref lref last post