Nancy:

Both the MSI and EXE installers distributed from openafs.org are
designed to upgrade previous IBM AFS clients.   Of course, it is
preferable to perform a clean uninstall of IBM AFS first.   Performing
an uninstall via Add/Remove Programs of the IBM AFS client should
be successful unless it is old.   There is strong evidence to indicate
that IBM AFS 3.6.5 does not uninstall properly.

The most important thing to check after an uninstall is that the
PATH environment variable in the System control panel no longer
includes the IBM AFS path.   That way even if there are old binaries
left behind they won't be picked up when OpenAFS is starting.

There should be no parts of an uninstall of IBM AFS that is Windows
version dependent.  Be aware that you should wait for the announcement
of OpenAFS 1.4.0 this week before installing clients on Windows XP SP2
or Windows 2003 SP1.  There was a bug in the Windows Internet Connection
Firewall processing that prevented the firewall from being properly
configured to allow AFS callbacks to be passed through.

Also note that if your machines are part of a domain the best way to
distribute OpenAFS for Windows is via a MSI transformed to include
the configuration specific to your environment.  See the release notes
for details on how to generate a transform.  Secure Endpoints Inc.
can be hired to assist you in developing transforms or providing
additional support.

Jeffrey Altman
Secure Endpoints Inc.


Nancy Wallace wrote:

> Hello,
> 
> We have a large user base for AFS, some of whom are using the last
> version of the Transarc client. We'd like to migrate all of them to
> OpenAFS if possible. My two main questions at this point are:
> 
> * Is it possible to do a clean uninstall of the Transarc client without
> having to completely re-install Windows?
> 
> * Are there any parts of the removal process that are Windows
> version-specific? (Most of our users are on XP, but there are some on
> 2000 and a few departments that may be on even older systems.)
> 
> Any advice would be appreciated. Thanks!
> 
> 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to