Overall System Status:
The Windows client from OpenAFS.org supports Windows XP/Vista/7 with the current release (as of Mar 2012). Older versions are still available, with reduced functionality. The features (1.7.x) release is recommended for Windows.
A complete installation of OpenAFS 1.5.x on 32-bit Windows XP, with screen shots, is illustrated at poosticks.dartmouth.edu/rc/content/how-do-i-install-afs-32-bit-windows (Dartmouth users only). Concise instructions for experienced users are below.
The AFS client service must be started as administrator; subsequently, non-administrator accounts can use it, but cannot modify some settings. Advanced configuration parameters such as cache size and chunk size can only be modified by administrators. On a system used with a wired network connection, performance can usually be enhanced by increasing the chunk size value to 2048 or 4096 kB. Most systems will benefit from increasing the cache size value from the default (approx. 98000) to somewhere between 200000 and 1000000. The cache size is in kB, and is used to locally cache files stored in AFS. 32-bit Windows can not use a cache larger than 1200000 (1.2GB). Consult Research Computing before changing the other parameters.
The CellServDB file must be present, but can be empty, as long as the Enable DNS option is selected. Using an empty CellServDB avoids all problems with it becoming out of date, and is adequate if only access to the local cell is needed. [Temporary bug: v1.5.66 does NOT work with an empty CellServDB file]
Various OpenAFS command line utilities, as found on UNIX and Mac OS X, are included with the client and the location is automatically added to %PATH. Running a command window will give access to these utilities (kpasswd, fs, vos etc.).
To do a clean uninstall of AFS on Windows, use the uninstall program left in C:\Program Files\OpenAFS\ (logged in as administrator).
The OpenAFS installer makes the necessary configuration rules for Windows Firewall, whether or not it is currently in use. If a 3rd party firewall is in use, it must allow all traffic to and from the loopback adapter (which appears as a network interface called AFS) and should allow inbound UDP on port 7001. All other network connections are client-initiated and usually allowed by default.
Important: Symantec EndPoint Protection (SEP Firewall). Older versions can interact badly with OpenAFS. Symantec v11.0.4 and OpenAFS versions before 1.5.68 could in some circumstances corrupt your files. The Antivirus component of SEP does not seem to cause any problems. The current (2010/04 and later) versions of SEP and OpenAFS do not have problems. If SEP Firewall is used, leave the "Browse files and printers on the network" setting ON (the default value) in the Network Threat Protection settings. If that is disabled, SEP erroneously blocks AFS authentication traffic as well as the network browsing tools.
Windows 7 users need to install v1.7 or later, to avoid problems which may prevent OpenAFS client from functioning if the system has changed IP address for any reason (sleep/hibernate and change location, switch from wired to wireless, or run VPN).
Last Updated: 11/9/12