[397] in Kakapo Windows Team
[Kakapo] Meeting Notes for April 28, 2004
daemon@ATHENA.MIT.EDU (Marshall Vale)
Wed Apr 28 15:23:42 2004
Mime-Version: 1.0 (Apple Message framework v613)
To: kakapo@mit.edu
Message-Id: <912FC412-9949-11D8-92BD-000393924756@mit.edu>
From: Marshall Vale <mjv@mit.edu>
Date: Wed, 28 Apr 2004 15:23:45 -0400
Content-Type: multipart/mixed; boundary="===============36343754271682838=="
Errors-To: kakapo-bounces@mit.edu
--===============36343754271682838==
Content-Type: multipart/alternative; boundary=Apple-Mail-3--353673210
--Apple-Mail-3--353673210
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Agenda
Notes
Anti-spyware
requests have been strongly increasing from the community
quick research has been done with what other schools have been
doing
list of tools (Spybot, Adaware, Virusscan)
problem is there is no perfect tool
free versions mostly require manual updates
VirusScan is already a licensed tool so that may help
But it won't be available until September with current
schedule
Tools produce rather scary reports, not all warnings are truly
problems
Since there is such a range of tools to have coverage, should
we publish some example reports and which items are valide
produce documentation, get the word out through variety of
channels
Spybot has some ability to block installation
Also HijackThis and CWShredder however they are more techie
oriented
SWRT is driving the effort
VirusScan Enterprise and SP2
The auto update service fails to run after upgrading SP2
Paul has reported the conflict to Microsoft
VirusScan 7.5 does not have the conflict but not out until the
fall
Proposed solutions
release 7.1 even though 7.5 will be released not too soon
thereafter
Solution
Produce 7.1, have it ready to go before SP2 is released.
Prep doc and installer to communicate out.
SWRT will drive this work
SUS
Goal is for production announcement at IT Partners luncheon,
May 12th
Most concerns are around documentation, URLs, etc.
Proposed name: MIT Auto-Update Service
Documentation change needs:
formatting of the patches
list of the patches
minor navigation within in the page
simpler links to getting more information about each
patch
SUS machine will add a redirect to the final documentation
We believe that we can meet this announcement date
Target to have all documentation ready for Friday, May 7th
SUS server will be able to be updated in the window
inbetween
Support identification and escalation for domain machines
There are a number of tools that can pull up the information
Windev is developing a java servlet to pull together the
aggregate information and display it appropriately via web
Questions regarding where it would be hosted (hd or netops)
this is an internal service, and it should be fine to host
on wince; pulling together teams across IS&T helps understand the needs
If the scope expands (machines in other domains, etc.)
revisit as a separate dev/service project
is there a way to describe when it matters if the workstation
is or is not in the domain when reporting problems?
follow all the normal troubleshooting steps
if the need is to reinstall or problem gets too complex,
escalate to the container admin
--Apple-Mail-3--353673210
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
charset=US-ASCII
<fontfamily><param>Helvetica</param>Agenda
Notes
Anti-spyware
requests have been strongly increasing from the community
quick research has been done with what other schools have been
doing
list of tools (Spybot, Adaware, Virusscan)
problem is there is no perfect tool
free versions mostly require manual updates
VirusScan is already a licensed tool so that may help
But it won't be available until September with current
schedule
Tools produce rather scary reports, not all warnings are truly
problems
Since there is such a range of tools to have coverage, should
we publish some example reports and which items are valide
produce documentation, get the word out through variety of
channels
Spybot has some ability to block installation
Also HijackThis and CWShredder however they are more techie
oriented
SWRT is driving the effort
VirusScan Enterprise and SP2
The auto update service fails to run after upgrading SP2
Paul has reported the conflict to Microsoft
VirusScan 7.5 does not have the conflict but not out until the
fall
Proposed solutions
release 7.1 even though 7.5 will be released not too soon
thereafter
Solution
Produce 7.1, have it ready to go before SP2 is released.
Prep doc and installer to communicate out.
SWRT will drive this work
SUS
Goal is for production announcement at IT Partners luncheon,
May 12th
Most concerns are around documentation, URLs, etc.
Proposed name: MIT Auto-Update Service
Documentation change needs:
formatting of the patches
list of the patches
minor navigation within in the page
simpler links to getting more information about each
patch
SUS machine will add a redirect to the final documentation
We believe that we can meet this announcement date
Target to have all documentation ready for Friday, May 7th
SUS server will be able to be updated in the window
inbetween
Support identification and escalation for domain machines
There are a number of tools that can pull up the information
Windev is developing a java servlet to pull together the
aggregate information and display it appropriately via web
Questions regarding where it would be hosted (hd or netops)
this is an internal service, and it should be fine to host
on wince; pulling together teams across IS&T helps understand the needs
If the scope expands (machines in other domains, etc.)
revisit as a separate dev/service project
is there a way to describe when it matters if the workstation
is or is not in the domain when reporting problems?
follow all the normal troubleshooting steps
if the need is to reinstall or problem gets too complex,
escalate to the container admin
</fontfamily>
--Apple-Mail-3--353673210--
--===============36343754271682838==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
_______________________________________________
Kakapo@mit.edu
http://mailman.mit.edu/mailman/listinfo/kakapo
--===============36343754271682838==--
