OpenAFS for Windows
OpenAFS is the world's foremost location independent file system. With OpenAFS for Windows, users of Microsoft Windows 2000, XP, 2003, XP64, Vista (32-bit and 64-bit editions, Server 2008 (32-bit and 64-bit editions), Windows 7 (all editions), and Server 2008 R2 (all editions) can make the most of this proven data sharing solution. The OpenAFS Project provides binary installation packages appropriate for both individual users and organizations with thousands of members.
Contents:
- All versions of OpenAFS for Windows prior to 1.5.75 are incompatible with Windows Security Update MS10-020 (KB980232).
- All versions of OpenAFS for Windows prior to 1.5.62 can experience data loss when storing data to the file server.
- Windows 7 Upgrading:
- Version 1.5.66 was the first release of OpenAFS for Windows that is supported on Windows 7.
- OpenAFS for Windows must be re-installed after a Windows 7 Upgrade. The Windows 7 Upgrade process will uninstall the Microsoft Loopback Adapter
- Version 1.5.99b (aka 1.6.0pre2) was the first release that will not lose connectivity with \\AFS when the network configuration changes.
The following guidelines should be used for choosing an installer type. If you are upgrading from a previous installation, select the same type of installer, EXE or MSI, as was previously installed on the system. If you are installing for the first time, choose the EXE if you are installing manually and the MSI if you either need to customize the installation package (via a transform) or wish to deploy via Active Directory Group Policy.
Each installer is provided in debug and non-debug versions. The debug versions should be installed only when you are experiencing a problem and you need to assist the OpenAFS developers in debugging the problem. The non-debug version is optimized for performance, does not generate logging information by default, and does not install symbol files.
All of the installers are produced and signed by Secure Endpoints Inc.. If the signature is missing do not complete the installation process and send e-mail to openafs-security@openafs.org
Secure Endpoints Inc. periodically publishes a report on the current status of OpenAFS for Windows development. The most recent report was published in July 2008. Read it today!
(updated 4 June 2011) 
Features:
- Starting with the 1.5.50 release of OpenAFS for Windows, each of the AFS Client Service, the AFS Explorer Shell Extension, and the command-line tools are Unicode enabled. No longer is OpenAFS restricted to accessing file system objects whose names can be represented in the locale specific OEM code page. This has significant benefits for end users. Most importantly it permits non-Western languages to now be used for file system object names in AFS from Microsoft Windows operating systems. Now that Unicode names are supported, Roaming User Profiles and Folder Redirection will no longer fail when a user attempts to store an object with a name that cannot be represented in the OEM code page.
- Compatible with all OpenAFS and IBM/Transarc AFS Server versions
- Support for all editions of Windows 7 and Windows Server 2008 R2
- Support for all editions of Windows Vista including SP1 and Windows Server 2008
- AFS credentials module for Network Identity Manager version 1 and version 2
- Support for 64-bit File Sizes on both 32-bit and 64-bit versions of Microsoft Windows
- Support for all AMD64 64-bit Windows platforms
- Implements Windows Byte Range Locking backed by AFS File Server Locks
- New commands:
- fs uuid [-generate]
- fs chown -owner <user name or id> [-path <dir/file path>+] [-literal]
- fs chgrp -group <user name or id> [-path <dir/file path>+] [-literal]
- Improved CIFS protocol compatibility
- Compatible with XP, XP64, Server 2003, Vista, Server 2008, Windows 7 and Server 2008 R2.
- Supports the SRVSVC and WKSSRV services providing an improved \\AFS browsing experience.
- Hard Dead and Connection Timeout values restricted to the CIFS Session Timeout value.
- CIFS Extended Timeouts are automatically detected when supported by the installed version of mrxsmb.sys. See Microsoft Hot Fixes.
- Improved handling of Windows Standby/Hibernate modes when network access is unavailable
- Fixes critical data loss errors:
- Prior to 1.5.15, write requests queued for background processing were not retried upon failure.
- Prior to 1.5.62, write requests whose file offset is not an even multiple of the cache buffer block size would fail to store all of the dirty data.
- Prior to 1.5.62, write requests to file servers that have 2GB file limits (aka IBM file servers and OpenAFS file servers older than 1.3.70) can fail to store dirty data on the first StoreData RPC after a InitCallBackState RPC is received.
- Increased cache hit ratio for data written to AFS by the local client
- Improved behavior when used behind Network Address Translation (NAT) devices
- Default chunk size increased to 1MB from 128KB as of 1.5.23 improving read and write performance.
- The 1.5.53 release fixed a significant memory leak (rx packets) in the rx rpc protocol library.
- The 1.5.56 and 1.5.57 releases fixes race conditions in the rx rpc protocol library that can result in the AFS Client Service terminating prematurely.
- The 1.5.60 release converts all documentation to Windows HTML Help and adds registry support for CellServDB information.
- 1.5.66
- Network Identity Manager OpenAFS Provider now provides its own "AFS lock" notification icon to report the status of "have tokens, have no tokens, service not started, service started but inaccessible". Hovering over the icon lists the cells for which tokens exist (if any) and the OpenAFS version
number. Double-clicking executes the Network Identity Manager default action. - disables the drive mapping functionality in the AFS Authentication Tool (afscreds) and AFS Configuration Tool (afs_config)
- Workaround a file server bug that can be triggered when extending the length of a file.
- Adds support for DNS SRV records _afs3-vlserver._udp.<cellname> in place of DNS AFSDB records.
- 1.5.75 provides compatibility with Windows Security Update MS10-020 (KB980232).
- 1.5.77 corrects an AFS RPC Path MTU discovery error that was introduced in 1.5.76.
- 1.5.99b corrects an error that caused Windows to lose connectivity with the \\AFS server after a network configuration change.
Documentation:
Supported Platforms:
- Windows 7 (X86 and AMD64)
- Windows Server 2008 R2 (AMD64)
- Windows Server 2008 (X86 and AMD64) including SP1
- Windows Vista (X86 and AMD64) including SP1 and SP2
- Windows 2003 64 (AMD64) including SP1 and SP2
- Windows XP 64 (AMD64) including SP1 and SP2
- Windows 2003 R2 including SP1
- Windows 2003 including SP1 and SP2
- Windows XP including SP2 and SP3
- Windows 2000 Workstation and Server at SP4
* Installers for Itanium systems are unavailable. Organizations interested in support for Itanium should consider donating a development/test system to OpenAFS. Known Issues:
- If a *beta* AFS plug-in for Network Identity Manager is installed, it must be uninstalled before OpenAFS 1.5.99f is installed. Otherwise, an error indicating that the plug-in cannot be installed because the appropriate version of OpenAFS is not installed will be generated.
- The AFS plug-in for Network Identity Manager provided as part of OpenAFS 1.5.99f requires MIT Kerberos for Windows 3.1 or above.
- Directory and File Change Notifications are ignored when accessing AFS via UNC paths
- Windows Vista Specific Issues
- Windows 7 and Server 2008 R2 Specific Issues
- There is a bug in Windows that will prevent access to \\AFS after an IP address has been removed or assigned after boot. When the bug is triggered, all attempts to connect to \\AFS will result in a "Bad Network Name" error. Please reproduce this issue locally and submit bug reports to Microsoft.
- All Vista issues apply as well.
Downloads for 32-bit Windows operating systems: Win7/2008/Vista/2003-R2/2003/XP/2000:
Downloads for 64-bit Windows operating systems: 2008-R2/Win7/2008/Vista/2003-R2/2003/XP:
Support for 32-bit Windows Applications on 64-bit Windows operating systems
This installer is required for any 32-bit applications that require use of AFS libraries. This includes 32-bit versions of MIT Kerberos for Windows.
Note: In 64-bit versions of Microsoft Windows there are 64-bit and 32-bit versions of the command prompt and the Explorer Shell. It is very important that when installing applications that the installers be started from a 64-bit process. It is strongly recommended that the Add/Remove Programs Control Panel be used to initiate installations on 64-bit Microsoft Windows operating systems.
OpenAFS for Windows depends on MIT Kerberos for Windows (KFW) to provide Kerberos 5 functionality. The recommended version of KFW for OpenAFS for Windows 1.5.99f is version 3.2.2. 64-bit releases of KFW are available from Secure Endpoints Inc.KFW 3.2.2 ships with Network Identity Manager version 1.3.1. Secure Endpoints provides version 2.0 as a free update.
Microsoft Hotfixes
Just as OpenAFS releases fixes on a continuous basis, so does Microsoft for their Windows products. If they are security related or deemed to be critical to the entire user base these hot fixes are pushed out via Microsoft's Windows Update service. However, if the fix is considered to be relevant only to a small user community, the hot fix is made available via a posting to Microsoft KnowledgeBase. When a new service pack is issued all of the outstanding hot fixes are rolled up and regression tested together.
OpenAFS for Windows is highly dependent on the correct operation of Microsoft's SMB redirector network file system driver and the Netbios communication stack. Over the years there have been a large number of bugs found and fixed within these two subsystems. At the present time there a hot fixes that have been issued by Microsoft which have yet to be bundled into a service pack for XP 32-bit, XP 64-bit and Server 2003. Hot Fixes that are considered critical for OpenAFS users are marked as such below.
Microsoft Windows Server 2003 and XP64
The current service pack level is 2.
Microsoft Windows XP
The current service pack level is 3.
