[3] in winnt
Minutes from 2/18/97 Kick-off mtg on WinNT at MIT
daemon@ATHENA.MIT.EDU (Rob Smyser)
Mon Mar 17 17:35:24 1997
To: winnt-mtg@menelaus.local
Date: Mon, 17 Mar 1997 17:35:20 EST
From: Rob Smyser <smyser@MIT.EDU>
------- Forwarded Message
Received: from SOUTH-STATION-ANNEX.MIT.EDU by po8.MIT.EDU (5.61/4.7) id AA27574; Thu, 20 Feb 97 14:34:32 EST
Received: from MIT.MIT.EDU by MIT.EDU with SMTP
id AA03738; Thu, 20 Feb 97 14:34:30 EST
Received: from MA-JONES.MIT.EDU by MIT.MIT.EDU (5.61/4.7) id AA01711; Thu, 20 Feb 97 14:34:28 EST
X-Sender: sbjones@po7.mit.edu
Message-Id: <v02140b21af3252fc14e5@[18.81.1.48]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 20 Feb 1997 14:35:13 -0500
To: awillis@MIT.EDU, pbh@MIT.EDU, goguen@MIT.EDU, seant@MIT.EDU,
sampson@MIT.EDU, sharari@MIT.EDU, tregan@MIT.EDU, azary@MIT.EDU
From: sbjones@MIT.EDU (Susan B. Jones)
Subject: NT Meeting 2/18 -- DRAFT
Cc: sbjones@MIT.EDU, cavan@MIT.EDU, hogue@MIT.EDU.janat, ljr@MIT.EDU,
dbaron@MIT.EDU, nschmidt@MIT.EDU, rar@MIT.EDU, smyser@MIT.EDU,
kelley@MIT.EDU, mbarker@MIT.EDU, rferrara@MIT.EDU, tytso@MIT.EDU
I think this is going to everyone who attended the meeting. If you know
someone I left off, please forward this to that person.
If I have misrepresented anything please send complaints to me and I will
fix them. This is a draft. -- SBJ
NT Meeting Minutes
Attending: Jana Tarasenko, Lorraine Rappaport, Barbara Goguen, Dennis
Baron, Naomi Schmidt, Al Willis, Bill Hogue (chair), Roger Roach, Rob
Smyser, Peter Kelley, Mike Sampson, Sean Tappendorf, Mike Barker, Theresa,
Regan, Dave Lambert, Tim McGovern, Paul Hill, Susan Minai-Azary, Bob
Ferrara, Ted T'so, Mohammed Sharari, Susan Jones.
SUMMARY submitted by tregan:
We are still endorsing Windows NT 4.0. Here a few items that we can move
ahead with while other issues are pursued.
* We can price out the OS system upgrade and we can reach out to the
Release I community.
* We can price out the memory upgrade.
* We can price out MS Office for NT (Windows '95).
* We can position that other software purchases are their responsiblities.
Question: Should we open the discussion of how to handle remote access to
include LOEs?
===========
Bill opened the meeting by reminding us that the purpose of the meeting was
to revisit the NT report. The short term goal was to be able to provide a
reasonably clear statement of:
* what we support
* what are the implications for the supported systems
and to ensure that we identify action items, assign them and move forward.
Agenda for NT Meeting of 2/18/97
1. Is it possible to agree on a common list of action items? Some
candidates:
* Integration Testing - going well and there is a report (however, there is
some software purchased for Release I and how do we wish to handle (Lotus,
WordPerfect, KeaTerm, etc.)) Also, there may be an upgrade issue for
MicroSoft Access. And, what about Office '97?
Aside from Management Reporting experiences, and the deployments to
SHSS/SOA/Physics, ksign does not presently run under NT4.0.
Mohammed's Report: Mohahmmed handed out the "spreadsheet" below that shows
the applications he has tested on NT and how they fared. People suggested
other applications that he ought to test, including: ProComm, FileMaker,
PageMaker, BrioQuery(?). Theresa added that everything also ought to be
tested over Tether using NT.
========================================================================
Integration testing for MS Windows NT 4.0 workstation
Application Source Results Comments
KrbV4 net-dist pass
DrSolomon /NT v7.67 MIT pass MIT Security Office
SQL*NET 2.3.2.1.5 oracle pass
ANO 2.3.2.1.5 oracle pass
PB4 Dkit Powersoft pass
PB5 Dkit Powersoft pass
KrbV5 N/A Availabilty Feb 97
Eudora 2.2 net-dist pass
Eudora 2.1.2 net-dist pass
Netscape 3.01 net-dist pass
Netscape 3.0 net-dist pass
MS Office 4.2 Microsoft pass Standard
MS Project 4.0 Microsoft pass
Leash v1.3 net-dist pass
NT4 FTP NT4 pass
NT4 Telnet NT4 pass Poor Terminal
Emulation
Tether Services net-dist pass
TCP3270 v2.60.07 net-dist pass
KTN3270 N/A
SumMIT CAO Testing by sponsoring depts
SPMS OSP Testing by sponsoring depts
SAP SAP Testing by sponsoring depts
ECAT ECAT Testing by sponsoring depts
Tested on DELL Optiplex GXL 5100 PC with 16MB RAM
========================================================================
Comment: we need local support people to help identify what we nee to test.
Comment:What about people who don't move to supported products, but keep
using, e.g., Lotus 1-2-3, WordPerfect, KeaTerm, TechMail.
Answer: We won't be testing these apps. Lots of people will be happy to
switch from KeaTerm when they can have KTN3270.
Discussion of who should test unsupported apps. Consensus seems to be that
local experts should do the tests in the Integration Lab.
Help Desk should probably know more about unsupported products in order to
be able to answer general questions like, I guess, that doesn't woirk with
NT or that does if...
Paul asked if the lab has a TechNet subscription
ACTION ITEM: MOHAMMED WILL SUBSCRIBE TO TECHNET
* Administrator's password - Ted and Paul can speak to
this more eloquently than I.
Paul and Ted explained the problem. NT systems come with an administrative
password which is basically a root password. If this is left on, whoever
knows the password has access to the whole system (which? the machine's or
MIT's?) As Dennis mentioned, this sounds much like the problems that we
faced with the Mac upgrades to System 7.0 which had file sharing has the
default.
There was much discussion about what should be done about this problem with
solutions ranging from turning off sharing, to partition ing the disk and
having one piece be administrative and one not.
One of the other problems is the need for passwords. Macs and PCs don't
require passwords. NTs require passwords at startup and for loading
software and (what else?)
A variety of solutions were offered, but the discussion was ended with two
action items emerging.
ACTION ITEM: PAUL, MIKE, AND THERESA WILL EXPLORE THE VARIOUS SOLUTIONS
AND COME UP WITH A SINGLE SOLUTION
ACTION ITEM: SUSAN WILL TELL THE ROBYN THAT i/s SHOULD PLAN TO RUN SEVERAL
ARTICLES ON NT, ONE OF WHICH WILL BE ON FILESHARING, ETC. ON NT.
Theresa suggested that people should be encouraged to use their "Kerberos
prinicipal"* as they're NT username.
*That's the "network ID." (See 2/18 OCMG minutes, Linda Lancaster) :-)
* Licenses - to date, we have spoken in terms of the OS.
Do we wish to consider Office '95/'97? Based on our present position with
Microsoft, should we just price it out? I am under the impression we should
be striving to use the ReEng dollars that Office Computing has available
this fiscal year.
Office 97 Al, Paul Hill, Paul Heffernan, and someone else (who?) are
meeting with Microsoft on license.
The difference between the educational price ($100) and the site license
price ($40) is substantial enough that it is worth negotiating with
Microsoft. Also NT requires a remote server licence as well. (IS THIS
CORRECT?)
* Help Desk: What does Help Desh support mean for NT? What needs to be
documented?
NT is installed on Help Desk machines and being used. The Help Desk gets NT
calls already.
One of the issues for the Help Desk is that you can't see the network setup
unless you're an administrator. (See discussion above on Administrator's
password.)
ACTION ITEM: CONVENE AN NT GROUP WITH ROB, AL, SEAN, HELP DESK PERSON
(besides Rob?), PUBS PERSON.
Al: How long would it take to be ready to support NT?
Barabara: We could use the 50 SAP NT machines to pilot.
* Other related concerns...
ISSUE: THERE ARE DATA FILE COMPATIBILITY PROBLEMS BETWEEN MS OFFICE 95 AND 97.
ISSUE: 16MB OF MEMORY IS NOT ENOUGH.
20MB is all right, 24 comfortable, higher is better.
RECOMMENDATION: NT machines should have at least 32MB of memory.
Theresa: How are we going to go back to the owners of 150 Release1
machines and recommend an upgrade?
ISSUE: SHOULD WE BUY THE APPROPRIATE LICENSES, SOFTWARE, AND MEMORY BEFORE
THE END OF THE YEAR IN ORDER TO BE READY?
2. Can we identify a single champion (project manager/coordinator?) for NT
efforts?
No champion was identified.
------- End of Forwarded Message
