Up to 60mb required for the OpenAFS binaries plus 100MB for the default AFSCache file. (The size of the AFSCache file may be adjusted via the Registry after installation.)
!MIT Kerberos for Windows 2.6.x if Kerberos 5 authentication support is desired.
!The Kerberos 4 infrastructure on which the OpenAFS 1.2 --- 2778,2803 ---- style='mso-spacerun:yes'> The last version with support for Windows NT 4.0 is 1.2.10.
!Up to 60mb required for the OpenAFS binaries plus 100MB for the default AFSCache file. (The size of the AFSCache file may be adjusted via the Registry after installation.)
!MIT Kerberos for Windows 2.6.x if Kerberos 5 authentication support is desired.
!The Kerberos 4 infrastructure on which the OpenAFS 1.2 *************** *** 2882,2889 **** style='mso-spacerun:yes'> XE "krb524"
!By itself the OpenAFS Client Service does not provide robust --- 2881,2888 ---- style='mso-spacerun:yes'> XE "krb524"
!By itself the OpenAFS Client Service does not provide robust *************** *** 2897,2906 **** other network adapters installed on the system.
!The MLA is installed with a name of "AFS" and a pre-assigned ! IP address in the 10.x.x.x range. The ! MLA is bound to the “Client for Microsoft Networks” service and not bound to ! the “File and Printer Sharing for Microsoft Networks”. If the MLA is unbound to "Client Microsoft Networks", the OpenAFS Client Service will become inaccessible when the machine is disconnected from the network.
!The MLA is installed with a name of "AFS" and a ! pre-assigned IP address in the 10.x.x.x range. ! The MLA is bound to the “Client for Microsoft Networks” service and not ! bound to the “File and Printer Sharing for Microsoft Networks”. If the MLA is unbound to "Client Microsoft Networks", the OpenAFS Client Service will become inaccessible when the machine is disconnected from the network. One of the benefits of using the MLA is that the NETBIOS name does not have to be published on any adapter other than the MLA. Therefore the chosen name is no ! longer required to be unique. Instead the ! NETBIOS name associated with the AFS Client Service is simply "AFS" ! and portable UNC paths of the form \\AFS\cellname\path can now be used on all ! machines.
!Traditionally, when the OpenAFS Client Service starts it must ! be able to access the "root.afs" volume of the default cell. The "root.afs" volume contains the ! set of 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 terminate ! unexpectedly. Since many users now use ! laptops or otherwise operate in disconnected environments in which a VPN may be ! required 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 OpenAFS Client Service will not successfully start.
To allow the OpenAFS Client Service to operate in these ! environments, a fake "root.afs" volume is dynamically constructed from ! mount points and symlinks stored in the local registry. This method of operation is referred to as Freelance mode.
--- 2965,2990 ---- style='mso-spacerun:yes'> XE "NETBIOS" !Traditionally, when the OpenAFS Client Service starts it ! must be able to access the "root.afs" volume of the default ! cell. The "root.afs" volume ! contains the set of 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 ! terminate unexpectedly. Since many users ! now use laptops or otherwise operate in disconnected environments in which a ! VPN may be required 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 OpenAFS Client Service will not successfully start.
To allow the OpenAFS Client Service to operate in these ! environments, a fake "root.afs" volume is dynamically constructed ! from mount points and symlinks stored in the local registry. This method of operation is referred to as Freelance mode.
*************** *** 3054,3061 **** style='mso-element:field-end'> !The OpenAFS for Windows client will use DNS AFSDB records to --- 3053,3060 ---- style='mso-element:field-end'>
!The OpenAFS for Windows client will use DNS AFSDB records to *************** *** 3068,3075 **** style='mso-spacerun:yes'> XE "afsdb"
!OpenAFS for Windows installs a WinLogon Network Provider to --- 3067,3074 ---- style='mso-spacerun:yes'> XE "afsdb"
!OpenAFS for Windows installs a WinLogon Network Provider to *************** *** 3096,3103 **** into the default ccache within the user logon session.
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.
Integrated Login supports the ability to obtain tokens for multiple cells. For further information --- 3095,3102 ---- into the default ccache within the user logon session.
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.
Integrated Login supports the ability to obtain tokens for multiple cells. For further information *************** *** 3107,3114 **** style='mso-element:field-begin'> XE "integrated login"
!The AFS System Tray tool (afscreds.exe) supports several --- 3106,3113 ---- style='mso-element:field-begin'> XE "integrated login"
!The AFS System Tray tool (afscreds.exe) supports several *************** *** 3142,3161 ****
-U = uninstall startup shortcut
!-X = test and do map share
-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 OpenAFS tools (not NET USE) are re-constructed --- 3141,3160 ----
-U = uninstall startup shortcut
!-X = test ! and do map share
-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 OpenAFS tools (not NET USE) are re-constructed *************** *** 3172,3179 **** style='mso-element:field-begin'> XE "afscreds.exe"
!The OpenAFS for Windows 1.4 client supports a local Windows --- 3171,3178 ---- style='mso-element:field-begin'> XE "afscreds.exe"
!The OpenAFS for Windows 1.4 client supports a local Windows *************** *** 3277,3284 **** style='mso-spacerun:yes'> XE "fs.exe"
!The OpenAFS 1.4 client supports UNC paths everywhere. XE "fs.exe"
!The OpenAFS 1.4 client supports UNC paths everywhere. AFS paths can be entered in UNIX notation (e.g., /afs/openafs.org/software), space utilization reports the output of the volume status for the specified ! path, and many AFS specific functions and variables have been added to the command ! language.
JPSoftware's web site is http://www.jpsoft.com.
!The OpenAFS 1.4 Client ships with its own version of --- 3309,3316 ---- style='mso-spacerun:yes'> XE "4nt.exe"
!The OpenAFS 1.4 Client ships with its own version of *************** *** 3322,3332 ****
Usage: aklog [-d] [[-cell | -c] cell [-k krb_realm]]
!! [[-p | -path] pathname]
![-noprdb] [-force]
[-5 [-m]| -4]
--- 3321,3331 ----Usage: aklog [-d] [[-cell | -c] cell [-k krb_realm]]
![[-p ! | -path] pathname]
!! [-noprdb] [-force]
[-5 [-m]| -4]
*************** *** 3356,3363 **** style='mso-element:field-begin'> XE "aklog.exe" !The AFS Server functionality provided with OpenAFS 1.4 might --- 3355,3362 ---- style='mso-element:field-begin'> XE "aklog.exe"
!The AFS Server functionality provided with OpenAFS 1.4 might *************** *** 3389,3397 **** style='mso-element:field-begin'> XE "AFS Servers"
!The OpenAFS for Windows installers now include Debugging Symbol files which should be installed if you are experiencing problems and --- 3388,3396 ---- style='mso-element:field-begin'> XE "AFS Servers"
!The OpenAFS for Windows installers now include Debugging Symbol files which should be installed if you are experiencing problems and *************** *** 3423,3451 **** style='mso-element:field-begin'> XE "Symbol files"
!OpenAFS for Windows does not support files larger than 2GB. The version of the SMB/CIFS protocol implemented imposes this limitation. ! Upgrading the SMB/CIFS implementation or replacing it with an ! Installable File System will allow larger files to be supported.
!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.
!OpenAFS 1.4 supports authenticated SMB connections using --- 3422,3450 ---- style='mso-element:field-begin'> XE "Symbol files"
!OpenAFS for Windows does not support files larger than 2GB. The version of the SMB/CIFS protocol implemented imposes this limitation. ! Upgrading the SMB/CIFS implementation or replacing it with an Installable ! File System will allow larger files to be supported.
!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.
!OpenAFS 1.4 supports authenticated SMB connections using *************** *** 3456,3473 ****
When GSS SPNEGO attempts a Kerberos 5 authentication, the ! Windows SMB client will attempt to retrieve service tickets for "cifs/afs@REALM" ! (if the loopback adapter is in use) or "cifs/machine-afs@REALM" (if ! the loopback adapter is not being used). ! It is extremely important that this service principal not exist in the ! KDC database as the Kerberos authentication must fail allowing automatic ! fallback to NTLM. When NTLM is used a ! special local authentication mode will be used that does not require access to ! the user's password. Instead, Windows ! will internally recognize the request as coming from a local logon session.
!Previous AFS clients for Windows stored configuration data --- 3455,3473 ----
When GSS SPNEGO attempts a Kerberos 5 authentication, the ! Windows SMB client will attempt to retrieve service tickets for ! "cifs/afs@REALM" (if the loopback adapter is in use) or ! "cifs/machine-afs@REALM" (if the loopback adapter is not being ! used). It is extremely important that ! this service principal not exist in the KDC database as the Kerberos ! authentication must fail allowing automatic fallback to NTLM. When NTLM is used a special local ! authentication mode will be used that does not require access to the user's ! password. Instead, Windows will ! internally recognize the request as coming from a local logon session.
!Previous AFS clients for Windows stored configuration data *************** *** 3487,3494 **** Windows registry. OpenAFS 1.4 will not process the contents of the “afsddbmt.ini”.
!The OpenAFS 1.4 Client is compatible with the Internet --- 3487,3494 ---- Windows registry. OpenAFS 1.4 will not process the contents of the “afsddbmt.ini”.
!The OpenAFS 1.4 Client is compatible with the Internet *************** *** 3499,3507 **** appropriate Back Connection registry entries are added to allow SMB authentication to be performed across the Microsoft Loopback Adapter.
!The OpenAFS 1.4 Client Service implements the CIFS Remote Admin Protocol which allows Explorer to browse server and share information. --- 3499,3507 ---- appropriate Back Connection registry entries are added to allow SMB authentication to be performed across the Microsoft Loopback Adapter.
!The OpenAFS 1.4 Client Service implements the CIFS Remote Admin Protocol which allows Explorer to browse server and share information. *************** *** 3525,3550 **** that files not be edited within AFS if they might be accessed by multiple users or multiple processes on a single machine.
!OpenAFS 1.4 will 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. Whether or ! not the profile has been loaded from the registry can be determined for Local ! Accounts, Active Directory accounts and NT4 accounts.
If there is a need to disable this functionality, the LogoffPreserveTokens registry value can be used. (see Appendix A.)
!When installing the NSIS (.exe) installer under Terminal --- 3525,3550 ---- that files not be edited within AFS if they might be accessed by multiple users or multiple processes on a single machine.
!OpenAFS 1.4 will 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. Whether or not the profile has ! been loaded from the registry can be determined for Local Accounts, Active ! Directory accounts and NT4 accounts.
If there is a need to disable this functionality, the LogoffPreserveTokens registry value can be used. (see Appendix A.)
!When installing the NSIS (.exe) installer under Terminal *************** *** 3553,3560 **** AFS not running properly. The AFS Server should not be installed on a machine with Terminal Server installed.
!AFS is a UNIX native file system. The AFS Server should not be installed on a machine with Terminal Server installed.
!AFS is a UNIX native file system.
! The Status Cache (AFS Configuration Control Panel: Advanced
--- 3564,3571 ----
automatically given the Hidden attribute so they will not normally be
displayed. The Status Cache (AFS Configuration Control Panel: Advanced
***************
*** 3584,3591 ****
3.22. Status
Cache Limits
3.22. Status
Cache Limits
"Netbios over TCP/IP" must be active on the --- 3584,3591 ---- Each entry requires approximately 1.2K. In OpenAFS 1.4, the default number of Status Cache entries is 10,000.
!"Netbios over TCP/IP" must be active on the *************** *** 3594,3601 **** on the machine, then communication with the AFS Client Service will be impossible.
!The OpenAFS Client Service and related binaries distributed --- 3594,3601 ---- on the machine, then communication with the AFS Client Service will be impossible.
!The OpenAFS Client Service and related binaries distributed *************** *** 3615,3622 **** registry value which can be used to disable the signature check. The file version check cannot be disabled.
!The maximum cache size is approximately 1.3GB. The file version check cannot be disabled.
!The maximum cache size is approximately 1.3GB.
! OpenAFS for Windows implements an SMB server which is used
--- 3627,3634 ----
signature verification code, any attempt to specify a cache size greater then
700MB will result in the automatic disabling of the signature check. OpenAFS for Windows implements an SMB server which is used
***************
*** 3826,3833 ****
OpenAFS for Windows from being able to access filenames containing the above
characters which were created without this setting. There is a known issue with storing Windows Roaming Profiles
--- 3826,3833 ----
OpenAFS for Windows from being able to access filenames containing the above
characters which were created without this setting. There is a known issue with storing Windows Roaming Profiles
***************
*** 3839,3846 ****
some sites run logoff scripts (assigned by group policy) which rename all files
to use only the supported characters for the locale. The AFS Cache file is stored by default at %TEMP%\AFSCache
--- 3839,3846 ----
some sites run logoff scripts (assigned by group policy) which rename all files
to use only the supported characters for the locale. The AFS Cache file is stored by default at %TEMP%\AFSCache
***************
*** 3858,3865 ****
style='mso-spacerun:yes'> 3.26. Filename
Character Sets
3.26. Filename
Character Sets
3.27. Known
Character Set Issues with Roaming Profiles
3.27. Known
Character Set Issues with Roaming Profiles
3.28. The
AFSCache File
3.28. The
AFSCache File
A new command line tool, afsdacl.exe, can be used to --- 3858,3865 ---- style='mso-spacerun:yes'> Significant performance gains can be achieved by defragmenting the AFSCache file with Sysinternal's Contig utility.
!A new command line tool, afsdacl.exe, can be used to *************** *** 3885,3892 ****
-show : Show current DACL (SDSF)
!The default @sys name list in OpenAFS 1.4 is set to --- 3885,3892 ----
-show : Show current DACL (SDSF)
!The default @sys name list in OpenAFS 1.4 is set to *************** *** 3895,3902 **** "ia64_win64" and "amd64_win64" for amd 64-bit processors when those platforms are supported.
!In OpenAFS 1.4, symlinks to AFS UNC paths, \\AFS[\all]\..., --- 3895,3902 ---- "ia64_win64" and "amd64_win64" for amd 64-bit processors when those platforms are supported.
!In OpenAFS 1.4, symlinks to AFS UNC paths, \\AFS[\all]\..., *************** *** 3904,3911 **** However, please use /afs/... as the Windows UNC form will not work on UNIX.
!OpenAFS for Windows 1.4 implements the Cache Manager --- 3904,3911 ---- However, please use /afs/... as the Windows UNC form will not work on UNIX.
!OpenAFS for Windows 1.4 implements the Cache Manager *************** *** 3928,3935 **** -cache print only cache configuration
!If you are a site which utilizes MIT/Heimdal Kerberos --- 3928,3935 ---- -cache print only cache configuration
!If you are a site which utilizes MIT/Heimdal Kerberos *************** *** 3937,3944 **** multi-domain Windows forest, you must enable Windows logon caching unless the workstation is Windows Vista Beta 1 or later.
!VLDB and File Server Preferences can now be provided initial --- 3937,3944 ---- multi-domain Windows forest, you must enable Windows logon caching unless the workstation is Windows Vista Beta 1 or later.
!VLDB and File Server Preferences can now be provided initial *************** *** 3948,3955 **** href="#_Appendix_A:_Registry_Values">Appendix A for details on the "Server Preferences" keys.
!OpenAFS 1.4 reports timestamps on files stored in AFS in UTC --- 3948,3955 ---- href="#_Appendix_A:_Registry_Values">Appendix A for details on the "Server Preferences" keys.
!OpenAFS 1.4 reports timestamps on files stored in AFS in UTC *************** *** 3974,3981 **** During DST, these two times will no longer agree even though they are in fact representing the same moment in time.
!If the installer refuses to install and complains about an --- 3974,3981 ---- During DST, these two times will no longer agree even though they are in fact representing the same moment in time.
!If the installer refuses to install and complains about an *************** *** 3994,4001 ****
HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncacn_http"
!OpenAFS 1.4 adds a new command, "fs --- 3994,4001 ----
HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncacn_http"
!OpenAFS 1.4 adds a new command, "fs *************** *** 4005,4012 **** can be very helpful when debugging the AFS Client Service when it is unresponsive to SMB/CIFS requests.
!The OpenAFS for Windows 1.4 client implements Universally --- 4005,4012 ---- can be very helpful when debugging the AFS Client Service when it is unresponsive to SMB/CIFS requests.
!The OpenAFS for Windows 1.4 client implements Universally *************** *** 4020,4028 **** client installed, the AFSCache files must be deleted as part of the cloning process.
!OpenAFS for Windows provides a wide range of tools to assist --- 4020,4028 ---- client installed, the AFSCache files must be deleted as part of the cloning process.
!OpenAFS for Windows provides a wide range of tools to assist *************** *** 4030,4041 **** techniques available to you are varied because of the wide range of issues that have been discovered over the years.
!pioctl (path-based ioctl) calls are used by various tools to --- 4030,4041 ---- techniques available to you are varied because of the wide range of issues that have been discovered over the years.
!pioctl (path-based ioctl) calls are used by various tools to *************** *** 4124,4131 **** KnowledgeBase can be used as a reference to help you determine the configuration probem with your system.
!Every time the AFS Client Service starts it appends data --- 4124,4131 ---- KnowledgeBase can be used as a reference to help you determine the configuration probem with your system.
!Every time the AFS Client Service starts it appends data *************** *** 4145,4155 **** maximum size of the %WINDIR%\TEMP\afsd_init.log file. If the file is larger than this value when OpenAFS Client Service starts, the file will be reset to 0 bytes. If value is set to 0, the file will be ! allowed to grow indefinitely.
!When attempting to debug the behavior of the SMB/CIFS Server --- 4145,4155 ---- maximum size of the %WINDIR%\TEMP\afsd_init.log file. If the file is larger than this value when OpenAFS Client Service starts, the file will be reset to 0 bytes. If value is set to 0, the file will be allowed ! to grow indefinitely.
!When attempting to debug the behavior of the SMB/CIFS Server *************** *** 4160,4167 **** any one time is 5000. This can be adjusted with the registry value:
!! [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
REG_DWORD TraceBufferSize
--- 4160,4167 ---- any one time is 5000. This can be adjusted with the registry value: ![HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
REG_DWORD TraceBufferSize
*************** *** 4171,4178 **** to clear to the log and "fs trace -dump" to output the contents of the log to the file. !An alternatve option to the use of "fs trace --- 4171,4178 ---- to clear to the log and "fs trace -dump" to output the contents of the log to the file.
!An alternatve option to the use of "fs trace *************** *** 4181,4190 **** style='mso-spacerun:yes'> When the OpenAFS Client Service starts and Bit 2 of the TraceOption value in the registry is set, all trace log events are output using the Windows Debug ! Monitor interface (OutputDebugString).
!! [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
REG_DWORD TraceOption = 0x04
--- 4181,4189 ---- style='mso-spacerun:yes'> When the OpenAFS Client Service starts and Bit 2 of the TraceOption value in the registry is set, all trace log events are output using the Windows Debug ! Monitor interface (OutputDebugString). ![HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]
REG_DWORD TraceOption = 0x04
*************** *** 4204,4211 **** style='mso-spacerun:yes'> The captured data can be stored to files for inclusion in bug reports. !If you are having trouble with the Integrated Logon --- 4215,4222 ---- of a MiniDump file containing the state of all of the threads in the AFS Client Service process.
!If you are having trouble with the Integrated Logon *************** *** 4235,4242 **** Event Handlers to log information to the Windows Event Log: Application under the name “AFS Logon".
!The rxdebug.exe tool can be used to query a variety of --- 4234,4241 ---- Event Handlers to log information to the Windows Event Log: Application under the name “AFS Logon".
!The rxdebug.exe tool can be used to query a variety of *************** *** 4294,4301 ****
-peers show peers
!The cmdebug.exe tool can be used to query the state of the --- 4293,4300 ----
-peers show peers
!The cmdebug.exe tool can be used to query the state of the *************** *** 4327,4334 **** -cache print only cache configuration
!The persistent cache is stored in a Hidden System file at --- 4326,4333 ---- -cache print only cache configuration
!The persistent cache is stored in a Hidden System file at *************** *** 4339,4347 ****
afsd_service.exe --validate-cache <cache-path>
!Bug reports should be sent to openafs-bugs@openafs.org. afsd_service.exe --validate-cache <cache-path>
!Bug reports should be sent to openafs-bugs@openafs.org.When reporting a error, please be sure to include the version of OpenAFS.
!Contributions to the development of OpenAFS for Windows are --- 4449,4457 ----
When reporting a error, please be sure to include the version of OpenAFS.
!Contributions to the development of OpenAFS for Windows are *************** *** 4460,4467 **** take many forms including cash donations, support contracts, donated developer time, and even donated tech writer time.
!USENIX, a 501c3 --- 4459,4466 ---- take many forms including cash donations, support contracts, donated developer time, and even donated tech writer time.
!USENIX, a 501c3 *************** *** 4583,4590 ****
A MSI installer option is available for those who wish to use Windows Installer for installing OpenAFS and for organizations that wish to --- 4582,4589 ----
A MSI installer option is available for those who wish to use Windows Installer for installing OpenAFS and for organizations that wish to *************** *** 4688,4695 **** style='mso-list:Ignore'>2. msitran -a openafs-transform.mst openafs-test.msi
!and then checking the resulting openafs-test.msi to see if all ! changes you have made above to openafs-modified.msi is present in openafs-test.msi. 'msitran' will complain if some modification in the transform can not be successfully applied.
--- 4687,4694 ---- style='mso-list:Ignore'>2. msitran -a openafs-transform.mst openafs-test.msi !and then checking the resulting openafs-test.msi to see if ! all changes you have made above to openafs-modified.msi is present in openafs-test.msi. 'msitran' will complain if some modification in the transform can not be successfully applied.
*************** *** 4697,4704 **** the MSI databases directly when editing openafs-modified.msi. More details are given below. !The logic necessary to implement many of the settings --- 4696,4703 ---- the MSI databases directly when editing openafs-modified.msi. More details are given below.
!The logic necessary to implement many of the settings *************** *** 4993,5000 **** style='mso-spacerun:yes'> : '1' or '0'
Controls whether AFSCreds.exe starts up automatically when the user logs on. ! When CREDSSTARTUP is '1' a shortcut is added to the 'Startup' folder ! in the 'Program menu' which starts AFSCREDS.EXE with the options that are determined by the other CREDS* properties.
--- 4992,4999 ---- style='mso-spacerun:yes'> : '1' or '0'Controls whether AFSCreds.exe starts up automatically when the user logs on. ! When CREDSSTARTUP is '1' a shortcut is added to the 'Startup' folder in ! the 'Program menu' which starts AFSCREDS.EXE with the options that are determined by the other CREDS* properties.
*************** *** 5220,5236 **** !Note that the ComponentId is an ! uppercase GUID. You can generate one ! using GUIDGEN.EXE or UUIDGEN.EXE, both of which are included in the Platform ! SDK.
The Attributes value of 144 is a ! sum of msidbComponentAttributesPermanent (16) and msidbComponentAttributesNeverOverwrite ! (128). This ensures that local ! modifications are not overwritten or lost during an installation or ! uninstallation. These are the same ! settings used on the default configuration files.
'fil_my_CellServDB' is a key into the 'File' table which we will fill later.
--- 5219,5234 ---- !Note that the ComponentId is an uppercase ! GUID. You can generate one using ! GUIDGEN.EXE or UUIDGEN.EXE, both of which are included in the Platform SDK.
The Attributes value of 144 is a ! sum of msidbComponentAttributesPermanent (16) and ! msidbComponentAttributesNeverOverwrite (128). ! This ensures that local modifications are not overwritten or lost during ! an installation or uninstallation. These ! are the same settings used on the default configuration files.
'fil_my_CellServDB' is a key into the 'File' table which we will fill later.
*************** *** 5362,5369 ****It is important to create the ! new feature under the 'feaClient' feature, which will ensure that the configuration ! file will be installed when the client binaries are installed.
Setting 'Display' to 0 will hide this feature from the feature selection dialog during an interactive --- 5360,5367 ----
It is important to create the ! new feature under the 'feaClient' feature, which will ensure that the ! configuration file will be installed when the client binaries are installed.
Setting 'Display' to 0 will hide this feature from the feature selection dialog during an interactive *************** *** 5526,5536 ****
(leave other fields blank)
!The 'Attributes' value is msidbFileAttributesNonCompressed ! (8192). This is because we will be ! placing this file in the same directory as the MSI instead of embedding the ! file in it. Transforms do not support ! updating compressed sources or adding new cabinet streams.
Finally, the 'Sequence' value of 1000 will be used later to distinguish the file as being in a separate source --- 5524,5535 ----
(leave other fields blank)
!The 'Attributes' value is ! msidbFileAttributesNonCompressed (8192). ! This is because we will be placing this file in the same directory as ! the MSI instead of embedding the file in it. ! Transforms do not support updating compressed sources or adding new ! cabinet streams.
Finally, the 'Sequence' value of 1000 will be used later to distinguish the file as being in a separate source *************** *** 5609,5616 ****
Columns that are unspecified should be left empty.
!We create a new ! feature and component to hold the new registry keys.
|
! 'Component' table: |
|
! 'Component' ! table: |
|
! 'Registry' ! table: |
|
! 'Registry' table: |
|
! amd64_w2k ! |
!
! {CC59770C-4690-4531-BAEB-55A5A6D2EEB9} ! |
!
|
! i386_w2k ! |
!
! {B2220B3E-B61D-4CC7-9D4B-17BA918D049C} ! |
!
|
! amd64_w2k ! |
!
! {A0A7B986-CF35-499C-9400-9A987F218127} ! |
!
|
! i386_w2k ! |
!
! {E832F832-C937-46BC-8C1D-BC7EF6F3F62F} ! |
!
Each build of the installation package will have a randomly ! assigned Product Code assigned to it. As ! each release of OpenAFS is shipped using a unique file name the Product IDs ! must be unique as well.
The service parameters primarily affect the behavior of --- 6126,6133 ---- style='mso-bookmark:_Toc115417116'>Appendix A: Registry Values !
The service parameters primarily affect the behavior of *************** *** 6302,6309 **** Variable: cm_mountRoot
Name of root mount point. In symlinks, if a path starts with ! cm_mountRoot, it is assumed that the path is absolute (as opposed to ! relative) and is adjusted accordingly. Eg: if a path is specified as /afs/athena.mit.edu/foo/bar/baz and cm_mountRoot is "/afs", then the path is interpreted as \\afs\all\athena.mit.edu\foo\bar\baz. If a path does not start with with --- 6244,6251 ---- Variable: cm_mountRoot
Name of root mount point. In symlinks, if a path starts with ! cm_mountRoot, it is assumed that the path is absolute (as opposed to relative) ! and is adjusted accordingly. Eg: if a path is specified as /afs/athena.mit.edu/foo/bar/baz and cm_mountRoot is "/afs", then the path is interpreted as \\afs\all\athena.mit.edu\foo\bar\baz. If a path does not start with with *************** *** 6650,6659 ****
Type: DWORD {0 .. MAXDWORD}
Default: 100K
This entry determines the maximum size of the ! %WINDIR%\TEMP\afsd_init.log file. If ! the file is larger than this value when afsd_service.exe starts the file will ! be reset to 0 bytes. If this value is ! 0, it means the file should be allowed to grow indefinitely.
Type: DWORD {0 .. MAXDWORD}
Default: 100K
This entry determines the maximum size of the ! %WINDIR%\TEMP\afsd_init.log file. If the ! file is larger than this value when afsd_service.exe starts the file will be ! reset to 0 bytes. If this value is 0, ! it means the file should be allowed to grow indefinitely.
This value will enable the gathering of RX Statistics for connections with the Cache Manager’s Peers. This functionality can be adjusted at ! runtime with the “fs rxstatpeer” command.
Type: REG_DWORD
! Default: 0x0
This value will enable the gathering of RX Statistics
! for the Cache Manager’s Process. This
! functionality can be adjusted at runtime with the “fs rxstatproc” command.
This value will enable the gathering of RX Statistics for connections with the Cache Manager’s Peers. This functionality can be adjusted at runtime ! with the “fs rxstatpeer” command.
Type: REG_DWORD
! Default: 0x0
This value will enable the gathering of RX Statistics ! for the Cache Manager’s Process. This functionality ! can be adjusted at runtime with the “fs rxstatproc” command.
Type: REG_SZ
Default: <not defined>
Specifies the directory containing ! the CellServDB file. When this value ! is not specified, the AFS Client install directory is used.
Type: REG_SZ
Default: <not defined>
Specifies the directory ! containing the CellServDB file. When ! this value is not specified, the AFS Client install directory is used.
Type: REG_DWORD
Default: 0x0
This value can be used to force the AFS Client Service ! to store filenames using the Windows system's ANSI character set instead of the ! OEM Code Page character set which has traditionally been used by SMB file systems.
Note: The use of ANSI characters will render access to
files with 8-bit OEM file names unaccessible from Windows.Type: REG_DWORD
Default: 0x0
This value can be used to force the AFS Client Service ! to store filenames using the Windows system's ANSI character set instead of ! the OEM Code Page character set which has traditionally been used by SMB file systems.
Note: The use of ANSI characters will render access to
files with 8-bit OEM file names unaccessible from Windows.
Type: REG_DWORD This key is used to specify a default
! set of File server preferences. For each entry the value name will be either
! the IP address of a server or a fully qualified domain name. The value will be the ranking. The ranking will be adjusted by a random
value between 0 and 256 prior to the preference being set. Type: REG_DWORD This key is used to specify a
! default set of File server preferences. For each entry the value name will be
! either the IP address of a server or a fully qualified domain name. The value will be the ranking. The ranking will be adjusted by a random
value between 0 and 256 prior to the preference being set.
Default: <none>
Default: <none>
Affects the network provider (afslogon.dll).
--- 6917,6924 ---- !Affects the network provider (afslogon.dll).
*************** *** 7156,7170 **** LogonOptionsType: DWORD
Default: 0x01
NSIS/WiX: depends on user configuration
0x00 - Integrated Logon is not
used
0x01 - Integrated Logon is used
0x02 - High Security Mode is used (deprecated)
0x03 - Integrated Logon with High Security Mode is used (deprecated)
High Security Mode generates random ! SMB names for the creation of Drive Mappings. ! This mode should not be used without Integrated Logon.
As of 1.3.65 the SMB server supports SMB authentication. The High Security Mode should not be used when using SMB authentication (SMBAuthType --- 7098,7114 ---- LogonOptions
Type: DWORD
Default: 0x01
NSIS/WiX: depends on user ! configuration
0x00 - Integrated Logon is not
used
0x01 - Integrated Logon is used
0x02 - High Security Mode is used (deprecated)
0x03 - Integrated Logon with High Security Mode is used (deprecated)
High Security Mode generates ! random SMB names for the creation of Drive Mappings. This mode should not be used without ! Integrated Logon.
As of 1.3.65 the SMB server supports SMB authentication. The High Security Mode should not be used when using SMB authentication (SMBAuthType *************** *** 7249,7255 **** l15 level1 lfo36;tab-stops:list 36.0pt'>1. ! NP key. ("HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider")
1. ! NP key. ! ("HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider")
Please be aware of this when setting this value.
!Affects the behavior of afscreds.exe
--- 7247,7254 ---- security setting. Please be aware of this when setting this value. !Affects the behavior of afscreds.exe
*************** *** 7333,7340 ****Type: REG_SZ
Default: <none>
Variable: IsServiceConfigured()
The value Cell is used to determine if the AFS Client ! Service has been properly configured or not.
--- 7278,7285 ----Type: REG_SZ
Default: <none>
Variable: IsServiceConfigured()
The value Cell is used to determine if the AFS Client Service ! has been properly configured or not.
*************** *** 7353,7360 ****Type: DWORD {0, 1}
Default: 1
Function: InitApp(), Main_OnCheckTerminate()
This value is used to determine ! whether or not a shortcut should be maintained in the user's Start Menu->Programs->Startup folder.
This value used to be stored at [HKLM\Software\TransarcCorporation\AFS Client\AfsCreds].
--- 7298,7305 ----Type: DWORD {0, 1}
Default: 1
Function: InitApp(), Main_OnCheckTerminate()
This value is used to determine whether ! or not a shortcut should be maintained in the user's Start Menu->Programs->Startup folder.
This value used to be stored at [HKLM\Software\TransarcCorporation\AFS Client\AfsCreds].
*************** *** 7401,7408 ****Type: REG_SZ
Default: "-A -M -N -Q"
Function: Shortcut_FixStartup
This value specifies the command line options which ! should be set as part of the shortcut to afscreds.exe. afscreds.exe rewrites the shortcut each time it exits so as to ensure that the shortcut points to the latest version of the program. This value is used to --- 7346,7353 ----
Type: REG_SZ
Default: "-A -M -N -Q"
Function: Shortcut_FixStartup
This value specifies the command line options which should ! be set as part of the shortcut to afscreds.exe. afscreds.exe rewrites the shortcut each time it exits so as to ensure that the shortcut points to the latest version of the program. This value is used to *************** *** 7459,7467 ****
Type: DWORD {0, 1}
Default: <none>
Function: LoadRemind(), SaveRemind()
These values are used to save and ! restore the state of the reminder flag for each cell for which the user has ! obtained tokens.
This value used to be stored at [HKLM\Software\TransarcCorporation\AFS Client\AfsCreds].
--- 7404,7412 ----Type: DWORD {0, 1}
Default: <none>
Function: LoadRemind(), SaveRemind()
These values are used to save ! and restore the state of the reminder flag for each cell for which the user ! has obtained tokens.
This value used to be stored at [HKLM\Software\TransarcCorporation\AFS Client\AfsCreds].
*************** *** 7482,7489 **** drive letter"Type: DWORD {0, 1}
Default: <none>
These values are used to store ! the persistence state of the AFS drive mappings as listed in the [...\Client\Mappings] key.
These values used to be stored in the afsdsbmt.ini file
--- 7427,7434 ---- drive letter"Type: DWORD {0, 1}
Default: <none>
These values are used to store the ! persistence state of the AFS drive mappings as listed in the [...\Client\Mappings] key.
These values used to be stored in the afsdsbmt.ini file
*************** *** 7507,7520 **** Default: <none>These values are used to store the AFS path in UNIX notation to which the drive letter is to be mapped.
!These values used to be stored in ! the afsdsbmt.ini file.
!