Authentication Information for Cache Manager Group (Auth_Stats_group) Index: openafs/doc/html/AdminReference/auarf052.htm diff -c openafs/doc/html/AdminReference/auarf052.htm:1.1 openafs/doc/html/AdminReference/auarf052.htm:1.3 *** openafs/doc/html/AdminReference/auarf052.htm:1.1 Wed Jun 6 14:09:11 2001 --- openafs/doc/html/AdminReference/auarf052.htm Thu Jul 29 00:17:02 2004 *************** *** 54,66 **** afsmonitor program passes as arguments to the cmd_to_execute command. If any of them include one or more spaces, enclose the entire field in double quotes.
The parameters fs, cm, field_name, threshold_val, and arg1 through argn correspond to the values with the same name on the thresh line. The host_name parameter identifies the file server or client machine where the statistic has crossed the threshold, and the actual_val parameter is the actual value of ! field_name that equals or exceeds the threshold value.
Use the thresh line to set either a global threshold, which applies to all file server machines listed on fs lines or client machines listed on cm lines in the configuration file, or a --- 54,72 ---- afsmonitor program passes as arguments to the cmd_to_execute command. If any of them include one or more spaces, enclose the entire field in double quotes. +
The afsmonitor program passes the following parameters to the + cmd_to_execute: +
The parameters fs, cm, field_name, threshold_val, and arg1 through argn correspond to the values with the same name on the thresh line. The host_name parameter identifies the file server or client machine where the statistic has crossed the threshold, and the actual_val parameter is the actual value of ! field_name that exceeds the threshold value.
Use the thresh line to set either a global threshold, which applies to all file server machines listed on fs lines or client machines listed on cm lines in the configuration file, or a Index: openafs/doc/html/AdminReference/auarf059.htm diff -c openafs/doc/html/AdminReference/auarf059.htm:1.1 openafs/doc/html/AdminReference/auarf059.htm:1.2 *** openafs/doc/html/AdminReference/auarf059.htm:1.1 Wed Jun 6 14:09:11 2001 --- openafs/doc/html/AdminReference/auarf059.htm Thu Jul 29 00:03:31 2004 *************** *** 41,47 **** operations. It allows the issuer to monitor, from a single location, a wide range of File Server and Cache Manager operations on any number of machines in both local and foreign cells. !
There are 271 available File Server statistics and 570 available Cache Manager statistics, listed in the appendix about afsmonitor statistics in the IBM AFS Administration Guide. By default, the command displays all of the relevant statistics for the file server --- 41,47 ---- operations. It allows the issuer to monitor, from a single location, a wide range of File Server and Cache Manager operations on any number of machines in both local and foreign cells. !
There are 271 available File Server statistics and 571 available Cache
Manager statistics, listed in the appendix about afsmonitor
statistics in the IBM AFS Administration Guide. By default,
the command displays all of the relevant statistics for the file server
Index: openafs/doc/txt/winnotes/afs-changes-since-1.2.txt
diff -c openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.8 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.1
*** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.8 Mon Jul 26 19:24:09 2004
--- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt Tue Aug 10 00:10:44 2004
***************
*** 1,3 ****
--- 1,71 ----
+ Since 1.3.66:
+ * file and directory names beginning with "." will now be given the
+ hidden attribute when the volume access is anonymous. this matches
+ the behavior when the volume access is via an authenticated user.
+
+ * Added a change monitor to the HKLM\SOFTWARE\OpenAFS\Client\Freelance
+ key. When a change occurs mark the root.afs data as invalid and
+ for it to be reloaded on the next access. This allows administrators
+ to modify the mount point list without restarting the service.
+
+ The freelance client used to provide a fake modification time for
+ the root.afs volume data and its mount points of 7/09/2001 14:24 EDT.
+ Added code to extract the last modification time of the Freelance
+ registry key and use that instead. The time now represents the
+ most recent mount point change.
+
+ * PTS registration of new users to foreign cells has been added to
+ aklog.exe
+
+ * Additional Cache Control and Credential Manager options have been
+ added to the WiX installer. See deployment guide for details.
+
+ * The CachePath setting is now optionally a REG_EXPAND_SZ type
+
+ * The WiX installer has been upgraded. Version 2.0.1927.1 is now
+ required.
+
+ * The loopback installation code may have had a problem updating the
+ %ETC%\HOSTS file which could have resulted in a premature failure.
+ Work around code has been added for the case where the file cannot
+ be deleted.
+
+ * The default max chunksize was increased from 15 (32K) to 17 (128K)
+ because Windows sends 64K blocks when using overlapped writes.
+
+ * The default number of server threads was increased from 4 to 25 to
+ better handle overlapped writes.
+
+ * The "AfscredsShortcutParams" registry value was not being properly
+ loaded by afscreds.exe. Therefore, the default value was always being
+ used instead of the value set by the installer.
+
+ * Windows XP provides downgrade attack detection to prevent an attacker
+ from being able to force the use of NTLM simply by disrupting
+ communication with the KDC. This attack cannot exist between the
+ Windows CIFS client and the AFS Client Service. Therefore, when a
+ downgrade has been detected the afs pioctl library will force the
+ establishment of a new CIFS connection using NTLM.
+
+ * A locking error was discovered surrounding all references to volume
+ server lists within the cm_cell.c source file.
+
+ * The logged into Windows username was incorrect on Terminal Server
+ machines.
+
+ * A new registry value "NonPersistentCaching" was added to the service
+ parameters key. When set to a non-zero value, the afs cache is stored
+ in the Windows paging file. There are two limitations to choosing
+ this option:
+ 1. when persistent caching is implemented it won't work with
+ this flag set since there will be nothing to persist.
+ 2. with this flag set the initial paging allocation cannot be
+ changed while the service is running
+
+ * An initialization bug was discovered in aklog.exe which affected users
+ who have a domain name for their afs servers which could not be mapped
+ to a realm
+
Since 1.3.65:
* afs_config.exe now validates cell names against DNS in addition
to the CellServDB file.
***************
*** 63,69 ****
user's profile is not loaded from within AFS. If the profile
was loaded from AFS we can't release the tokens since the Logoff
event is triggered prior to the profile being written back to
! the its source location.
* Windows XP SP2 Internet Connection Firewall interoperability
has been added.
--- 131,138 ----
user's profile is not loaded from within AFS. If the profile
was loaded from AFS we can't release the tokens since the Logoff
event is triggered prior to the profile being written back to
! the its source location. This is now performed in an XP SP2
! safe manner.
* Windows XP SP2 Internet Connection Firewall interoperability
has been added.
Index: openafs/doc/txt/winnotes/afs-install-notes.txt
diff -c openafs/doc/txt/winnotes/afs-install-notes.txt:1.7 openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.1
*** openafs/doc/txt/winnotes/afs-install-notes.txt:1.7 Sun Jul 25 16:53:09 2004
--- openafs/doc/txt/winnotes/afs-install-notes.txt Tue Aug 10 00:10:44 2004
***************
*** 11,16 ****
--- 11,17 ----
series but also attempts to enhance the functionality of the product to better
fit the usage model of today's users. Several items standout.
+
1. The Kerberos 4 infrastructure on which the 1.2 series is reliant is no
longer secure. Cross-realm Kerberos is very important in the AFS context and
most sites have or are migrating to Kerberos 5 environments. The 1.3 series
***************
*** 18,42 ****
5 functionality including the ability to auto-renew credentials and obtain
single sign-on capabilities with the Microsoft Windows Kerberos Logon Service.
! The 1.3.65 OpenAFS client will directly use Kerberos 5 tickets as tokens if
! KFW is installed. It requires that all of the AFS Servers which it
! communicates support Kerberos 5 tickets. This requires that all servers
! be running OpenAFS release 1.2.8 or higher. Transarc servers do not support
! Kerberos 5 tickets as tokens.
!
! When using a Microsoft Windows Active Directory as your KDC for the AFS cell
! extremely large tickets may be issued. If this is your situation you either
! must modify your 1.2.x servers to support tokens larger than a few hundred
! bytes; or install the 1.3.64 or higher release on your servers.
2. The AFS Client Service does not provide robust behavior in an environment
with a plug-n-play network environment. Changes to the number of network
! adapters or the assigned IP addresses will cause the client to panic. The
! recommended work around for this problem is to install on the machine the
! Microsoft Loopback Adapter. When the MLA is installed with a static IP
! address the AFS Client Service will bind only to the loopback and not be
! affected by changes to state of other network adapters installed on the
! system.
Starting in the 1.3.65 release the installers provided by OpenAFS.org will
install the Microsoft Loopback Adapter for you with a name of "AFS" and a
--- 19,48 ----
5 functionality including the ability to auto-renew credentials and obtain
single sign-on capabilities with the Microsoft Windows Kerberos Logon Service.
! As of 1.3.65, the OpenAFS client will directly use Kerberos 5 tickets as tokens if
! KFW is installed. The client requires that all of the AFS Servers with which it
! communicates support the use of Kerberos 5 tickets as tokens (aka 2b tokens).
! This means that all of the AFS servers must be running OpenAFS release 1.2.8 or
! higher. Transarc servers do not support Kerberos 5 tickets as tokens.
!
! When using a Microsoft Windows Active Directory as the KDC which issues the
! service ticket for the AFS cell there are two things to consider. First, the
! Kerberos 5 tickets issued by Active Directory can be quite large when compared
! to tickets issued by a traditional KDC due to the incorporation of
! authorization data in the PAC. If this is your situation you either must
! modify your 1.2.x servers to support tokens larger than a few hundred bytes;
! or install the 1.3.64 or higher release on your servers. Second, Windows 2003
! Active Directory will issue service tickets utilizing the DES-CBC-MD5 enctype.
! OpenAFS releases older than 1.3.64 will not properly support this enctype.
!
2. The AFS Client Service does not provide robust behavior in an environment
with a plug-n-play network environment. Changes to the number of network
! adapters or the assigned IP addresses will cause the service to panic. The
! recommended work around for this problem is to install the Microsoft Loopback
! Adapter on the machine. When the MLA is installed with a static IP address
! the AFS Client Service will bind only to the loopback and not be affected by
! changes to state of other network adapters installed on the system.
Starting in the 1.3.65 release the installers provided by OpenAFS.org will
install the Microsoft Loopback Adapter for you with a name of "AFS" and a
***************
*** 48,90 ****
is in use, the NETBIOS name associated with the AFS Client Service is simply
"AFS". When the MLA is not in use the NETBIOS name is "MACHINE-AFS".
! With the MLA installed, UNC paths of the form \\AFS\cellname\path may be used.
! 3. When the AFS Client Service starts it must be able to contact the root.afs
! volume of the default cell. If the root.afs volume is not accessible when the
! client service is started, the service will panic. Since many users now use
! laptops or otherwise operate in disconnected environments in which a VPN may
! be needed to access the cell's servers, it is often the case that the root.afs
! volume for the default cell will not be reachable and the client service
! cannot successfully start.
! In the 1.3.65 release there is support for a fake root.afs volume which is
! dynamically constructed when the afs client service starts. This is called
! Freelance mode. Freelance mode is turned on by default in the OpenAFS.org
! installers.
!
! A couple of notes about Freelance mode. First, since the fake root.afs volume
! is constructed on the fly, when it is first used the only mount points will
! be for the default afs cell. Do not be concerned. Any attempt to access a
! valid cell name will automatically result in a new read-only mount point
! being created in the fake root.afs volume. These mount points are preserved
! between service starts in the HKLM\SOFTWARE\OpenAFS\Client\Freelance registry
! key.
!
! As of 1.3.70, Freelance mode supports read-write mount points in the fake
! root.afs volume. In addition, if the mount point list is empty, mount points
! for "cellname" (ro) and ".cellname" (rw) will be automatically generated.
! 4. The OpenAFS for Windows client will make use of AFSDB DNS records to
discover cell information when it is not located in the local CellServDB file
(\Program Files\OpenAFS\Client\CellServDB).
- 5. OpenAFS for Windows 1.3.65 only supports Windows 2000, Windows XP, and
- Windows 2003. Windows NT 4.0 and the entire Windows 9x/Me line are not
- supported. If OpenAFS for Windows runs on those platforms it is by sheer
- luck.
! 6. OpenAFS for Windows installs a Network Provider for use in supporting an
Integrated Logon (Single Sign-on) functionality. Integrated Logon can be used
when the Windows username and password match the username and password
associated with the default cell's Kerberos realm. For example, if the
--- 54,111 ----
is in use, the NETBIOS name associated with the AFS Client Service is simply
"AFS". When the MLA is not in use the NETBIOS name is "MACHINE-AFS".
! When the MLA is installed, UNC paths of the form \\AFS\cellname\path may be used.
!
! 3. Traditionally, when the AFS Client Service starts it must be able to
! access the "root.afs" volume of the default cell. The "root.afs" volume
! contains a set of read-only and read-write mount points to the "root.cell"
! volumes of various cells the administrator of the default cell believes
! should be accessible. If the "root.afs" volume is
! inaccessible when the client service is started, the service will panic.
! Since many users now use laptops or otherwise operate in disconnected
! environments in which a VPN may be needed to access the cell's servers, it is
! often the case that the "root.afs" volume for the default cell is not
! reachable and the AFS Client Service will not successfully start.
! The OpenAFS Client Service now supports a fake "root.afs" volume which is
! dynamically constructed when the service starts. This mode is called
! Freelance mode. Freelance mode is turned on by default.
!
! The contents of the
! fake "root.afs" volume are constructed dynamically as cells are accessed.
! When the fake "root.afs" volume is constructed it will only contain two
! mount points: a read-only and read-write mount point used to access the
! "root.cell" volume of the default AFS cell. Any attempt to access a
! valid cell name will automatically result in a new mount point
! being created in the fake "root.afs" volume. If the cellname begins with
! a "." the mount point will be read-write; otherwise the mount point will
! be read-only. These mount points are preserved in the registry at key:
! HKLM\SOFTWARE\OpenAFS\Client\Freelance
!
! Additional mount points may be manually created using the "fs mkmount"
! command. Mount points may be removed using the "fs rmmount" command.
!
! fs mkmount \\AFS\all\athena.mit.edu root.cell athena.mit.edu
! fs mkmount \\AFS\all\.athena.mit.edu root.cell athena.mit.edu -rw
! fs rmmount \\AFS\all\athena.mit.edu
! fs rmmount \\AFS\all\.athena.mit.edu
!
! 4. The OpenAFS for Windows client will use AFSDB DNS records to
discover cell information when it is not located in the local CellServDB file
(\Program Files\OpenAFS\Client\CellServDB).
! 5. OpenAFS for Windows 1.3.70 only supports Windows 2000, Windows XP, and
! Windows 2003. Windows NT 4.0 and the entire Windows 9x/Me line are no
! longer supported. Older releases of OpenAFS are available for download
! if those operating systems must be supported. The last version with support
! for Win9x is 1.2.2b. The last version with support for Windows NT 4.0 is
! 1.2.10.
!
!
! 6. OpenAFS for Windows installs a WinLogon Network Provider to provide
Integrated Logon (Single Sign-on) functionality. Integrated Logon can be used
when the Windows username and password match the username and password
associated with the default cell's Kerberos realm. For example, if the
***************
*** 109,114 ****
--- 130,146 ----
Authenticated SMB connections which removes the need for High Security mode.
DO NOT USE IT!!!!!
+ What Integrated Logon does not do:
+ (a) Integrated Logon does not have the ability to obtain Kerberos 5
+ tickets for use during the Windows Session. At the current time there
+ is no mechanism by which a Kerberos 5 CCAPI credentials cache can
+ be constructed during the logon process such that it will exist in
+ the user's logon session.
+ (b) Integrated Logon does not have the ability to cache the user's
+ username and password for the purpose of obtaining tokens if the
+ Kerberos KDC is inaccessible at logon time.
+
+
7. The AFS Systray tool (afscreds.exe) supports several new command line
options:
***************
*** 118,138 ****
-Z = unmap drives
autoinit will result in automated attempts to acquire AFS tokens when
! afscreds.exe is started. When used in combination with ip address change
! detection, afscreds.exe will attempt to acquire AFS tokens whenever a new IP
! address is added to the system.
The renew drive maps option is used to ensure that the user drive maps
! constructs via the AFS tools (not NET USE) are re-constructed at afscreds.exe
! start time.
By default afscreds.exe is configured by the OpenAFS.org installers to use -A
! -N -M as startup options. Currently, there is no UI to change this selection
! after install time although these options may be set via the registry either
! per machine or per user.
! 8. Some attempts in the 1.3.65 release have been made to restrict the behavior
! of users with regards to their ability to alter the state of the AFS Client
Service. For example, the following fs.exe commands are now restricted to
Administrator:
--- 150,174 ----
-Z = unmap drives
autoinit will result in automated attempts to acquire AFS tokens when
! afscreds.exe is started. afscreds.exe will attempt to utilize tickets stored
! in the MSLSA credentials cache; any existing CCAPI credentials cache; and
! finally display an Obtain Tokens dialog to the user. When used in combination
! with ip address change detection, afscreds.exe will attempt to acquire AFS
! tokens whenever the IP address list changes and the Kerberos KDC is
! accessible.
The renew drive maps option is used to ensure that the user drive maps
! constructed via the AFS tools (not NET USE) are re-constructed each time
! afscreds.exe is started.
By default afscreds.exe is configured by the OpenAFS.org installers to use -A
! -N -M -Q as startup options. Currently, there is no UI to change this selection
! after install time although these options may be altered via the registry either
! per machine or per user. See AfscredsShortcutParams in registry.txt.
!
! 8. Some attempts have been made to restrict the ability
! of users to alter the state of the AFS Client
Service. For example, the following fs.exe commands are now restricted to
Administrator:
***************
*** 154,163 ****
Some of the AFS Client Configuration Control Panel options are also restricted
to use by the "Administrator" account.
! 9. As of 1.3.65, the AFS Client should support UNC paths everywhere.
10. The AFS Client ships with its own version of aklog.exe which should be
! used in preference to those obtained by third party sources.
Usage: aklog [-d] [[-cell | -c] cell [-k krb_realm]]
[[-p | -path] pathname]
--- 190,206 ----
Some of the AFS Client Configuration Control Panel options are also restricted
to use by the "Administrator" account.
!
! 9. The AFS Client should support UNC paths everywhere. Power users that make
! extensive use of the command line shell, cmd.exe, might want to consider using
! JP Software's 4NT command processor. Unlike cmd.exe, 4NT does fully support
! UNC paths and can use a UNC path as the default device.
!
10. The AFS Client ships with its own version of aklog.exe which should be
! used in preference to those obtained by third party sources. The OpenAFS
! aklog.exe supports Kerberos 5 as well as the ability to auto-generate
! pts IDs for user's obtaining tokens to foreign cells.
Usage: aklog [-d] [[-cell | -c] cell [-k krb_realm]]
[[-p | -path] pathname]
***************
*** 172,203 ****
(default is Kerberos V)
No commandline arguments means authenticate to the local cell.
! 11. The AFS Server functionality provided with OpenAFS 1.3.65 does work but
! should be considered experimental. It has not been thoroughly tested.
12. The OpenAFS for Windows installers now include Symbol information which
should be installed if you are experiencing problems and need to send crash
! reports.
- 13. OpenAFS for Windows does not support files larger than 2GB.
! 14. There are known problems running the AFS Client on Hyperthreaded
! Pentium 4 machines. As of 1.3.70, a registry entry may be created to specify
that the AFS Client Service should only use a single processor. If you have
! a hyperthreaded system it is strongly advised that this registry value be set.
! See "registry.txt" for details on the MaxCPUs value.
! 15. OpenAFS for Windows currently requires the use of TCP based RPC. If the
! machine is restricted to Local RPC only, you will be unable to store tokens.
! As of 1.3.70, Local RPC is used as the default RPC mechanism for setting
! tokens. TCP RPC is still used for debugging and other functions.
! 16. As of 1.3.70, OpenAFS for Windows automatically open ports in the Windows
Internet Connection Firewall.
17. The OpenAFS for Windows installer by default activates a weak form of
encrypted data transfer between the AFS client and the AFS servers. This
! is often referred to as "crypt" mode.
18. OpenAFS 1.3.70 adds support for authenticated SMB connections using
either NTLM or GSS SPNEGO (NTLM, Kerberos 5, ...). In previous versions
--- 215,269 ----
(default is Kerberos V)
No commandline arguments means authenticate to the local cell.
!
! 11. The AFS Server functionality provided with OpenAFS 1.3.70 might work but
! should be considered highly experimental. It has not been thoroughly tested.
! Any data which would cause pain if lost should be stored in an OpenAFS
! Server on Windows.
!
! A few notes on the usage of the AFS Client Service if it is going to be
! used with the OpenAFS AFS Server:
!
! (a) When the AFS Server is installed Freelance mode must be turned off.
!
! (b) The AFS Server and related tools only support the built in kaserver
! (Kerberos IV). If the AFS Server is being used, MIT Kerberos for Windows
! should not be used.
!
12. The OpenAFS for Windows installers now include Symbol information which
should be installed if you are experiencing problems and need to send crash
! reports. This is true in both the release and the debug versions of the
! installers. The differences between the release and debug versions are
! whether or not the binaries were compiled with optimization; whether the
! debug symbols are installed by default; and whether additional debug
! statements were compiled into the binaries.
! 13. OpenAFS for Windows does not support files larger than 2GB.
!
!
! 14. There are reported problems running the AFS Client on Hyperthreaded
! Pentium 4 machines. A registry entry may be created to specify
that the AFS Client Service should only use a single processor. If you have
! a hyperthreaded system and you are experiencing crashes, it is advised that
! you create the "MaxCPUs" registry value and set it to "1".
! See "registry.txt" for details.
!
! 15. Local RPC is used as the default RPC mechanism for setting
! tokens. TCP RPC is required to be installed and is used for debugging
! and other functions.
!
! 16. OpenAFS for Windows automatically open ports in the Windows
Internet Connection Firewall.
+
17. The OpenAFS for Windows installer by default activates a weak form of
encrypted data transfer between the AFS client and the AFS servers. This
! is often referred to as "fcrypt" mode.
!
18. OpenAFS 1.3.70 adds support for authenticated SMB connections using
either NTLM or GSS SPNEGO (NTLM, Kerberos 5, ...). In previous versions
***************
*** 221,226 ****
--- 287,293 ----
add these service principals to the list of principals to be maintained
for each host.
+
19. As of 1.3.70, INI files are no longer used for the storage of AFS
configuration data. No longer are there any AFS related files stored in the
%WINDIR% directory. The CellServDB file is no longer called "afsdsbmt.ini"
***************
*** 231,236 ****
--- 298,304 ----
data will be automatically migrated; there is no mechanism for automatic
migration of Submounts, Drive Mappings, Active Maps, and CSCPolicy data.
+
20. As of 1.3.70, the OpenAFS Client is compatible with Windows XP SP2
and Windows 2003 SP1. The Internet Connection Firewall will be
automatically adjusted to allow the receipt of incoming callback messages
***************
*** 238,253 ****
entries are added to the registry to allow SMB authentication to be
performed across the loopback connection.
21. As of 1.3.70, the OpenAFS Client Service supports the CIFS Remote
Admin Protocol which provides browsing of server and share information.
! This significantly enhances the functionality of AFS volumes within the
! Explorer Shell.
22. OpenAFS will now automatically forget a user's tokens upon Logoff
unless the user's profile was loaded from an AFS volume. In this situation
there is no mechanism to determine when the profile has been successfully
written back to the network. It is therefore unsafe to release the user's
tokens.
------------------------------------------------------------------------
--- 306,346 ----
entries are added to the registry to allow SMB authentication to be
performed across the loopback connection.
+
21. As of 1.3.70, the OpenAFS Client Service supports the CIFS Remote
Admin Protocol which provides browsing of server and share information.
! This significantly enhances the interoperability of AFS volumes within the
! Explorer Shell and Microsoft Office applications.
!
! Note: This functionality has been disabled in the 1.3.70 installers due
! to problems discovered with the final release build of XP SP2. To enable
! this functionality on other versions of Windows the following registry
! entries should be added:
!
! REG_DWORD HKLM "Software\Microsoft\Windows NT\CurrentVersion\WinLogon\Notify\AfsLogon" "Asynchronous" 0
! REG_DWORD HKLM "Software\Microsoft\Windows NT\CurrentVersion\WinLogon\Notify\AfsLogon" "Impersonate" 1
! REG_SZ HKLM "Software\Microsoft\Windows NT\CurrentVersion\WinLogon\Notify\AfsLogon" "DLLName" "afslogon.dll"
! REG_SZ HKLM "Software\Microsoft\Windows NT\CurrentVersion\WinLogon\Notify\AfsLogon" "Logoff" "AFS_Logoff_Event"
! REG_SZ HKLM "Software\Microsoft\Windows NT\CurrentVersion\WinLogon\Notify\AfsLogon" "Startup" "AFS_Startup_Event"
!
22. OpenAFS will now automatically forget a user's tokens upon Logoff
unless the user's profile was loaded from an AFS volume. In this situation
there is no mechanism to determine when the profile has been successfully
written back to the network. It is therefore unsafe to release the user's
tokens.
+
+
+ 23. Terminal Server installations.
+ When installing under Terminal Server, you must execute the NSIS installer
+ (.exe) from within the Add/Remove Programs Control Panel. Failure to do so
+ will result in AFS not running properly. The AFS Server should not
+ be installed on a machine with Terminal Server installed.
+
+ 24. AFS is a Unix native file system. As such the OpenAFS client attempts
+ to treat the files stored in AFS as they would be on Unix. File and directory
+ names beginning with a "." are automatically given the Hidden attribute so
+ they will not normally be displayed.
------------------------------------------------------------------------
Index: openafs/doc/txt/winnotes/afs-issues.txt
diff -c openafs/doc/txt/winnotes/afs-issues.txt:1.5 openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.1
*** openafs/doc/txt/winnotes/afs-issues.txt:1.5 Sun Jul 25 16:53:09 2004
--- openafs/doc/txt/winnotes/afs-issues.txt Tue Aug 10 00:10:44 2004
***************
*** 139,146 ****
Currently there is no synchronization of thread creation which results in timing
conflicts; and there is no attempt to cleanly shutdown the service which causes
problems when restarting and prevents the implementation of a persistent cache
! 3. Implement a persistent cache
! 4. Prevent panic situation when the root.afs volume is not reachable
5. Prevent panic situation when the IP address to which the SMB server is bound is removed
from the local machine's network configuration
6. Identify and fix the problems with running the RX library on Hyperthreaded systems
--- 139,147 ----
Currently there is no synchronization of thread creation which results in timing
conflicts; and there is no attempt to cleanly shutdown the service which causes
problems when restarting and prevents the implementation of a persistent cache
! 3. Implement a persistent cache (requires item 2)
! 4. Prevent panic situation when the root.afs volume is not reachable and
! the AFS Client Server is not using Freelance mode
5. Prevent panic situation when the IP address to which the SMB server is bound is removed
from the local machine's network configuration
6. Identify and fix the problems with running the RX library on Hyperthreaded systems
***************
*** 187,190 ****
3. force share names to be no longer than 13 characters
4. restrict authentication to ASCII only names and passwords
19. Complete implementation of CIFS Remote Administration Protocol
! 20. Identify and correct the problems with Microsoft Office applications
--- 188,198 ----
3. force share names to be no longer than 13 characters
4. restrict authentication to ASCII only names and passwords
19. Complete implementation of CIFS Remote Administration Protocol
! 20. Correct the problems with overlapped writes which adversely affect
! Microsoft Office applications storing documents and temporary files
! within AFS volumes
! 21. Add support for SMB/CIFS Digital Signatures
! 22. Development of afsmap.exe tool to provide AFS aware NET USE functionality
! afsmap.exe