Select Page

Contents

Introduction

Prior to installing the OpenAFS client on a windows machine, it is recommend you install Kerberos for Windows beforehand.

It is also recommended that you use msi installers for both products, as upgrades often do not work when upgrading from an older NSIS installation (see the note below). Computer Science provide downloads of the MSI installers for both products, these are configured for the ec.auckland.ac.nz cell for easy installation.

About Kerberos for Windows

AFS uses kerberos for authentication. The OpenAFS client comes with its own kerberos 4 libraries. Kerberos for Windows installs kerberos 5 libraries and makes them available for use by AFS. In the future we will only be running kerberos 5 so it will save you upgrading later by installing krb5 libraries now.

About the OpenAFS Client

The OpenAFS client allows windows to mount afs volumes as network drives, it is assumed that those reading this document will be familiar with this.

Please note that the msi installer for afs has issues when upgrading from a previous NSIS version. It is recommended if you have an NSIS (.exe) version of OpenAFS installed that you remove it before using either of the installation options provided in this guide.

Downloads

FOS_MIT_Kerberos_3.2.2×86.zip

FOS_MIT_Kerberos_3.2.2×64.zip

FOS_OpenAFS_1.5.64×86.zip

FOS_OpenAFS_1.5.64×64.zip

You will need the msi installers plus the files: krb5.ini, krb.con and krbrealm.con. These must be in the same directory as the Kerberos-for-Windows msi installer. (There are all in the zip file)

Installing on a standalone computer

This method is best for computers that are not in a domain or for those that want to build an image that has the client pre-installed.

  • Download FOS_MIT_Kerberos_3.2.zip and FOS_OpenAFS_1.5.52.zip to local machine.
  • Unzip everything in FOS_MIT_Kerberos_3.2.zip to a folder and double click on install.cmd to install the software.
  • Unzip everything in FOS_OpenAFS_1.5.52 zip to a folder and double click on install.cmd to install the software (reboot is needed after you install this).

Note that if you choose this option for your image – you may run into problems with sysprep due to the local loopback adapter that is installed by afs. If you must include the afs client on your image, contact SIT Windows Team about the details.

Final Note

MSI installers that are already congfigured for the ec.auckland.ac.nz cell.

After you have obtain an AFS token using EC credential, you can map the AFS share using Windows network drive mapping. For more information, please read Mapping Network Drives section.

Skip to toolbar