2.1 Supported Operating Systems
2.1.1 Unsupported Operating Systems
2.3 Additional Software Packages
3.1. Requirements for Kerberos v5 Authentication
3.1.2. Using the krb524 service
3.1.3. Network Identity Manager Provider
3.2. Use of the Microsoft Loopback Adapter by the AFS Client Service
3.3. Using Freelance (Dynamic Root) Mode to Improve Mobility
3.4. Locating AFS Volume Database Servers via DNS
3.5. Obtaining AFS Tokens as a Integrated Part of Windows Logon
3.6. AFS System Tray Command Line Options
3.7. The “AFS Client Admins” Authorization Group
3.8. OpenAFS support for UNC paths
3.10. OpenAFS Servers on Windows are Unsupported
3.10.1. OpenAFS Server Installation
3.10.2. Using the AFS Client Service when the Server is installed
3.11. OpenAFS Debugging Symbol files
3.12. Large File (64-bit) Support
3.13. Encrypted AFS Network Communication
3.14. Authenticated Access to the OpenAFS Client Service
3.16. Microsoft Windows Internet Connection Firewall
3.17. Browsing AFS from the Explorer Shell and Office
3.19. Automatic Discarding of AFS Tokens at Logoff
3.20. Windows Terminal Server installations
3.23. NETBIOS over TCP/IP must be enabled
3.24. OpenAFS binaries are digitally signed
3.25. Maximum Size of the AFSCache File
3.27. Known Character Set Issues with Roaming Profiles
3.29. Restricting OpenAFS Client Service Start and Stop
3.31. Symlinks to AFS UNC paths
3.32. Cache Manager Debugging Now Supported
3.33. Windows Logon Caching vs. Kerberos Logons
3.34. Initial Server Preferences
3.36. Windows RPC client support must be installed
3.37. Generating Minidumps of the OpenAFS Client Service
3.38. AFS Client Universally Unique Identifiers (UUIDs) vs. System Cloning
3.39. Delayed Write Errors with Microsoft Office Applications
3.40. Global Drives (aka Service Drive Letters) are no longer supported by Microsoft
3.41. 64-bit Microsoft Windows Installations
3.42. Known Issues with Microsoft Windows Vista
3.43. New AFS Share Name Syntax Provides Direct Access to Volumes
3.44. Differences between Windows and UNIX “fs examine”
4. How to Debug Problems with OpenAFS for Windows:
4.1. pioctl debugging (IoctlDebug registry key)
4.2. afsd_service initialization log (%WinDir%\TEMP\afsd_init.log)
4.3. afsd_service debug logs (fs trace {-on, -off, -dump} ->%WinDir%\TEMP\afsd.log)
4.4. Using SysInternal’s DbgView and ProcMon or FileMon Tools
4.5. Microsoft MiniDumps (fs minidump -> %WinDir%\TEMP\afsd.dmp)
4.6. Single Sign-on (Integrated Logon) debugging
4.7. RX (AFS RPC) debugging (rxdebug)
4.8. Cache Manager debugging (cmdebug)
4.9. Persistent Cache consistency check
6. How to Contribute to the Development of OpenAFS for Windows
6.3. Direct contributions of code and/or documentation
6.4. OpenAFS for Windows Mailing Lists
7.2.1.2 OpenAFS for Windows Properties
7.2.1.2.2 AFSCreds.exe Properties
7.2.2 Existing Registry Entries
7.2.3 Replacing Configuration Files
7.2.3.1 Components for Configuration Files
7.2.4 Adding Domain Specific Registry Keys
7.2.5 Adding Site Specific Freelance Registry Keys
Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
Value: daemonCheckDownInterval
Value: daemonCheckLockInterval
Value: daemonCheckTokenInterval
Value: daemonCheckOfflineVolInterval
Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters\GlobalAutoMapper]
Value: <Drive Letter:> for example "G:"
Regkey: [HKLM\SOFTWARE\OpenAFS\Client]
Regkey: [HKLM\SOFTWARE\OpenAFS\Client\CSCPolicy]
Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Freelance]
Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Freelance\Symlinks]
Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Submounts]
Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Server Preferences\VLDB]
Value: "hostname or ip address"
Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Server Preferences\File]
Value: "hostname or ip address"
A.2. Integrated Logon Network provider parameters
Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]
A.2.1 Domain specific configuration keys for the Network Provider
[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]
[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]
[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain"domain name"]
[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]
A.2.1.1 Domain specific configuration values
A.2.1.2 Selection of effective values for domain specific configuration
A.3. AFS Credentials System Tray Tool parameters
Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
Regkey: [HKLM\SOFTWARE\OpenAFS\Client] [HKCU\SOFTWARE\OpenAFS\Client]
Value: AcceptDottedPrincipalNames
Regkey: [HKCU\SOFTWARE\OpenAFS\Client]
Regkey: [HKCU\SOFTWARE\OpenAFS\Client\Reminders]
Regkey: [HKCU\SOFTWARE\OpenAFS\Client\Active Maps]
Value: "upper case drive letter"
Regkey: [HKCU\SOFTWARE\OpenAFS\Client\Mappings]
Value: "upper case drive letter"
A.4 OpenAFS Client Service Environment Variables