[8352] in Info-AFS_Redistribution
RE: SMS and Win2k AFS Client 3.6
daemon@ATHENA.MIT.EDU (Buhrmaster, Gary)
Thu Dec 28 19:23:51 2000
Content-return: allowed
Date: Thu, 28 Dec 2000 16:00:02 -0800
From: "Buhrmaster, Gary" <gtb@slac.stanford.edu>
To: "'Bo Tretta'" <botretta@jpl.nasa.gov>, info-afs@transarc.com
Message-id: <76A109862EAED4119176009027EECD1E19ABD2@AGAMEMNON.SLAC.Stanford.EDU>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Hi,
We just recently identified this incompatibility, and plan to
report it as a bug to Transarc/IBM when our location reopens
at the beginning of the new year.
So, you are not alone, and we do not have any bypass at
this time.
Gary
> -----Original Message-----
> From: Bo Tretta [mailto:botretta@jpl.nasa.gov]
> Sent: Thursday, December 28, 2000 2:49 PM
> To: info-afs@transarc.com
> Subject: SMS and Win2k AFS Client 3.6
>
>
>
> Hi,
>
> The new AFS client 3.6 works great under Windows 2000 as does
> Microsoft
> SMS 2.0.
>
> However, the issue is that if SMS 2.0 is installed, the provided AFS
> installer hangs at setup /SMS.
>
> If the AFS client exists on a system, then the SMS client installation
> may
> fail to complete and hangs the computer. If the install
> completes, upon
> system restart, a window appears on top that indicates that
> winnt\system32\services.exe terminated unexpectedly with status code
> 128.
>
> I would like to know if Transarc or anyone else has received other
> reports of this apparent conflict and can suggest a remedy. I am
> completely behind the AFS client
> availability but this development throws a real kink into our
> protective
> measures compliance and SMS deployment plans.
> --
> Bo Tretta
> PH# : 3-4496
> M/S : 600-174
> Note : "Opinions expressed herein have not been approved by JPL."
>
