-OpenAFS for Windows 1.3.80 Installation Notes
+OpenAFS for Windows 1.3.8300 Installation Notes
---------------------------------------------
The OpenAFS for Windows product was very poorly maintained throughout the
of the Status Cache and all requests will result in network operations.
If you are experiencing poor performance you might want to increase the
-maximum number of Status Cache entries. Each entry requires 164K. Only
-those entries which are used are allocated.
+maximum number of Status Cache entries. Each entry requires approximately
+1.2K. Note that the default number of Status Cache entries was increased
+to 10,000 starting in 1.3.80.
26. "Netbios over TCP/IP" must be active on the machine in order for
-addrs print only host interfaces
-cache print only cache configuration
+37. If you are a site which utilizes MIT/Heimdal Kerberos principals
+to logon to Windows via a cross-realm relationship with a multi-domain
+Windows forest, you must enable Windows logon caching unless the
+workstation is Longhorn Beta 1 or later.
+
+
+38. VLDB and File Server Preferences can now be provided initial
+values using registry keys. This is useful for managed machines in a
+Windows domain which are centrally located (e.g., in a computing
+lab.) See registry.txt for details on the "Server Preferences" keys.
+
+
+39. As of 1.3.81, timestamps on file stored in AFS are reported to
+Windows in UTC all year round. Previously, in locales with daylight
+savings time, the time reported by AFS to Windows when DST is active
+was UTC+1. This was done to preserve the relative local time for the
+user. A file stored at 11:00am EST in January would be reported as
+having been stored at 11:00am EDT in June. Unfortunately, this has
+the negative side effect of changing the reported timestamp from 16:00UTC
+to 15:00UTC. Since Windows treats all file times in UTC, data
+synchronization applications which rely on the timestamp would believe
+that all files stored in AFS had changed. This will no longer be the
+case.
+
+It should be noted that Unix based operating systems (such as Solaris)
+do not appear to report file times to applications in UTC. They do
+preserve the relative local time. This may confuse some users who are
+used to being able to compare the timestamp in an Unix shell with the
+timestamp from the Windows explorer. During DST, these two times will
+no longer agree even though they are in fact describing the same time.
+
+
+40. If the installer refuses to install and complains about an RPC
+configuration error, check to ensure that the following registry
+entries are present and that they refer to the dll "rpcrt4.dll":
+
+ HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncacn_np"
+ HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncacn_ip_tcp"
+ HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncadg_ip_udp"
+
+
+41. Starting in 1.3.83, when Integrated Logon is used in conjunction
+with KFW, the Kerberos 5 tickets obtained during the process of
+generating AFS tokens are preserved and stored into the default
+ccache within the user logon session.
+
+
+42. 1.3.83 adds a new command, "fs minidump". This command can
+be used at any time to generate a mini dump file containing the
+current stack of the afsd_service.exe process. This output can
+be very helpful when debugging the AFS Client Service when it is
+unresponsive to SMB/CIFS requests.
------------------------------------------------------------------------
Bug reports should be sent to openafs-bugs@openafs.org. Please include as
much information as possible about the issue. If you are reporting a crash,
please install the debugging symbols by re-running the installer. If a dump
-file is available for the problem include it along with the AFS Client Trace
-file %WINDIR%\TEMP\afsd.log. The AFS Client startup log is
-%WINDIR%\TEMP\afsd_init.log. Send the last continuous block of log
-information from this file.
+file is available for the problem, %WINDIR%\TEMP\afsd.dmp, include it along
+with the AFS Client Trace file %WINDIR%\TEMP\afsd.log. The AFS Client
+startup log is %WINDIR%\TEMP\afsd_init.log. Send the last continuous block
+of log information from this file.
Configuring DrWatson to generate dump files for crashes: