<bookinfo>
<title>OpenAFS for Windows Release Notes</title>
<copyright>
- <year>2003-2011</year>
+ <year>2003-2012</year>
<holder>Secure Endpoints Inc. and Your File System Inc.</holder>
</copyright>
<legalnotice>
</bookinfo>
<preface>
<title id="Preface">Preface</title>
- <para>The Andrew File System (AFS) is a location-independent file system that uses a local cache to increase its performance. An AFS client accesses files anonymously or via a Kerberos authentication. The global AFS is partitioned into cells. The AFS cell is a collection of AFS volumes that are administered by a common entity. AFS cells can be administered by a department even when the Kerberos realm used for local authentication is managed by a much larger organization. AFS clients and servers take advantage of Kerberos cross realm authentication to enable authenticated access by entities located outside the local realm. Authorization is enforced by the use of directory level access control lists which can consist of individual or group identities. </para>
+ <para>The Andrew File System (AFS) is a globally-accessible location-independent file system
+ that uses local caching to increase its performance. An AFS client accesses files anonymously
+ or authenticated via Kerberos. The global AFS is partitioned into cells. Each AFS cell is a
+ collection of AFS volumes that are administered by a common entity. AFS cells can be
+ administered by a department even when the associated Kerberos authentication realms are
+ managed by a much larger organization. AFS clients and servers take advantage of Kerberos
+ cross-realm authentication to permit authenticated access by entities located outside the
+ local realm. Authorization is enforced by the use of directory level access control lists of
+ individual or group identities. </para>
<para>The AFS volume is a tree of files and sub-directories. AFS volumes are created by administrators and are joined to an AFS cell via the use of a mount point. Once a volume is created, users can create files and directories as well as mount points and symlinks within the volume without regard for the physical location of the volume. Administrators can move the volume to another server as necessary without the need to notify users. In fact, the volume move can occur while files in the volume are in use. </para>
<para>AFS volumes can be replicated to read-only copies. When accessing files from a read-only replica, clients will read all of the data from a single replica. If that replica becomes unavailable, the clients will failover to any replica that is reachable. Users of the data are unaware of where the replicas are stored or which one is being accessed. The contents of the replicas can be updated at any time by
<emphasis>releasing</emphasis> the current contents of the source volume.
</para>
- <para>OpenAFS for Windows (OAFW) provides AFS client access Microsoft Windows operating systems. It strives to maintain transparency such that the user is unaware of the distinction between the use of AFS and Microsoft Windows file shares. OAFW can be part of a single sign-on solution by allowing credentials for a Kerberos principal to be obtained at logon and for that principal to be used to obtain AFS tokens for one or more cells. OAFW is implemented as a native installable file system and maintains the portability of file paths by its use of the \\AFS UNC server name.</para>
- <para>OpenAFS is the product of an open source development effort begun on October 31 2000. OpenAFS is maintained and developed by a group of volunteers with the support of the end user community. When OpenAFS is used as part of your computing infrastructure, please <link linkend="Contributing_to_OpenAFS">contribute</link> to its continued growth.
- </para>
+ <para>OpenAFS for Windows (OAFW) provides AFS client access on Microsoft Windows operating
+ systems. It strives to maintain transparency such that the user is unaware of the distinction
+ between the use of AFS and Microsoft Windows file shares. OAFW can be part of a single sign-on
+ solution by allowing credentials for a Kerberos principal to be obtained at logon and for that
+ principal to be used to obtain AFS tokens for one or more cells. OAFW is implemented as a
+ native installable file system and maintains the portability of file paths by its use of the
+ \\AFS UNC server name.</para>
+ <para>OpenAFS is the product of an open source development effort begun on 1 November 2000.
+ OpenAFS is maintained and developed by a group of volunteers with the support of the end user
+ community. When OpenAFS is used as part of your computing infrastructure, please <link
+ linkend="Contributing_to_OpenAFS">contribute</link> to its continued growth. </para>
</preface>
<chapter id="chap_1">
<title id="Installer_Options">Installer Options</title>
<para>Microsoft Windows 7 (32-bit and 64-bit Intel)</para>
</listitem>
<listitem>
- <para>Microsoft Windows 2008 Server R2 (32-bit and 64-bit Intel)</para>
+ <para>Microsoft Windows 2008 Server R2 (64-bit Intel)</para>
</listitem>
</itemizedlist>
</para>
</para>
<para>It is important to note that AFS file servers are character-set agnostic. All file system object names are stored as octet strings without any character set tagging. If a file system object is created using OEM Code Page 858 and then interpreted as UTF-8 it is likely that the object name will appear to be gibberish. OpenAFS for Windows goes to great lengths to ensure that the object name is converted to a form that will permit the user to rename the object using Unicode. Accessing UTF-8 names on UNIX systems that have the locale set to one of the ISO Latin character sets will result in the UTF-8 strings appearing to be gibberish. </para>
<para>UNIX AFS can not perform Unicode Normalization for string comparisons. Although it is possible to store and read Unicode object names, it is possible that a user may not be able to open an object by typing the name of the object at the keyboard. GUI point and click operations should permit any object to be accessed.</para>
+ <section>
+ <title>3.1.1. Interoperability with MacOS X</title>
+ <indexterm>
+ <primary>MacOS X</primary>
+ </indexterm>
+ <para>MacOS X uses UTF-8 Normalization Form D (NFD) whereas Microsoft Windows and most other
+ applications use UTF-8 Normalization Form C (NFC). The difference is that in NFD Unicode
+ character sequences containing diacritical marks are decomposed whereas in NFC the Unicode
+ character sequences use combined characters whenever possible. Whereas Microsoft Windows
+ can display and manipulate files stored using NFD, MacOS X Finder does have trouble with
+ filenames that are NFC encoded. All file names stored by the OpenAFS Windows client use
+ NFC.</para>
+ </section>
</section>
<section id="Kerberos_v5_Requirements">
<title>3.2. Requirements for Kerberos v5 Authentication</title>
<indexterm significance="normal">
<primary>heimdal</primary>
</indexterm>
- <para>The OpenAFS distribution ships with its own implementation of Kerberos v4 and although it is Kerberos v5 capable, it relies on third-party Kerberos v5 libraries. The OpenAFS 1.4 series (and later) integrates with
- <ulink url="http://web.mit.edu/kerberos/">MIT Kerberos for Windows</ulink> 2.6.5 and above. OpenAFS Kerberos v5 capable functionality includes integrated logon, the AFS Authentication Tool, the Network Identity Manager AFS provider, and the aklog command. These tools provide support for Kerberos v5 authentication including acquisition and automatic renewal of AFS tokens as well as support for single sign-on via the Microsoft Windows Kerberos Logon Service.
- </para>
+ <para>The OpenAFS distribution ships with its own implementation of Kerberos v4 and although
+ it is Kerberos v5 capable, it relies on third-party Kerberos v5 libraries. The OpenAFS 1.4
+ series (and later) integrates with <ulink url="https://www.secure-endpoints.com/heimdal"
+ >Heimdal</ulink> or <ulink url="http://web.mit.edu/kerberos/">MIT Kerberos for
+ Windows</ulink> 2.6.5 and above. OpenAFS Kerberos v5 capable functionality includes
+ integrated logon, the AFS Authentication Tool, the Network Identity Manager AFS provider,
+ and the aklog command. These tools provide support for Kerberos v5 authentication including
+ acquisition and automatic renewal of AFS tokens as well as support for single sign-on via
+ the Microsoft Windows Kerberos Logon Service. </para>
<indexterm significance="normal">
<primary>network identity manager</primary>
</indexterm>
- <para>The recommended version of
- <ulink url="http://web.mit.edu/kerberos/">MIT Kerberos for Windows</ulink> is 3.2.2 as distributed by <ulink url="https://www.secure-endpoints.com/">Secure Endpoints Inc.</ulink>. As of this writing, the Secure Endpoints Inc. distribution provides 64-bit Windows support which is unavailable from MIT. KFW 3.2.2 includes Network Identity Manager 1.3.1 which integrates with the
- <link linkend="Network_Identity_Manager_Provider">AFS Provider</link> installed as part of OpenAFS for Windows. The most recent version of Network Identity Manager is version 2.1 which is available as an independent upgrade to MIT Kerberos for Windows.
- </para>
+ <para>The recommended versions of <ulink url="https://www.secure-endpoints.com/heimdal"
+ >Heimdal</ulink> and <ulink url="http://web.mit.edu/kerberos/">MIT Kerberos for
+ Windows</ulink> are distributed by <ulink url="https://www.secure-endpoints.com/">Secure
+ Endpoints Inc.</ulink>. As of this writing, the Secure Endpoints Inc. distribution
+ provides 64-bit Windows support which is unavailable from MIT. KFW 3.2.2 includes Network
+ Identity Manager 1.3.1 which integrates with the <link
+ linkend="Network_Identity_Manager_Provider">AFS Provider</link> installed as part of
+ OpenAFS for Windows. The most recent version of Network Identity Manager is version 2.1
+ which is available as an independent upgrade to MIT Kerberos for Windows. Heimdal does not
+ include a version of Network Identity Manager.</para>
<indexterm significance="normal">
<primary>transarc afs</primary>
</indexterm>
- <para>With Kerberos for Windows installed, the OpenAFS for Windows client can perform authentication to AFS services using Kerberos v5 service tickets as AFS tokens. When a Kerberos v5 derived AFS token is used, all of the AFS Volume Location and File Servers within the authenticated cell must support Kerberos v5. If a Kerberos v5 based token is presented to an AFS server that does not support them, the server will be unable to respond to the client. Attempts to access AFS volumes stored on such a server will fail with the Windows STATUS_NO_KERB_KEY (0xC0000322L) error. Kerberos v5 based tokens are supported by OpenAFS revisions 1.2.8 or later. IBM AFS 3.6 servers do not support Kerberos v5.</para>
+ <para>With Heimdal or Kerberos for Windows installed, the OpenAFS for Windows client can
+ perform authentication to AFS services using Kerberos v5 service tickets as AFS tokens. When
+ a Kerberos v5 derived AFS token is used, all of the AFS Volume Location and File Servers
+ within the authenticated cell must support Kerberos v5. If a Kerberos v5 based token is
+ presented to an AFS server that does not support them, the server will be unable to respond
+ to the client. Attempts to access AFS volumes stored on such a server will fail with the
+ Windows STATUS_NO_KERB_KEY (0xC0000322L) error. Kerberos v5 based tokens are supported by
+ OpenAFS revisions 1.2.8 or later. IBM AFS 3.6 servers do not support Kerberos v5.</para>
<section>
<title id="Active_Directory">3.2.1. Active Directory</title>
<indexterm significance="normal">
<indexterm significance="normal">
<primary>des-cbc-crc encryption type</primary>
</indexterm>
- <para>Microsoft Windows Active Directory can be used as a Kerberos v5 KDC in conjunction with OpenAFS.
- <itemizedlist>
+ <para>Microsoft Windows Active Directory can be used as a Kerberos v5 KDC in conjunction
+ with OpenAFS. <itemizedlist>
<listitem>
- <para>
- There are two things to consider when using an Active Directory as the Kerberos realm that issues the AFS service ticket. First, the Kerberos v5 tickets issued by Active Directory can be quite large when compared to tickets issued by traditional UNIX KDCs due to the inclusion of Windows specific authorization data <ulink url="http://msdn.microsoft.com/en-us/library/cc237917%28v=prot.10%29.aspx">(the Microsoft PAC)</ulink>. If the issued tickets are larger than 344 bytes, OpenAFS 1.2.x servers will be unable to process them and will issue a RXKADBADTICKET error. OpenAFS 1.4 (and beyond) servers can support the largest tickets that Active Directory can issue.
- </para>
- </listitem>
- <listitem>
- <para>Second, the Kerberos v5 tickets issued by Windows 2003 Active Directory are encrypted with the DES-CBC-MD5 encryption type (enctype). OpenAFS 1.2.x servers only support the DES-CBC-CRC enctype. As a result, OpenAFS 1.2.x servers cannot process the resulting Kerberos v5 tokens. Windows 2000 Active Directory issues tickets with the DES-CBC-CRC enctype. Windows Server 2008 R2 Active Directory domain by default disables use of DES-CBC-MD5 and it must be enabled.
- </para>
- <para>Microsoft has documented in
- <ulink url="http://support.microsoft.com/kb/832572/">Knowledge Base article 832572</ulink> a new NO_AUTH_REQUIRED flag that can be set on the account mapped to the AFS service principal. When this flag is set, the PAC authorization data will not be included in the ticket. Setting this flag is recommended for all accounts that are associated with non-Windows services and that do not understand the authorization data stored in the PAC. This flag cannot be used if AFS service tickets are obtained via cross-realm using an Active Directory user principal.
- </para>
- <para>Note that an Active Directory computer object cannot be used for the afs service principal. A user object must be used.</para>
- </listitem>
- </itemizedlist>
- </para>
+ <para> There are two things to consider when using an Active Directory as the Kerberos
+ realm that issues the AFS service ticket. First, the Kerberos v5 tickets issued by
+ Active Directory can be quite large when compared to tickets issued by traditional
+ UNIX KDCs due to the inclusion of Windows specific authorization data <ulink
+ url="http://msdn.microsoft.com/en-us/library/cc237917%28v=prot.10%29.aspx">(the
+ Microsoft PAC)</ulink>. If the issued tickets are larger than 344 bytes, OpenAFS
+ 1.2.x servers will be unable to process them and will issue a RXKADBADTICKET error.
+ OpenAFS 1.4 (and beyond) servers can support the largest tickets that Active
+ Directory can issue. </para>
+ </listitem>
+ <listitem>
+ <para>Second, the Kerberos v5 tickets issued by Windows 2003 Active Directory are
+ encrypted with the DES-CBC-MD5 encryption type (enctype). OpenAFS 1.2.x servers only
+ support the DES-CBC-CRC enctype. As a result, OpenAFS 1.2.x servers cannot process
+ the resulting Kerberos v5 tokens. Windows 2000 Active Directory issues tickets with
+ the DES-CBC-CRC enctype. Windows Server 2008 R2 Active Directory domain by default
+ disables use of DES-CBC-MD5 and it must be enabled. </para>
+ <para>Microsoft has documented in <ulink url="http://support.microsoft.com/kb/832572/"
+ >Knowledge Base article 832572</ulink> a new NO_AUTH_REQUIRED flag that can be set
+ on the account mapped to the AFS service principal. When this flag is set, the PAC
+ authorization data will not be included in the ticket. Setting this flag is
+ recommended for all accounts that are associated with non-Windows services and that
+ do not understand the authorization data stored in the PAC. This flag cannot be used
+ if AFS service tickets are obtained via cross-realm using an Active Directory user
+ principal. </para>
+ <para>Note that an Active Directory computer object cannot be used for the afs service
+ principal. A user object must be used.</para>
+ </listitem>
+ <listitem>
+ <para>Starting with Windows 7 and Windows Server 2008 R2, Microsoft has disabled the
+ single DES encryption types,<ulink
+ url="http://technet.microsoft.com/en-us/library/dd560670(WS.10).aspx">TechNet:
+ Changes in Kerberos Authentication</ulink>. DES must be enabled via Group Policy
+ in order for Active Directory to be used as a KDC for OpenAFS. Enable weak
+ encryption becuase of AFS... Start > Administrative Tools > Group Policy
+ Management Expand Forest > Domains > (domain name) > Group Policy Objects
+ > Default Domain Policy Right-click "Default Domain Policy" and select "Edit"
+ Expand "Computer Configuration" > "Policies" > "Windows Settings” >
+ "Security Settings” > "Local Policies” > "Security Options” Double click
+ "Network security: Configure encryption types allowed for Kerberos” Select "Define
+ this policy setting", then select "DES_CBC_CRC" and all the others... Press "OK" </para>
+ </listitem>
+ </itemizedlist></para>
</section>
<section>
<title id="Using_krb524_Service">3.2.2. The krb524 Service is no longer supported</title>
<indexterm significance="normal">
<primary>network identity manager</primary>
</indexterm>
- <para>As of release 1.5.9, OpenAFS for Windows includes a Network Identity Manager Provider for obtaining AFS tokens. This plug-in is a contribution from
- <ulink url="https://www.secure-endpoints.com/">Secure Endpoints Inc.</ulink> Network Identity Manager is a multiple identity credential management tool that ships with
- <ulink url="http://web.mit.edu/kerberos/">MIT Kerberos for Windows</ulink> version 3.0 and above. The OpenAFS plug-in requires
- <ulink url="http://web.mit.edu/kerberos/">MIT Kerberos for Windows</ulink> version 3.1 or above. Version 3.2.2 is recommended for the best user experience.
- </para>
+ <para>As of release 1.5.9, OpenAFS for Windows includes a Network Identity Manager Provider
+ for obtaining AFS tokens. This plug-in is a contribution from <ulink
+ url="https://www.secure-endpoints.com/">Secure Endpoints Inc.</ulink> Network Identity
+ Manager is a multiple identity credential management tool that ships with <ulink
+ url="http://web.mit.edu/kerberos/">MIT Kerberos for Windows</ulink> version 3.0 and
+ above. The OpenAFS plug-in requires <ulink url="https://www.secure-endpoints.com/heimdal"
+ >Heimdal</ulink> or <ulink url="http://web.mit.edu/kerberos/">MIT Kerberos for
+ Windows</ulink> version 3.1 or above. </para>
<para>
<inlinemediaobject>
<imageobject>
</listitem>
</itemizedlist>
</section>
+ <section>
+ <title>3.2.4. Heimdal 1.5 and Weak Encryption Types</title>
+ <para>Just as Microsoft disabled the use of Weak Encryption Types in Windows 7 and Windows
+ Server 2008 R2, Heimdal and MIT have disabled the use of weak encryption types in their
+ latest releases. In order to use Heimdal 1.5 or MIT Kerberos 1.9 or later with OpenAFS,
+ the weak encryption types including DES-CBC-CRC and DES-CBC-MD5 must be enabled. In
+ Heimdal, this is performed by adding "allow_weak_crypto = true" to the [libdefaults]
+ section of the %SystemRoot%\ProgramData\krb5.conf file.</para>
+ <para>Futures versions of OpenAFS will not have this requirement.</para>
+ </section>
</section>
<section>
<title id="Use_of_Microsoft_Loopback">3.3. The Former use of the Microsoft Loopback Adapter by the OpenAFS Client Service</title>
<indexterm significance="normal">
<primary>microsoft loopback adapter</primary>
</indexterm>
- <para>
- This section is preserved for those sites that may want to manually configure the OpenAFS Client Service to run as an SMB Gateway to AFS instead of using the native IFS file system redirector driver. When the IFS driver is in use the Microsoft Loopback Adapter (if installed) is ignored. The OpenAFS 1.7.x installer will not install a Microsoft Loopback Adapter by default nor will it remove one if already present on the machine.
- </para>
+ <para> This section is preserved for those sites that may want to manually configure the
+ OpenAFS Client Service to run as an SMB Gateway to AFS instead of using the native IFS file
+ system redirector driver. When the IFS driver is active, the Microsoft Loopback Adapter is
+ ignored. The OpenAFS 1.7.x installer will not install a Microsoft Loopback Adapter by
+ default nor will it remove one if already present on the machine. </para>
<para>The Microsoft Loopback Adapter (MLA) is installed with a name "AFS" and a pre-assigned IP address of 10.254.254.253. The MLA is bound to the "Client for Microsoft Networks" service and not bound to the "File and Printer Sharing for Microsoft Networks" service. If the MLA is unbound to "Client Microsoft Networks", the OpenAFS Client Service will become inaccessible when the machine is disconnected from the network. If the MLA is bound to "File and Printer Sharing ..." there will be a service type collision between the "AFS" SMB Service and the local machine's File Sharing Service. This will result in the OpenAFS client service becoming inaccessible and the "NET VIEW \\AFS" command will return a "System Error 52" message. To correct the problem:</para>
<itemizedlist>
<listitem>
<indexterm significance="normal">
<primary>symlinks</primary>
</indexterm>
- <para>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 Virtual Private Network (VPN) connection 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 can not successfully start. </para>
- <para>To allow the OpenAFS Client Service to operate in these environments, Freelance mode dynamically constructs a fake "root.afs" volume from mount points and symlinks stored in the local registry.</para>
+ <para>Historically, when the OpenAFS Client Service starts it must mount 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 starts, the
+ service will terminate unexpectedly. Since many users now use laptops or otherwise operate
+ in disconnected environments in which a Virtual Private Network (VPN) connection may be
+ required to access the cell's servers, it is often the case that the "root.afs" volume is
+ unreachable and the OpenAFS Client Service can not successfully start. </para>
+ <para>Freelance mode dynamically constructs a fake "root.afs" volume from mount points and
+ symlinks stored in the local registry. This permits the OpenAFS Client Service to operate
+ in these environments.</para>
<para>The content of the fake "root.afs" volume is dynamically generated as cells are accessed. When the fake "root.afs" volume is initially constructed it will only contain two mount points: a
<emphasis>regular path </emphasis>and
<emphasis>read-write path </emphasis>mount point used to access the "root.cell" volume of the default AFS cell. Any attempt to access a valid cell name will 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 a
<indexterm significance="normal">
<primary>afsdb dns records</primary>
</indexterm>
- <para>The OpenAFS for Windows client will use DNS SRV records and AFSDB records to discover the location of AFS Volume Database servers when entries for the cell are not present in either the client's CellServDB registry store or file (\%PROGRAMFILES%\OpenAFS\Client\CellServDB).
- Also see <link linkend="Registry_VLDB_Configuration">Registry Configuration for AFS Volume Database Servers</link>.</para>
+ <para>The OpenAFS for Windows client will use DNS SRV records and DNS AFSDB records to
+ discover the location of AFS Volume Database servers when entries for the cell are not
+ present in either the client's CellServDB registry store or file
+ (\%PROGRAMFILES%\OpenAFS\Client\CellServDB). Also see <link
+ linkend="Registry_VLDB_Configuration">Registry Configuration for AFS Volume Database
+ Servers</link>.</para>
</section>
<section>
<title id="Integrated_Logon">3.6. Obtaining AFS Tokens as a Integrated Part of Windows Logon</title>
<indexterm significance="normal">
<primary>tokens</primary>
</indexterm>
- <para>OpenAFS for Windows installs a WinLogon Network Provider to provide Single Sign-On functionality (aka Integrated Logon.) 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 Windows username is "jaltman" and the default cell is "athena.mit.edu", then Integrated Logon can be successfully used if the windows password matches the password assigned to the Kerberos principal "jaltman@ATHENA.MIT.EDU". The realm "ATHENA.MIT.EDU" is obtained by performing a domain name to realm mapping on the hostname of one of the cell's Volume Database servers.</para>
- <para>Integrated Logon is required if you desire the ability to store roaming user profiles within the AFS file system. OpenAFS does not provide tools for synchronizing the Windows and Kerberos user accounts and passwords.</para>
+ <para>OpenAFS for Windows installs a WinLogon Network Provider to provide Single Sign-On
+ functionality (aka Integrated Logon.) Integrated Logon can be used to obtain AFS tokens when
+ the Windows username and password match the username and password associated with the
+ default cell's Kerberos realm. For example, if the Windows username is "jaltman" and the
+ default cell is "your-file-system.com", then Integrated Logon can be successfully used if
+ the windows password matches the password assigned to the Kerberos principal
+ "jaltman@YOUR-FILE-SYSTEM.COM". The realm "YOUR-FILE-SYSTEM.COM" is obtained by performing a
+ domain name to realm mapping on the hostname of one of the cell's Volume Database
+ servers.</para>
+ <para>Integrated Logon is required if roaming user profiles are stored within the AFS file
+ system. OpenAFS does not provide tools for synchronizing the Windows and Kerberos user
+ accounts and passwords. Integrated Logon can be enabled or disabled via the <link
+ linkend="Value_LogonOptions">LogonOptions</link> registry value.</para>
<para>When KFW is configured, Integrated Logon will use it to obtain tokens. Use of KFW for Integrated Logon can be disabled via the
<link linkend="Value_EnableKFW">EnableKFW</link> registry value.
</para>
<indexterm significance="normal">
<primary>network identity manager</primary>
</indexterm>
- <para>The AFS Authentication Tool (afscreds.exe) has been deprecated in favor of Network Identity Manager. afscreds.exe is no longer installed by default in the OpenAFS 1.7 release series. The following information is for historical reference.</para>
+ <para><emphasis role="italic">The AFS Authentication Tool (afscreds.exe) has been deprecated
+ in favor of Network Identity Manager. afscreds.exe is no longer installed by default in
+ the OpenAFS 1.7 release series. The following information is for historical
+ reference.</emphasis></para>
<para>The AFS Authentication Tool (afscreds.exe) supports several command line options: </para>
<itemizedlist>
<listitem>
<indexterm significance="normal">
<primary>64-bit file sizes</primary>
</indexterm>
- <para>As of release 1.5.3, OpenAFS for Windows supports files larger than 2GB. The maximum file size is now 16777216 terabytes when the AFS File Server supports large files. If the AFS File Server does not support 64-bit file sizes, then the maximum size of files stored on that server remains 2GB.</para>
+ <para>As of release 1.5.3, OpenAFS for Windows supports files larger than 2GB. The maximum
+ file size is now 16777216 terabytes when the AFS File Server supports large files. If the
+ AFS File Server does not support 64-bit file sizes, then the maximum size of files stored on
+ that server remains 2GB. </para>
</section>
<section>
<title id="Encrypted_AFS_Network_Communication">3.14. Encrypted AFS Network Communication</title>
<indexterm significance="normal">
<primary>Back Connection</primary>
</indexterm>
- <para>The OpenAFS Client is compatible with the Internet Connection Firewall that debuted with Windows XP SP2 and Windows 2003 SP1. The Internet Connection Firewall will be automatically configured to allow the receipt of incoming callback messages from the AFS file server. In addition, if the OpenAFS Service is manually configured to behave as an SMB Gateway, the appropriate
- <emphasis>Back Connection</emphasis> registry entries are added to allow SMB authentication to be performed across the Microsoft Loopback Adapter.
- </para>
- <para>
- On Windows Vista, Windows 7 and Server 2008 the OpenAFS Service can only modify the local machine firewall policy. The domain firewall policy must be manually configured by the Domain Administrator.
- </para>
+ <para>The OpenAFS Client is compatible with the Internet Connection Firewall that debuted with
+ Windows XP SP2 and Windows 2003 SP1 and the Advanced Firewall that was introduced with
+ Windows Vista. The Internet Connection Firewall will be automatically configured to allow
+ the receipt of incoming callback messages from the AFS file server. In addition, if the
+ OpenAFS Service is manually configured to behave as an SMB Gateway, the appropriate
+ <emphasis>Back Connection</emphasis> registry entries are added to allow SMB
+ authentication to be performed across the Microsoft Loopback Adapter. </para>
</section>
<section>
<title id="Browsing_AFS_from_Explorer_Shell">3.18. Browsing AFS from the Explorer Shell and Office</title>
<indexterm significance="normal">
<primary>Installation</primary>
</indexterm>
- <para>The OpenAFS Servers should not be installed on a machine with Terminal Server installed.</para>
+ <para>The OpenAFS Servers should not be installed on a machine with Terminal Server installed.
+ The OpenAFS Client is fully compatible with Terminal Services.</para>
</section>
<section>
<title id="Hidden_Dot_Files">3.22. Hidden Dot Files</title>
<indexterm significance="normal">
<primary>NETBIOS over TCP</primary>
</indexterm>
+ <para><emphasis role="italic">This section only applies when the IFS client mode is
+ disabled.</emphasis></para>
<para>"Netbios over TCP/IP" must be active on the machine in order for communication with the AFS Client Service to succeed. If "Netbios over TCP/IP" is disabled on the machine, then communication with the AFS Client Service will be impossible. If you are using the Microsoft Loopback Adapter, configure the "Netbios over TCP/IP" setting for the adapter.</para>
</section>
<section>
<primary>SysName</primary>
</indexterm>
<para>The default @sys name list in the OpenAFS Client is set to "x86_win32 i386_w2k i386_nt40" for 32-bit x86 systems. The default is "amd64_win64" for amd 64-bit versions of Windows.</para>
- <para>The IFS redirector driver is aware of the process type. On 64-bit systems, there are two @sys name lists "SysName" which is used for the WOW64 environment and "SysName64" which is used for the 64-bit environment.</para>
+ <para>The IFS redirector driver is aware of the process type. On 64-bit systems, there are two
+ @sys name lists "SysName" which is used for the WOW64 environment and "SysName64" which is
+ used for the 64-bit environment. If "SysName64" is not provided, "SysName" is used for all
+ processes.</para>
</section>
<section>
<title id="Symlinks_to_AFS_UNC_Paths">3.32. Symlinks to AFS UNC Paths</title>
<para>For lab environments that wish to erase all cached data on each restart, the
<link linkend="Value_NonPersistentCaching">NonPersistentCaching</link> option will disable the use of the persistent cache file. As a side effect, a new UUID will be generated for the AFS client service on each restart.
</para>
- <para>When a Windows system is cloned, the Microsoft Loopback Adapter will be disabled in the cloned system. Administrators must re-install the Microsoft Loopback Adapter within the cloned environment. This can be automated by using the OpenAFS "
- <emphasis>instloop.exe</emphasis> –
- <emphasis>i</emphasis>" command. Instloop.exe can be extracted from the MSI installer by performing an administrative install via
- <emphasis>msiexec.exe /a</emphasis>.
- </para>
+ <para><emphasis role="italic">[SMB only]</emphasis> When a Windows system is cloned, the
+ Microsoft Loopback Adapter will be disabled in the cloned system. Administrators must
+ re-install the Microsoft Loopback Adapter within the cloned environment. This can be
+ automated by using the OpenAFS " <emphasis>instloop.exe</emphasis> – <emphasis>i</emphasis>"
+ command. Instloop.exe can be extracted from the MSI installer by performing an
+ administrative install via <emphasis>msiexec.exe /a</emphasis>. </para>
</section>
<section>
<title id="Delayed_Write_Errors">3.40. Delayed Write Errors with Microsoft Office Applications</title>
<indexterm significance="normal">
<primary>path ioctl failures</primary>
</indexterm>
- <para>The Global DriveAuto-mount feature has been deprecated due to the following Microsoft KB article.</para>
+ <para>The Global Drive auto-mount feature has been deprecated due to the following Microsoft
+ KB article.</para>
<para>
<ulink url="http://msdn.microsoft.com/library/en-us/dllproc/base/services_and_redirected_drives.asp">http://msdn.microsoft.com/library/en-us/dllproc/base/services_and_redirected_drives.asp</ulink>
</para>
<para>Windows Vista, Windows 7, and Server 2008 [R2] implement
<ulink url="http://www.microsoft.com/technet/windowsvista/library/0d75f774-8514-4c9e-ac08-4c21f5c6c2d9.mspx">User Account Control</ulink> (UAC), a new security feature that implements least user privilege. With UAC, applications only run with the minimum required privileges. Even Administrator accounts run applications without the "Administrator" access control credentials. One side effect of this is that existing applications that mix user and system configuration capabilities must be re-written to separate those functions that require "Administrator" privileges into a separate process space. Future updates to OpenAFS will incorporate the necessary privilege separation, until that time some functions such as the Start and Stop Service features of the AFS Authentication Tool and the AFS Control Panel will not work unless they are "Run as Administrator". When a Vista user account that is a member of the "Administrators" group is used to access the AFS Control Panel (afs_config.exe), the process must be "Run as Administrator". Otherwise, attempts to modify the OpenAFS configuration will appear to succeed but in reality will have failed due to Vista's system file and registry virtualization feature.
</para>
- <para>The help files provided with OpenAFS are in .HLP format.
- <ulink url="http://support.microsoft.com/kb/917607">Windows Vista, Windows 7, and Server 2008 [R2] do not include a help engine for this format.</ulink>
+ <para>The help files provided with OpenAFS are in .HLP format. <ulink
+ url="http://support.microsoft.com/kb/917607">Windows Vista, Windows 7, and Server 2008
+ [R2] do not include a help engine for this format.</ulink>
</para>
<para><emphasis>The following items only apply when the OpenAFS Service is manually configured as an SMB Gateway.</emphasis></para>
<para>OpenAFS for Windows works with Microsoft Windows Vista, Windows 7 and Server 2008 [R2] from both the command prompt and the Explorer Shell.
</para>
</section>
<section id="Registry_VLDB_Configuration">
- <title>3.49 Registry Configuration for AFS Volume Database Servers</title>
+ <title>3.49 Registry Alternative to CellServDB File</title>
<indexterm significance="normal">
<primary>vldb server locations</primary>
</indexterm>
as a substitute for it. The precedence order for lookups is: Registry, File, and then DNS.</para>
</section>
<section>
- <title id="HTMLHelp_Documentation">3.50 Documentation Converted to Windows HTML Help</title>
+ <title id="HTMLHelp_Documentation">3.50 Release Notes Converted to Windows HTML Help</title>
<indexterm significance="normal">
<primary>HTMLHelp</primary>
</indexterm>
<indexterm significance="normal">
<primary>Microsoft Office</primary>
</indexterm>
- <para>Beginning with the 1.5.62 release, the OpenAFS SMB Server supports named pipes and the Microsoft RPC Services
- WKSSVC and SRVSVC. This permits a significantly improved Netbios Server browsing experience with both the
- <emphasis>NET VIEW \\AFS</emphasis> command and the Explorer Shell. No longer will Windows display truncated
- cell names as available network shares. The network share properties will also include the object type and
- and the target of symlinks and mount points.</para>
+ <para>Beginning with the 1.5.62 release, the OpenAFS client supports named pipes and the
+ Microsoft RPC Services WKSSVC and SRVSVC. This permits a significantly improved Netbios
+ Server browsing experience with both the <emphasis>NET VIEW \\AFS</emphasis> command and the
+ Explorer Shell. No longer will Windows display truncated cell names as available network
+ shares. The network share properties will also include the object type and and the target of
+ symlinks and mount points.</para>
</section>
<section>
<title id="fs_newcell_differences">3.52. Differences between Windows and UNIX <emphasis>fs newcell</emphasis></title>
point or symlink as part of a recursive directory tree removal without
crossing into the reparse point target.
</para>
+ <para>The Explorer Shell displays Symlinks and Mount Points using overlay icons.</para>
+ <para><inlinegraphic fileref="relnotes03.jpg" align="center" arch=""/></para>
</section>
<section>
<para>A restart of the service is necessary when adjusting this value. Execute "fs trace -on -reset" to begin the logging and "fs trace -dump" to output the contents of the log to the file.</para>
</section>
<section>
- <title id="Using_Sysinternals_Tools">4.4. Using SysInternal's Debug Viewer, Process Monitor and Process Explorer Tools</title>
+ <title id="Using_Sysinternals_Tools">4.4. Using SysInternal's Debug Viewer, Process Monitor,
+ Process Explorer and Process Dump Tools</title>
<indexterm significance="normal">
<primary>SysInternals</primary>
</indexterm>
<indexterm significance="normal">
<primary>TraceOption</primary>
</indexterm>
- <para>If you are having trouble with the Integrated Logon operations it is often useful to be able to obtain a log of what it is attempting to do. Setting Bit 0 of the
- <link linkend="Value_TraceOption">TraceOption</link> registry value:
- </para>
- <para> [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
- <para> REG_DWORD TraceOption = 0x01</para>
+ <para>If you are having trouble with the Integrated Logon operations it is often useful to be
+ able to obtain a log of what it is attempting to do. Setting the <link
+ linkend="Value_AFSLogon_Debug">Debug</link> registry value: </para>
+ <para> [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]</para>
+ <para> REG_DWORD Debug = 0x01</para>
<para>will instruct the Integrated Logon Network Provider and Event Handlers to log information to the Windows Event Log: Application under the name "AFS Logon".</para>
</section>
<section>
<para>Default: -1</para>
<para>Variable: LANadapter</para>
<para>LAN adapter number to use. This is the lana number of the LAN adapter that the SMB server should bind to. If unspecified or set to -1, a LAN adapter with named 'AFS' or a loopback adapter will be selected. If neither are present, then all available adapters will be bound to. When binding to a non-loopback adapter, the NetBIOS name hostname%-AFS' will be used (where %hostname% is the NetBIOS name of the host truncated to 11 characters). Otherwise, the NetBIOS name will be 'AFS'.</para>
+ <para>[This parameter is ignored unless SMB mode is active.]</para>
</section>
<section>
<title id="Regkey_TransarcAFSDaemon_Parameters_CacheSize">Value: CacheSize</title>
<para>Size of chunk for reading and writing. Actual chunk size is 2^cm_logChunkSize. The default chunk size is therefore 1 MB.</para>
</section>
<section>
+ <title id="Regkey_TransarcAFSDaemon_Parameters_BlockSize">Value: BlockSize</title>
+ <indexterm>
+ <primary>BlockSize</primary>
+ </indexterm>
+ <para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
+ <para>Type: DWORD</para>
+ <para>Default: 4096 (CM_CONFIGDEFAULT_BLOCKSIZE)</para>
+ <para>Size of buffer allocation. Must be an even multiple of 1024 and (2^cm_logChuckSize
+ mod BlockSize) must equal zero.</para>
+ </section>
+ <section>
<title id="Regkey_TransarcAFSDaemon_Parameters_Daemons">Value: Daemons</title>
<para>
<emphasis>Value: Daemons</emphasis>
</para>
<para>Type: DWORD</para>
- <para>Default: 4 (CM_CONFIGDEFAULT_DAEMONS)</para>
+ <para>Default: 16 (CM_CONFIGDEFAULT_DAEMONS)</para>
<para>Variable: numBkgD</para>
<para>Number of background daemons (number of threads of cm_BkgDaemon). (see cm_BkgDaemon in cm_daemon.c)</para>
</section>
<primary>IdleDeadTimeout</primary>
</indexterm>
<para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
- <para>
- Type: DWORD
- </para>
- <para>
- Default: 0 (seconds)
- </para>
- <para>
- Variable: IdleDeadtimeout
- </para>
- <para>The Idle Dead Time determines how long the cache manager will wait for an RPC to complete when the service is responding that it is busy.
- If the timeout occurs on a replicated object, the cache manager can choose to fail over to an alternate replica.
- This value is typically the same as the ConnDeadTimeout. </para>
+ <para>Type: DWORD </para>
+ <para>Default: 1200 (seconds) </para>
+ <para>Variable: IdleDeadtimeout </para>
+ <para>The Idle Dead Time determines how long the cache manager will wait for an RPC on a
+ non-replicated volume to complete when the service is responding only with keep alive
+ messages. When there is no replica available there is no other file server to try. An
+ idle dead timeout in this case is fatal. This option is intended to protect a client
+ against a file server that never responds. This value must be larger that the file
+ server hard dead timeout of 120 seconds.</para>
+ </section>
+ <section>
+ <title>Value: ReplicaIdleDeadTimeout</title>
+ <indexterm>
+ <primary>ReplicaIdleDeadTimeout</primary>
+ </indexterm>
+ <para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
+ <para>Type: DWORD</para>
+ <para>Default: 180 (seconds)</para>
+ <para>Variable: ReplicaIdleDeadtimeout</para>
+ <para>The Replica Idle Dead Time determines how long the cache manager will wait for an
+ RPC on a replicated volume to complete when the service is responding only with keep
+ alive messages. When a volume is replicated the cache manager can choose to retry the
+ request against a file server hosting one of the replicas. This value must be larger
+ that the file server hard dead timeout of 120 seconds.</para>
</section>
<section>
<title id="Regkey_TransarcAFSDaemon_Parameters_NATPingInterval">Value: NATPingInterval</title>
<para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
<para>Type: DWORD {1..32} or {1..64} depending on the architecture
</para>
- <para>
-Default: <no default></para>
- <para>If this value is specified, afsd_service.exe will restrict itself to executing on the specified number of CPUs if there are a greater number installed in the machine. </para>
+ <para> Default: 2</para>
+ <para>If this value is specified, afsd_service.exe will restrict itself to executing on
+ the specified number of CPUs if there are a greater number installed in the machine.
+ Performance profiling shows that overall system performance degrades when the
+ afsd_service.exe is permitted to execute on more than two cores.</para>
</section>
<section>
<title id="Regkey_TransarcAFSDaemon_Parameters_SmbAuthType">Value: SmbAuthType</title>
<para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
<para>Type: DWORD {0, 1}
</para>
- <para>
-Default: 0</para>
+ <para> Default: 1</para>
<para>Determines whether or not the AFS Cache Manager will give up all callbacks prior to the service being suspended or shutdown. Doing so will have significant performance benefits for the file servers. However, file servers older than 1.4.6 can become unstable if the GiveUpAllCallBacks RPC is executed.</para>
<para>0: do not perform GiveUpAllCallBacks RPCs</para>
<para>1: perform GiveUpAllCallBacks RPCs </para>
<para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
<para>Type: DWORD {0, 1}
</para>
- <para>
-Default: 0</para>
- <para>
- Determines whether or not the AFS Cache Manager will will make use of the volume version information reported
- by the file server as part of the AFSVolSync data structure. Use of volume version information can significantly
- reduce the number of FetchStatus RPCs issued on objects stored in read-only volumes. This functionality is
- disabled by default because all OpenAFS file servers older than OpenAFS 1.4.10 failed to include valid volume
- version information as part of the BulkStatus and InlineBulkStatus RPCs.
- </para>
+ <para>Default: 0</para>
+ <para>Determines whether or not the AFS Cache Manager will will make use of the volume
+ version information reported by the file server as part of the AFSVolSync data
+ structure. Use of volume version information can significantly reduce the number of
+ FetchStatus RPCs issued on objects stored in read-only volumes. This functionality is
+ disabled by default because all OpenAFS file servers older than OpenAFS 1.4.10 failed to
+ include valid volume version information as part of the BulkStatus and InlineBulkStatus
+ RPCs. </para>
<para>0: do not make use of volume version information</para>
<para>1: make use of volume version information</para>
</section>
<para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
<para>Type: DWORD {0, 1}
</para>
- <para>
-Default: 0</para>
+ <para>Default: 0</para>
<para>Determines whether or not the AFS Cache Manager will give preference to .backup volumes when following mount points that originate in a .backup volume.</para>
<para>0: do not prefer .backup volumes when the mount point originates in a .backup volume.</para>
<para>1: prefer .backup volumes when the mount point originates in a .backup volume.</para>
<para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
<para>Type: DWORD {bytes}
</para>
- <para>
-Default: 262144</para>
+ <para>Default: 262144</para>
<para>Specifies the UDP socket receive and send buffer sizes..</para>
</section>
+ <section>
+ <title>Value: VerifyData</title>
+ <indexterm>
+ <primary>VerifyData</primary>
+ </indexterm>
+ <para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
+ <para>Type: DWORD {0, 1}</para>
+ <para>Default: 0</para>
+ <para>1: after every RXAFS_StoreData RPC immediately perform an RXAFS_FetchData RPC and
+ verify that the data was correctly stored on the file server. If the data does not
+ match, retry the store operation until it does.</para>
+ <para>The "fs getverify" and "fs setverify {on, off}" commands can be used to query and
+ set this value at runtime.</para>
+ </section>
</section>
<section>
<title id="Regkey_TransarcAFSDaemon_Parameters_GlobalAutoMapper">Regkey:
<para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]</para>
<para>Type: DWORD
</para>
- <para>
-Default: 0</para>
+ <para>Default: 0</para>
<para>Do not display message boxes if the login fails.</para>
</section>
</section>
<para>Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]</para>
<para>Type: DWORD
</para>
- <para>
-Default: 0</para>
+ <para>Default: 0</para>
<para>Disables visible warnings during logon.</para>
</section>
<section>
+ <title id="Value_AFSLogon_Debug">Value: Debug</title>
+ <para>Regkey:
+ [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]</para>
+ <para>Type: DWORD</para>
+ <para>Default: 0</para>
+ <para>Set to 1 to turn on "AFS Logon" event logging to the Windows Event Log.</para>
+ </section>
+ <section>
<title id="NP_Regkey_TransarcAFSDaemon_NetworkProvider_AuthentProviderPath">Value: AuthentProviderPath</title>
<indexterm significance="normal">
<primary>AuthentProviderPath</primary>
<para>Specifies the DLL to use for the network provider</para>
</section>
</section>
- </section>
- <section id="Domain_Specific_Configuration">
- <title>A.2.1 Domain specific configuration keys for the Network Provider</title>
- <indexterm significance="normal">
- <primary>domain logon configuration</primary>
- </indexterm>
- <para>The network provider can be configured to have different behavior depending on the domain that the user logs into. These settings are only relevant when using integrated login. A domain refers to an Active Directory (AD) domain, a trusted Kerberos (non-AD) realm or the local machine (i.e. local account logins). The domain name that is used for selecting the domain would be the domain that is passed into the NPLogonNotify function of the network provider.</para>
- <para>Domain specific registry keys are:</para>
- <section>
- <title id="Domain_Regkey_TransarcAFSDaemon_NetworkProvider">Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]</title>
- <para> (NP key)</para>
- </section>
- <section>
- <title id="Domain_Regkey_TransarcAFSDaemon_NetworkProvider_Domain">Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</title>
- <para> (Domains key)</para>
- </section>
- <section>
- <title id="Domain_Regkey_TransarcAFSDaemon_NetworkProvider_Domain_DomainName">Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<Domain Name>]</title>
- <para> (Specific domain key. One per domain.)</para>
- </section>
- <section>
- <title id="Domain_Regkey_TransarcAFSDaemon_NetworkProvider_Domain_LocalHost">Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</title>
- <para> (Localhost key)</para>
- </section>
- <section>
- <title id="Domain_Example">Domain Specific Example:</title>
- <para>HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider</para>
- <para> |</para>
- <para> +- Domain</para>
- <para> +-AD1.EXAMPLE.COM</para>
- <para> +-AD2.EXAMPLE.NET</para>
- <para> +-LOCALHOST</para>
- <para>Each of the domain specific keys can have the set of values described in 2.1.1. The effective values are chosen as described in 2.1.2.</para>
- </section>
- <section>
- <title id="Domain_Specific_Configuration_Values">A.2.1.1 Domain Specific Configuration Values</title>
- <section id="Domain_Specific_Regkeys">
- <title>Regkeys: [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]</title>
- <section>
- <title id="Domain_Specific_Regkeys_LogonOptions">Value: LogonOptions</title>
- <indexterm significance="normal">
- <primary>LogonOptions</primary>
- </indexterm>
- <para id="Value_LogonOptions">[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
- <para>Type: DWORD
- </para>
- <para>
-Default: 0x01</para>
- <para>NSIS/WiX: depends on user configuration</para>
- <para>
- <simplelist type="vert">
- <member>0x00 - Integrated Logon is not used
-</member>
- <member>
-0x01 - Integrated Logon is used
-</member>
- <member>
-0x02 - High Security Mode is used (deprecated)
-</member>
- <member>
-0x03 - Integrated Logon with High Security Mode is used (deprecated)
-</member>
- </simplelist>
- </para>
- <para>High Security Mode generates random SMB names for the creation of Drive Mappings. This mode should not be used without Integrated Logon.</para>
- <para>As of 1.3.65 the SMB server supports SMB authentication. The High Security Mode should not be used when using SMB authentication (SMBAuthType setting is non zero).</para>
+ <section id="Domain_Specific_Configuration">
+ <title>A.2.1 Domain specific configuration keys for the Network Provider</title>
+ <indexterm significance="normal">
+ <primary>domain logon configuration</primary>
+ </indexterm>
+ <para>The network provider can be configured to have different behavior depending on the
+ domain that the user logs into. These settings are only relevant when using integrated
+ login. A domain refers to an Active Directory (AD) domain, a trusted Kerberos (non-AD)
+ realm or the local machine (i.e. local account logins). The domain name that is used for
+ selecting the domain would be the domain that is passed into the NPLogonNotify function of
+ the network provider.</para>
+ <para>Domain specific registry keys are:</para>
+ <section>
+ <title id="Domain_Regkey_TransarcAFSDaemon_NetworkProvider">Regkey:
+ [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]</title>
+ <para> (NP key)</para>
+ </section>
+ <section>
+ <title id="Domain_Regkey_TransarcAFSDaemon_NetworkProvider_Domain">Regkey:
+ [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</title>
+ <para> (Domains key)</para>
+ </section>
+ <section>
+ <title id="Domain_Regkey_TransarcAFSDaemon_NetworkProvider_Domain_DomainName">Regkey:
+ [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<Domain
+ Name>]</title>
+ <para> (Specific domain key. One per domain.)</para>
+ </section>
+ <section>
+ <title id="Domain_Regkey_TransarcAFSDaemon_NetworkProvider_Domain_LocalHost">Regkey:
+ [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</title>
+ <para> (Localhost key)</para>
+ </section>
+ <section>
+ <title id="Domain_Example">Domain Specific Example:</title>
+ <para>HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider</para>
+ <para> |</para>
+ <para> +- Domain</para>
+ <para> +-AD1.EXAMPLE.COM</para>
+ <para> +-AD2.EXAMPLE.NET</para>
+ <para> +-LOCALHOST</para>
+ <para>Each of the domain specific keys can have the set of values described in 2.1.1. The
+ effective values are chosen as described in 2.1.2.</para>
+ </section>
+ <section>
+ <title id="Domain_Specific_Configuration_Values">A.2.1.1 Domain Specific Configuration
+ Values</title>
+ <section id="Domain_Specific_Regkeys">
+ <title>Regkeys:
+ [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]</title>
+ <section>
+ <title id="Domain_Specific_Regkeys_LogonOptions">Value: LogonOptions</title>
+ <indexterm significance="normal">
+ <primary>LogonOptions</primary>
+ </indexterm>
+ <para id="Value_LogonOptions"
+ >[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain
+ name>]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
+ <para>Type: DWORD </para>
+ <para> Default: 0x01</para>
+ <para>NSIS/WiX: depends on user configuration</para>
+ <para>
+ <simplelist type="vert">
+ <member>0x00 - Integrated Logon is not used </member>
+ <member> 0x01 - Integrated Logon is used </member>
+ </simplelist>
+ </para>
+ </section>
+ <section>
+ <title id="Domain_Specific_Regkeys_FailLoginsSilently">Value:
+ FailLoginsSilently</title>
+ <indexterm significance="normal">
+ <primary>FailLoginsSilently</primary>
+ </indexterm>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain
+ name>]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
+ <para>Type: DWORD (1|0) </para>
+ <para> Default: 0 </para>
+ <para> NSIS/WiX: (not set)</para>
+ <para>If true, does not display any visible warnings in the event of an error during
+ the integrated login process.</para>
+ </section>
+ <section>
+ <title id="Domain_Specific_Regkeys_LogonScript">Value: LogonScript</title>
+ <indexterm significance="normal">
+ <primary>LogonScript</primary>
+ </indexterm>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain
+ name>]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
+ <para>Type: REG_SZ or REG_EXPAND_SZ </para>
+ <para> Default: (null) </para>
+ <para> NSIS/WiX: (only value under NP key) <install path>\afscreds.exe -:%s -x
+ -a -m -n -q</para>
+ <para>A logon script that will be scheduled to be run after the profile load is
+ complete. If using the REG_EXPAND_SZ type, you can use any system environment
+ variable as "%varname%" which would be expanded at the time the network provider is
+ run. Optionally using a "%s" in the value would result in it being expanded into the
+ AFS SMB username for the session.</para>
+ </section>
+ <section>
+ <title id="Domain_Specific_Regkeys_LoginRetryInterval">Value:
+ LoginRetryInterval</title>
+ <indexterm significance="normal">
+ <primary>LoginRetryInterval</primary>
+ </indexterm>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain
+ name>]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
+ <para>Type: DWORD </para>
+ <para> Default: 30 </para>
+ <para> NSIS/WiX: (not set)</para>
+ <para>If the OpenAFS client service has not started yet, the network provider will
+ wait for a maximum of "LoginRetryInterval" seconds while retrying every
+ "LoginSleepInterval" seconds to check if the service is up.</para>
+ </section>
+ <section>
+ <title id="Domain_Specific_Regkeys_LoginSleepInterval">Value:
+ LoginSleepInterval</title>
+ <indexterm significance="normal">
+ <primary>LoginSleepInterval</primary>
+ </indexterm>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain
+ name>]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
+ <para>Type: DWORD </para>
+ <para> Default: 5 </para>
+ <para> NSIS/WiX: (not set)</para>
+ <para>See description of LoginRetryInterval.</para>
+ </section>
+ <section>
+ <title id="Domain_Specific_Regkeys_Realm">Value: Realm</title>
+ <indexterm significance="normal">
+ <primary>Realm</primary>
+ </indexterm>
+ <para id="Value_Realm"
+ >[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain
+ name>]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
+ <para>Type: REG_SZ </para>
+ <para> NSIS: <not set></para>
+ <para>When Kerberos v5 is being used, Realm specifies the Kerberos v5 realm that
+ should be appended to the first component of the Domain logon username to construct
+ the Kerberos v5 principal for which AFS tokens should be obtained.</para>
+ </section>
+ <section>
+ <title id="Domain_Specific_Regkeys_TheseCells">Value: TheseCells</title>
+ <indexterm significance="normal">
+ <primary>TheseCells</primary>
+ </indexterm>
+ <para id="Value_TheseCells"
+ >[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain
+ name>]</para>
+ <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
+ <para>Type: REG_MULTI_SZ </para>
+ <para> NSIS: <not set></para>
+ <para>When Kerberos v5 is being used, TheseCells provides a list of additional cells
+ for which tokens should be obtained with the default Kerberos v5 principal.</para>
+ </section>
</section>
+ </section>
+ <section>
+ <title id="Selection_Effective_Values_for_Domain_Specific_Configuration">A.2.1.2 Selection
+ of effective values for domain specific configuration</title>
+ <para>During login to domain X, where X is the domain passed into NPLogonNotify as
+ lpAuthentInfo->LogonDomainName or the string 'LOCALHOST' if
+ lpAuthentInfo->LogonDomainName equals the name of the computer, the following keys
+ will be looked up.</para>
+ <para>1. NP key.
+ ("HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider")</para>
+ <para>2. Domains key. (NP key\"Domain")</para>
+ <para>3. Specific domain key. (Domains key\X)</para>
+ <para>If the specific domain key does not exist, then the domains key will be ignored. All
+ the configuration information in this case will come from the NP key.</para>
+ <para>If the specific domain key exists, then for each of the values metioned in (2), they
+ will be looked up in the specific domain key, domains key and the NP key successively
+ until the value is found. The first instance of the value found this way will be the
+ effective for the login session. If no such instance can be found, the default will be
+ used. To re-iterate, a value in a more specific key supercedes a value in a less
+ specific key. The exceptions to this rule are stated below.</para>
+ </section>
+ <section>
+ <title id="Domain_Specific_Configuration_Exceptions">A.2.1.3 Exceptions to A.2.1.2</title>
+ <para>To retain backwards compatibility, the following exceptions are made to
+ A.2.1.2.</para>
<section>
- <title id="Domain_Specific_Regkeys_FailLoginsSilently">Value: FailLoginsSilently</title>
+ <title id="Domain_Specific_Configuration_Exception_FailLoginsSilently">2.1.3.1
+ 'FailLoginsSilently'</title>
<indexterm significance="normal">
<primary>FailLoginsSilently</primary>
</indexterm>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
- <para>Type: DWORD (1|0)
- </para>
- <para>
-Default: 0
- </para>
- <para>
-NSIS/WiX: (not set)</para>
- <para>If true, does not display any visible warnings in the event of an error during the integrated login process.</para>
+ <para>Historically, the 'FailLoginsSilently' value was in
+ HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters key and not in the
+ NP key. Therefore, for backwards compatibility, the value in the Parameters key will
+ supercede all instances of this value in other keys. In the absence of this value in
+ the Parameters key, normal scope rules apply.</para>
</section>
<section>
- <title id="Domain_Specific_Regkeys_LogonScript">Value: LogonScript</title>
+ <title id="Domain_Specific_Configuration_Exception_LogonScript">2.1.3.2
+ 'LogonScript'</title>
<indexterm significance="normal">
<primary>LogonScript</primary>
</indexterm>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
- <para>Type: REG_SZ or REG_EXPAND_SZ
- </para>
- <para>
-Default: (null)
- </para>
- <para>
-NSIS/WiX: (only value under NP key) <install path>\afscreds.exe -:%s -x -a -m -n -q</para>
- <para>A logon script that will be scheduled to be run after the profile load is complete. If using the REG_EXPAND_SZ type, you can use any system environment variable as "%varname%" which would be expanded at the time the network provider is run. Optionally using a "%s" in the value would result in it being expanded into the AFS SMB username for the session.</para>
- </section>
- <section>
- <title id="Domain_Specific_Regkeys_LoginRetryInterval">Value: LoginRetryInterval</title>
- <indexterm significance="normal">
- <primary>LoginRetryInterval</primary>
- </indexterm>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
- <para>Type: DWORD
- </para>
- <para>
-Default: 30
- </para>
- <para>
-NSIS/WiX: (not set)</para>
- <para>If the OpenAFS client service has not started yet, the network provider will wait for a maximum of "LoginRetryInterval" seconds while retrying every "LoginSleepInterval" seconds to check if the service is up.</para>
- </section>
- <section>
- <title id="Domain_Specific_Regkeys_LoginSleepInterval">Value: LoginSleepInterval</title>
- <indexterm significance="normal">
- <primary>LoginSleepInterval</primary>
- </indexterm>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
- <para>Type: DWORD
- </para>
- <para>
-Default: 5
- </para>
- <para>
-NSIS/WiX: (not set)</para>
- <para>See description of LoginRetryInterval.</para>
- </section>
- <section>
- <title id="Domain_Specific_Regkeys_Realm">Value: Realm</title>
- <indexterm significance="normal">
- <primary>Realm</primary>
- </indexterm>
- <para id="Value_Realm">[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
- <para>Type: REG_SZ
- </para>
- <para>
-NSIS: <not set></para>
- <para>When Kerberos v5 is being used, Realm specifies the Kerberos v5 realm that should be appended to the first component of the Domain logon username to construct the Kerberos v5 principal for which AFS tokens should be obtained.</para>
- </section>
- <section>
- <title id="Domain_Specific_Regkeys_TheseCells">Value: TheseCells</title>
- <indexterm significance="normal">
- <primary>TheseCells</primary>
- </indexterm>
- <para id="Value_TheseCells">[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>]</para>
- <para>[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST]</para>
- <para>Type: REG_MULTI_SZ
- </para>
- <para>
-NSIS: <not set></para>
- <para>When Kerberos v5 is being used, TheseCells provides a list of additional cells for which tokens should be obtained with the default Kerberos v5 principal.</para>
+ <para>If a 'LogonScript' is not specified in the specific domain key nor in the domains
+ key, the value in the NP key will only be checked if the effective 'LogonOptions'
+ specify a high security integrated login. If a logon script is specified in the
+ specific domain key or the domains key, it will be used regardless of the high
+ security setting. Please be aware of this when setting this value.</para>
</section>
</section>
</section>
- <section>
- <title id="Selection_Effective_Values_for_Domain_Specific_Configuration">A.2.1.2 Selection of effective values for domain specific configuration</title>
- <para>During login to domain X, where X is the domain passed into NPLogonNotify as lpAuthentInfo->LogonDomainName or the string 'LOCALHOST' if lpAuthentInfo->LogonDomainName equals the name of the computer, the following keys will be looked up.</para>
- <para>1. NP key. ("HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider")</para>
- <para>2. Domains key. (NP key\"Domain")</para>
- <para>3. Specific domain key. (Domains key\X)</para>
- <para>If the specific domain key does not exist, then the domains key will be ignored. All the configuration information in this case will come from the NP key.</para>
- <para>If the specific domain key exists, then for each of the values metioned in (2), they will be looked up in the specific domain key, domains key and the NP key successively until the value is found. The first instance of the value found this way will be the effective for the login session. If no such instance can be found, the default will be used. To re-iterate, a value in a more specific key supercedes a value in a less specific key. The exceptions to this rule are stated below.</para>
- </section>
- <section>
- <title id="Domain_Specific_Configuration_Exceptions">A.2.1.3 Exceptions to A.2.1.2</title>
- <para>To retain backwards compatibility, the following exceptions are made to A.2.1.2.</para>
- <section>
- <title id="Domain_Specific_Configuration_Exception_FailLoginsSilently">2.1.3.1 'FailLoginsSilently'</title>
- <indexterm significance="normal">
- <primary>FailLoginsSilently</primary>
- </indexterm>
- <para>Historically, the 'FailLoginsSilently' value was in HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters key and not in the NP key. Therefore, for backwards compatibility, the value in the Parameters key will supercede all instances of this value in other keys. In the absence of this value in the Parameters key, normal scope rules apply.</para>
- </section>
- <section>
- <title id="Domain_Specific_Configuration_Exception_LogonScript">2.1.3.2 'LogonScript'</title>
- <indexterm significance="normal">
- <primary>LogonScript</primary>
- </indexterm>
- <para>If a 'LogonScript' is not specified in the specific domain key nor in the domains key, the value in the NP key will only be checked if the effective 'LogonOptions' specify a high security integrated login. If a logon script is specified in the specific domain key or the domains key, it will be used regardless of the high security setting. Please be aware of this when setting this value.</para>
- </section>
- </section>
</section>
<section>
<title id="AFSCreds_Parameters">A.3. AFS Credentials System Tray Tool parameters</title>
<para>Regkey: [HKCU\SOFTWARE\OpenAFS\Client\Mappings]</para>
<para>Type: REG_SZ
</para>
- <para>
-Default: <none></para>
+ <para>Default: <none></para>
<para>These values are used to store the AFS path in UNIX notation to which the drive letter is to be mapped.</para>
<para>These values used to be stored in the afsdsbmt.ini file.</para>
</section>
</para>
</section>
</section>
+ <section>
+ <title>A.5 AFS Redirector Parameters</title>
+ <indexterm>
+ <primary>afsredir.sys</primary>
+ </indexterm>
+ <indexterm>
+ <primary>afsredirlib.sys</primary>
+ </indexterm>
+ <para>The AFS Redirector is implemented with three components:
+ %windir%\system32\drivers\AFSRedir.sys, %windir%\system32\drivers\AFSRedirLib.sys and
+ %windir%\system32\AFSRDFSProvider.dll. These components provide the interface between the
+ Windows Installable File System interface and the WNet application interface and the AFS
+ file system. The </para>
+ <section>
+ <title>[HKLM\SYSTEM\CurrentControlSet\Services\AFSRedirector\Parameters]</title>
+ <para/>
+ <section>
+ <title>Value: DebugFlags</title>
+ <para>RegKey: [HKLM\SYSTEM\CurrentControlSet\Services\AFSRedirector\Parameters]</para>
+ <para>Type: REG_DWORD</para>
+ <para>Default: 0</para>
+ <para>Bit 0 (0x1): Trigger Debug Break on AFSRedir.sys start. Used for kernel
+ debugging.</para>
+ <para>Bit 1 (0x2): Output trace logging to Kernel Debugger. Used for kernel
+ debugging.</para>
+ <para>Bit 2 (0x4): Enable Force Crash Ioctl. Checked builds only. Used for force a
+ BSOD.</para>
+ <para>Bit 3 (0x8): Enable Bug Check on all exceptions. Normally exceptions are caught by
+ handlers. Used during testing.</para>
+ <para>Bit 4 (0x10): Reserved.</para>
+ <para>Bit 5 (0x20): Do not start the AFS Redirector if Windows did not perform a clean
+ shutdown.</para>
+ </section>
+ <section>
+ <title>Value: TraceBufferSize</title>
+ <para>RegKey: [HKLM\SYSTEM\CurrentControlSet\Services\AFSRedirector\Parameters]</para>
+ <para>Type: REG_DWORD</para>
+ <para>Default: 0 {0 .. 10000} (KBs)</para>
+ <para>Specifies the size of the circular trace log buffer allocated within kernel memory.
+ 0 disables trace logging.</para>
+ </section>
+ <section>
+ <title>Value: TraceLevel</title>
+ <para>RegKey: [HKLM\SYSTEM\CurrentControlSet\Services\AFSRedirector\Parameters]</para>
+ <para>Type: REG_DWORD</para>
+ <para>Default: 0 {0..4}</para>
+ <para>0: No logging; 1: Error; 2: Warning; 3: Verbose; 4: Maximum Verbosity</para>
+ </section>
+ <section>
+ <title>Value: TraceSubsystem</title>
+ <para>RegKey: [HKLM\SYSTEM\CurrentControlSet\Services\AFSRedirector\Parameters]</para>
+ <para>Type: REG_DWORD</para>
+ <para>Default: 0</para>
+ <para>Bit 0 (0x1): I/O Subsystem</para>
+ <para>Bit 1 (0x2): File Control Blocks and Name Processing</para>
+ <para>Bit 2 (0x4): Lock Processing (requires Verbose or higher level)</para>
+ <para>Bit 3 (0x8): Extent Processing</para>
+ <para>Bit 4 (0x10): Worker Thread Processing</para>
+ <para>Bit 5 (0x20): Reference counting of directory entries</para>
+ <para>Bit 6 (0x40): Reference counting of objects</para>
+ <para>Bit 7 (0x80): Reference counting of volumes</para>
+ <para>Bit 8 (0x100): Reference counting of file control blocks</para>
+ <para>Bit 9 (0x200): Garbage Collection</para>
+ <para>Bit 10 (0x400): Pipe and share processing</para>
+ <para>Bit 11 (0x800): Directory notification interface</para>
+ <para>Bit 12 (0x1000): Network Provider support processing</para>
+ <para>Bit 13 (0x2000): Directory node count processing</para>
+ <para>Bit 14 (0x4000): PIOCTL processing</para>
+ <para>Bit 15 (0x8000): Authentication Group creation and assignment</para>
+ <para>Bit 16 (0x10000): Library load and unload, task queuing</para>
+ <para>Bit 17 (0x20000): Process creation and destruction</para>
+ <para>Bit 18 (0x40000): Extent Active counting</para>
+ <para>Bit 19 (0x80000): Redirector initialization</para>
+ </section>
+ </section>
+ <section>
+ <title>[HKLM\SYSTEM\CurrentControlSet\Services\AFSRedirector\NetworkProvider]</title>
+ <para/>
+ <section>
+ <title>Value: Debug</title>
+ <para>RegKey:
+ [HKLM\SYSTEM\CurrentControlSet\Services\AFSRedirector\NetworkProvider]</para>
+ <para>Type: REG_DWORD</para>
+ <para>Default: 0</para>
+ <para>Set to 1 to log all AFSRDFSProvider Network Provider requests to
+ C:\TEMP\AFSRDFSProvider.log. The C:\TEMP directory cannot be changed and must
+ exist.</para>
+ </section>
+ <section>
+ <title>Value: Name</title>
+ <para>RegKey:
+ [HKLM\SYSTEM\CurrentControlSet\Services\AFSRedirector\NetworkProvider]</para>
+ <para>Type: REG_SZ</para>
+ <para>Default: "OpenAFS Network"</para>
+ <para>This value defines the name displayed in the Explorer Shell and to which network
+ drive mappings are made.</para>
+ </section>
+ </section>
+ </section>
</chapter>
<index>
<para>
git://git.openafs.org / openafs.git / blobdiff