[8354] in Info-AFS_Redistribution
RE: SMS and Win2k AFS Client 3.6
daemon@ATHENA.MIT.EDU (Touretsky, Gregory)
Thu Dec 28 19:39:38 2000
Message-ID: <CB46341FECBDD111832600A0C926615A0784CEE7@hasmsx31.iil.intel.com>
From: "Touretsky, Gregory" <gregory.touretsky@intel.com>
To: Bo Tretta <botretta@jpl.nasa.gov>, info-afs@transarc.com
Date: Thu, 28 Dec 2000 16:15:00 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
We have the same problem. We are working closely with IBM and MS to solve
it.
For now, we got a hotfix from MS (services.exe) that seems to be fine.
Gregory Touretsky
IDC Computing / Systems Engineering Group
Unix Server Platforms
gregory.touretsky@intel.com
> (+) 972-4-865-6377, Fax: 04-865-5999
iNET: 465-6377, M/S: IDC-1B
-----Original Message-----
From: Bo Tretta [mailto:botretta@jpl.nasa.gov]
Sent: Friday, December 29, 2000 12:49 AM
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."
