[37] in Kakapo Windows Team
Re: win.mit.edu installers
daemon@ATHENA.MIT.EDU (Stephen Dowdy)
Sun Jul 20 09:22:02 2003
Message-Id: <5.0.2.1.2.20030720091735.029eab50@hesiod>
Date: Sun, 20 Jul 2003 09:22:19 -0400
To: "Thomas L. Thornton" <tomt@mit.edu>, contact-container-admins@mit.edu,
kakapo@mit.edu
From: Stephen Dowdy <sdowdy@MIT.EDU>
In-Reply-To: <200307200235.h6K2Zddn003996@the-rim.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Tom,
I will be on vacation and will miss the container admin meeting on
Friday. As always, the room is reserved.
However, I have one question that hopefully you can address at the meeting
and make sure it gets into the meeting minutes... You say below, that we
should NOT manually install since it might present problems in the
future. What happens to all my XP machines (and my handful of W2K
machines) where I manually installed openAFS? Since I've tested various
flavors for you over the past several months, I may have more than one
release of the openAFS. Whill I need to roll-back (uninstall) and then
re-boot to get properly synced with the domain? For example, I did the
manual things to my W2K workstation to test SP4 and took a final release
candidate from Paul to test SP4.
At 10:35 PM 7/19/2003 -0400, Thomas L. Thornton wrote:
>Container Admins and Kakapo,
>
>For those of you unfamiliar with the latter addressee, it is a new
>forum to discuss and coordinate Windows efforts around the Campus.
>For more detail see its discuss group, particularly the first minutes
>at http://diswww.mit.edu/menelaus/kakapo/16 .
>
>This note reports the latest state of the win.mit.edu installers,
>Pismere.msi v 0.2.13 and OpenAFS.msi v 1.3.2.301.
>
>Since Thursday night we have seen successful OpenAFS installs via
>Group Policy to various OS versions in a number of containers both
>inside IS and in test DLCs. Over the weekend testing continues, and
>we plan to announce to you when a GP-deployable pair of installers is
>available. We recommend against hand-installs of this test, since
>that might endanger the subsequent GP-based auto deployment. On W2K,
>once the new OpenAFS.msi installs, we see no adverse behavior from
>SP4.
>
>A minor problem with the Pismere.msi exists, so early next week
>developers plan to roll back a couple binary modules of it. Remember
>it is now separate from the AFS installer so we may deploy a minor
>upgrade release.
>
>Note that Paul and I are out Monday-Thursday next week but intend to
>remain in close contact. The Friday Container Admins will take place
>as scheduled Friday, 11:00 in E19-750. Expect detailed results of our
>work then.
>
>-Tom
