There are two things to consider when using a Microsoft Windows Active Directory as the Kerberos realm that issues the AFS service @@ -2843,8 +3631,8 @@ style='mso-element:field-begin'> XE "DES enctypes"

Some organizations which have AFS cell names and Kerberos realm names which differ by more then just lower and upper case rely on a @@ -2871,10 +3659,10 @@ a win in all situations except when the cell name does not match the realm name and the principal names placed into the ACLs are not the principal names from the Kerberos 5 ticket. To support this transition, OpenAFS for Windows 1.4 adds a new registry value, Use524, to force the use of krb524d. However, the availability of this option -should only be used by individuals until such time as their organizations can -provide a more permanent solution.

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 @@ -3166,8 +3954,8 @@ style='mso-spacerun:yes'> change this selection after install time although these options may be altered via the registry on either per machine or per user basis. See AfscredsShortcutParams in Appendix A.

The OpenAFS for Windows 1.4 client supports a local Windows authorization group named "AFS Client Admins". This group is used in place of the -"Administrators" group to determine which users are allowed to modify -the AFS Client Service configuration via the AFS Control Panel (afs_config.exe) -or fs.exe command line tool. The -following fs.exe commands are now restricted to members of the "AFS Client -Admins" group:

Setting the default sysname for a machine should be done via -the registry and not via "fs -sysname".

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 +weak form of encrypted data transfer between the AFS client and the AFS +servers. This is often referred to as "fcrypt" mode.

3.15. No More INI Files

Previous AFS clients for Windows stored configuration data -in Windows .INI files. OpenAFS 1.4 does +in Windows .INI files. OpenAFS 1.4 does not use Windows .INI files for the storage of configuration data. All settings are now stored in the registry -(see Appendix A). The CellServDB file is now stored in the -%PROGRAMFILES%\OpenAFS\Client directory. -The CellServDBDir registry value can be -used to specify an alternative location.

OpenAFS 1.4 will relocate the contents of the afsdcell.ini file to the new CellServDB file. OpenAFS @@ -3500,8 +4286,8 @@ appropriate Back Connection registry entries are added to allow SMB authentication to be performed across the Microsoft Loopback Adapter.

3.17. Browsing AFS -from the Explorer Shell and Office

The OpenAFS 1.4 Client Service implements the CIFS Remote Admin Protocol which allows Explorer to browse server and share information. @@ -3517,31 +4303,43 @@ w:st="on"> Locking -

Many applications on Windows (e.g. Microsoft Office) require -the use of byte range locks applied to a file either to protect against +

Many applications on Windows (e.g. Microsoft Office) +require the use of byte range locks applied to a file either to protect against simultaneous file access or as a signaling mechanism. As of 1.4.1, OpenAFS for Windows utilizes -AFS' advisory locks to simulate Microsoft Windows mandatory locks. When an application opens a file, a lock -will be placed in AFS indicating that the file is in use. If the lock is a write lock, the use of the -file will be restricted to other applications running on the same machine as -the first application to apply the lock. -Applications running on other machines will see the full lock and will -be unable to access the file.

Most Windows applications and Windows itself opens files in -shared read mode. When this is done, a read lock is applied to the file. This does not prevent shared read access -across multiple machines but is used to ensure that no one writes to the file -while it is in use.

As locks are checked and applied during the file open -operation, it is crucial that users have the locking 'k' privilege in all -directories in which the user might read a file or execute an application -unless the directory exists on a read only volume. A failure to assign the 'k' privilege will -result in "Access Denied" errors during file open.

Note: +In a future release, OpenAFS for Windows will utilize +AFS' advisory locks to simulate Microsoft Windows mandatory locks. +When an application opens a file, a lock will be placed in AFS indicating that +the file is in use. If the lock is a write lock, the use of the file will +be restricted to other applications running on the same machine as the first +application to apply the lock. Applications running on other +machines will see the full lock and will be unable to access the file.

Most Windows +applications and Windows itself opens files in shared read mode. When this is +done, a read lock is applied to the file. This does not prevent +shared read access across multiple machines but is used to ensure that no one +writes to the file while it is in use.

As locks are checked and applied during the file open operation, it is +crucial that users have the locking 'k' privilege in all directories in which +the user might read a file or execute an application unless the directory +exists on a read only volume. A failure to assign the 'k' privilege will +result in "Access Denied" errors during file open.

3.19. Automatic @@ -3550,16 +4348,17 @@ Discarding of AFS Tokens at Logoff

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.

3.20. Terminal @@ -3593,9 +4392,9 @@ directory entry accessed within the AFS file system. When the maximum number of entries are allocated, entries will begin to be reused according to a least recently used (LRU) algorithm. If the number of files -or directories being accessed repeatedly by your applications is greater then -the maximum number of entries, your host will begin to experience thrashing of -the Status Cache and all requests will result in network operations.

+or directories being accessed repeatedly by your applications is greater then the +maximum number of entries, your host will begin to experience thrashing of the +Status Cache and all requests will result in network operations.

If you are experiencing poor performance try increasing the maximum number of Status Cache entries. @@ -3608,8 +4407,8 @@ over TCP/IP must be enabled

"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 +style='mso-spacerun:yes'> If "Netbios over TCP/IP" is +disabled on the machine, then communication with the AFS Client Service will be impossible.

Appendix A -documents the "VerifyServiceSignature" +

Appendix A +documents the "VerifyServiceSignature" registry value which can be used to disable the signature check. The file version check cannot be disabled.

@@ -3836,21 +4637,21 @@ characters:

OpenAFS 1.4 provides an optional registry value, StoreAnsiFilenames, that can be -set to instruct OpenAFS to store filenames using the ANSI Code Page instead of -the OEM Code Page. The ANSI Code Page is -a compatible superset of Latin-1. This -setting is not the default setting because making this change would prevent -OpenAFS for Windows from being able to access filenames containing the above -characters which were created without this setting.

+href="oafw-1-4-release-notes.doc#_Value___: StoreAnsiFilenames">StoreAnsiFilenames, +that can be set to instruct OpenAFS to store filenames using the ANSI Code Page +instead of the OEM Code Page. The ANSI +Code Page is a compatible superset of Latin-1. +This setting is not the default setting because making this change would +prevent OpenAFS for Windows from being able to access filenames containing the +above characters which were created without this setting.

3.27. Known Character Set Issues with Roaming Profiles

There is a known issue with storing Windows Roaming Profiles -when the profile contains either directories or files with names which cannot be -represented in the local OEM character set. +when the profile contains either directories or files with names which cannot +be represented in the local OEM character set. In this case, attempts to write the profile back to AFS will fail. OpenAFS for Windows does not currently support UNICODE. To avoid this problem @@ -3862,8 +4663,8 @@ name="_Toc115416134">3.28. The AFSCache File

The AFS Cache file is stored by default at %TEMP%\AFSCache -in a persistent file marked with the Hidden and System attributes. The persistent nature of the data stored in +in a persistent file marked with the Hidden and System attributes. The persistent nature of the data stored in the cache file improves the performance of OpenAFS by reducing the number of times data must be read from the AFS file servers.

In OpenAFS 1.4, symlinks to AFS UNC paths, \\AFS[\all]\..., are treated the same as symlinks to /afs/... -However, please use /afs/... as the Windows UNC form will not work on -UNIX.

3.32. Cache -Manager Debugging Now Supported

OpenAFS for Windows 1.4 implements the Cache Manager Debugging RPC Interface. The CM debugger @@ -3963,8 +4763,10 @@ Server Preferences values using registry keys. This is useful for managed machines in a Windows domain which are centrally located (e.g., in a computing lab.) See Appendix A for details on the "Server Preferences" keys.

3.35. File @@ -3973,7 +4775,7 @@ Timestamps

OpenAFS 1.4 reports timestamps on files stored in AFS in UTC all year round. In locales with daylight savings time, previous versions of AFS for Windows reported the time when DST -is active as UTC+1. This was done to +is active as UTC+1. This was done to preserve the relative local time for the user. A file stored at 11:00am EST in January would be reported as having been stored at 11:00am EDT in June. @@ -4044,14 +4846,14 @@ _Toc115417081'>4. How to Debug Problems with OpenAFS for Windows:

OpenAFS for Windows provides a wide range of tools to assist -you in debugging problems. The techniques -available to you are varied because of the wide range of issues that have been -discovered over the years.

4.1. pioctl -debugging (IoctlDebug IoctlDebug registry key)

· setting/querying @@ -4159,10 +4961,10 @@ style='mso-spacerun:yes'> code will quickly reveal the reason for the termination.

The MaxLogSize registry value determines the -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.MaxLogSize +registry value determines the 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.

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 TraceOption registry value:

-cache print only cache @@ -4368,14 +5175,14 @@ installer. for the problem, %WINDIR%\TEMP\afsd.dmp, include it along with the AFS Client Trace file %WINDIR%\TEMP\afsd.log. The AFS Client startup log is -%WINDIR%\TEMP\afsd_init.log. Send the last -continuous block of log information from -this file.

· Run @@ -4383,77 +5190,77 @@ drwtsn32.exe to configure or to identify where the log and the crash dump files are created:

· Once @@ -4487,8 +5294,8 @@ will be allocated by the OpenAFS Elders to fund OpenAFS development, documentation, project management, and maintaining openafs.org.

+no-wrap-beside;mso-element-anchor-vertical:page;mso-element-left:.05pt; +mso-element-top:372.8pt'> @@ -4496,8 +5303,7 @@ column;mso-element-left:.05pt;mso-element-top:372.8pt;mso-height-rule:exactly'> 9.0pt;padding-bottom:0pt;padding-left:9.0pt'>

USENIX OpenAFS Fund
+ mso-element-left:.05pt;mso-element-top:372.8pt'>USENIX OpenAFS Fund
USENIX Association
2560 Ninth St., Suite 215
@@ -4512,55 +5318,59 @@ column;mso-element-left:.05pt;mso-element-top:372.8pt;mso-height-rule:exactly'>
-

Donations can be made by sending a check, drawn on a U.S. bank, -made out to the USENIX OpenAFS Fund or by making a Donations can be made by sending a check, drawn on a U.S. +bank, made out to the USENIX OpenAFS Fund or by making a donation online.

6.2. Secure -Endpoints Inc.

6.2. Secure Endpoints Inc.

Secure -Endpoints Inc. provides development and support services for OpenAFS for -Windows and MIT Kerberos for Windows. -Donations provided to Secure Endpoints Inc. for the development of -OpenAFS are used to cover the OpenAFS gatekeeper responsibilities; providing -support to the OpenAFS community via the OpenAFS mailing lists; and furthering -development of desired features that are either too small to be financed by -development contracts.

Secure Endpoints Inc. provides +development and support services for OpenAFS for Windows and MIT Kerberos for +Windows. Donations provided to Secure +Endpoints Inc. for the development of OpenAFS are used to cover the OpenAFS +gatekeeper responsibilities; providing support to the OpenAFS community via the +OpenAFS mailing lists; and furthering development of desired features that are +either too small to be financed by development contracts.

Secure Endpoints Inc. accepts software development -agreements from organizations who wish to fund a well-defined set of bug fixes -or new features.

Secure Endpoints +Inc. accepts software development agreements from organizations who wish to +fund a well-defined set of bug fixes or new features.

Secure Endpoints Inc. provides contract based support for -the OpenAFS for Windows and the MIT Kerberos for Windows products.

Secure Endpoints +Inc. provides contract based support for the OpenAFS for Windows and the MIT +Kerberos for Windows products.

6.3. The -MIT Kerberos Account

6.3. The MIT Kerberos Account

The MIT Kerberos development team accepts -unrestricted grants. Grants are tax -deductible and the full amount of the grant will be used to fund the -development of Kerberos 5 and/or Kerberos for Windows. OpenAFS for Windows is dependent on MIT -Kerberos for Windows for authentication and shares many of the same requirements for credential management. Future releases of both products will share a -common identity management user interface.

- -

6.4. Direct -contributions of code and/or documentation

- -

Organizations that use OpenAFS in house and have -development staffs are encouraged to contribute any code modifications they -make to OpenAFS.org via openafs-bugs@openafs.org. Contributions of documentation are highly -desired.

+color:black;mso-fareast-language:JA'>The MIT +Kerberos development team accepts unrestricted grants. Grants are tax deductible and the full amount +of the grant will be used to fund the development of Kerberos 5 and/or Kerberos +for Windows. OpenAFS for Windows is +dependent on MIT Kerberos for Windows for authentication and shares many of the +same requirements for credential +management. Future releases of both +products will share a common identity management user interface.

+ +

6.4. Direct contributions of code and/or +documentation

+ +

Organizations that +use OpenAFS in house and have development staffs are encouraged to contribute +any code modifications they make to OpenAFS.org via openafs-bugs@openafs.org. + Contributions of documentation are +highly desired.

6.5. OpenAFS for Windows Mailing Lists

@@ -4586,14 +5396,14 @@ name="_Toc115417098">7. -MSI Deployment Guide +style='mso-bookmark:_Toc115417098'>7. MSI +Deployment Guide

@@ -4620,15 +5430,15 @@ Requirements

The information in this document applies to MSI packages distributed with OpenAFS for Windows releases from 1.3.65 and onwards or MSI -packages built from corresponding source releases. Not all releases support all the -configuration options documented here.

+packages built from corresponding source releases. Not all releases support all the configuration +options documented here.

Authoring a "Windows Installer" transform requires additional software for editing the MSI database tables and generating the transform from the modified MSI package. -ORCA.EXE and MSITRAN.EXE which are included in the Windows Platform SDK -("Windows Installer" SDK) can be used for this purpose.

+ORCA.EXE and MSITRAN.EXE which are included in the Windows Platform SDK ("Windows +Installer" SDK) can be used for this purpose.

For reference, the schema for the MSI package is based on SCHEMA.MSI distributed with the Platform SDK.

@@ -4655,8 +5465,8 @@ creating a transform at:

http://msdn.microsoft.com/library/en-us/msi/setup/a_customization_transform_example.asp

7.1.2 -Authoring a Transform

7.1.2 Authoring +a Transform

Transforms describe a set of modifications to be performed on an existing MSI for the purpose of customizing it. example:

1. copy openafs.msi openafs-modified.msi

2. (edit the openafs-modified.msi to include the necessary changes)

3. msitran -g openafs.msi openafs-modified.msi openafs-transform.mst

4. (generates openafs-transform.mst, which is the transform)

Transforms have an extension of .mst. 'msitran' is a tool distributed as part of -the "Windows Installer" SDK (part of the Windows Platform SDK).

+style='mso-spacerun:yes'> 'msitran' is a tool distributed as part of the +"Windows Installer" SDK (part of the Windows Platform SDK).

You can test a transform by:

1. copy openafs.msi openafs-test.msi

2. msitran -a openafs-transform.mst openafs-test.msi

@@ -4714,17 +5524,17 @@ the MSI databases directly when editing openafs-modified.msi. More details are given below.

7.2. -Configuration Options

+name="_Toc115416162">7.2. Configuration +Options

The logic necessary to implement many of the settings -described in Appendix A are present -in the MSI. Most of these can be -controlled by setting the corresponding properties to the desired value. Some settings may require modifying existing registry -entries (though not recommended) or adding new resources (like files or -registry keys). Instructions for -performing these tasks are below.

+described in Appendix +A are present in the MSI. Most of +these can be controlled by setting the corresponding properties to the desired +value. Some settings may require +modifying existing registry entries (though not recommended) or adding new +resources (like files or registry keys). +Instructions for performing these tasks are below.

7.2.1 Configurable Properties

@@ -4742,12 +5552,12 @@ the MSI.

When one of the configurable properties is set, the installer will use the property value to set the corresponding setting in the -HKEY_LOCAL_MACHINE registry hive. The -HKEY_CURRENT_USER hive is not touched by the installer.

+HKEY_LOCAL_MACHINE registry hive. The HKEY_CURRENT_USER +hive is not touched by the installer.

For each property, the associated registry setting is -referenced by the same text used in Appendix -A.

+referenced by the same text used in Appendix A.

Strings are quoted using single quotes (e.g. 'a string'). An empty string is denoted as ''. Note that @@ -4760,14 +5570,14 @@ you can't author null values into the 'Property' table.

In order to set a property,

1. Open the MSI in ORCA.EXE

2. @@ -4775,7 +5585,7 @@ style='font:7.0pt "Times New Roman"'> tables on the left.

3. @@ -4783,7 +5593,7 @@ style='font:7.0pt "Times New Roman"'> the right, double click the value and type the new value.

4. @@ -4798,189 +5608,196 @@ desired value.

mso-border-insideh:.75pt outset windowtext;mso-border-insidev:.75pt outset windowtext'>

(Service parameters):

[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]

(Network provider):

(Network + provider):

[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]

(OpenAFS Client):

[HKLM\SOFTWARE\OpenAFS\Client]

(OpenAFS + Client):

[HKLM\SOFTWARE\OpenAFS\Client]

7.2.1.2.1 Registry Properties

These properties are used to set the values of registry entries -associated with OpenAFS for Windows.

These properties are used to set the values of registry +entries associated with OpenAFS for Windows.

@@ -4991,20 +5808,20 @@ associated with OpenAFS for Windows.

style='mso-bookmark:_Toc115416184'>7.2.1.2.2 AFSCreds.exe Properties

These properties are combined to add a command line option -to the shortcut that will be created in the Start:Programs:OpenAFS and Start:Programs:Startup -folders (see CREDSSTARTUP). The method -of specifying the option was chosen for easy integration with the Windows -Installer user interface. Although other -methods can be used to specify options to AFSCREDS.EXE, it is advised that they -be avoided as transforms including such options may not apply to future -releases of OpenAFS.

+to the shortcut that will be created in the Start:Programs:OpenAFS and +Start:Programs:Startup folders (see CREDSSTARTUP). The method of specifying the option was +chosen for easy integration with the Windows Installer user interface. Although other methods can be used to specify +options to AFSCREDS.EXE, it is advised that they be avoided as transforms +including such options may not apply to future releases of OpenAFS.

AFSCACHEPATH

Registry key : (Service - parameters)

+ style='mso-spacerun:yes'> : (Service parameters)

Registry value : CachePath

+ href="oafw-1-4-release-notes.doc#_Value_:_CachePath">CachePath

Valid values : string .

AFSCACHESIZE

Registry key : (Service parameters)

Registry value : CacheSize

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : CacheSize

Valid values : numeric

AFSCELLNAME

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : Cell

+ href="oafw-1-4-release-notes.doc#_Value_:_Cell">Cell

Valid values : string

FREELANCEMODE

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : FreelanceClient

+ href="oafw-1-4-release-notes.doc#_Value_:_FreelanceClient">FreelanceClient

Valid values : '1' or '0'

HIDEDOTFILES

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : HideDotFiles

+ href="oafw-1-4-release-notes.doc#_Value_:_HideDotFiles">HideDotFiles

Valid values : '1' or '0'

LOGONOPTIONS

Registry key : (Network provider)

+ href="oafw-1-4-release-notes.doc#_(Network_provider):">(Network provider)

Registry value : LogonOptions

Valid values : '0', - '1' or '3'

See Appendix A - section 2.1 (Domain specific - configuration keys for Network Provider) for more details.

+ href="oafw-1-4-release-notes.doc#_Value___: LogonOptions">LogonOptions

Valid values : '0', '1' + or '3'

See Appendix A + section + 2.1 (Domain specific configuration keys for Network Provider) for more + details.

MOUNTROOT

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : Mountroot

+ href="oafw-1-4-release-notes.doc#_Value_:_Mountroot">Mountroot

Valid values : string

NETBIOSNAME

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : NetbiosName

+ href="oafw-1-4-release-notes.doc#_Value___: NetbiosName">NetbiosName

Valid values : string (at most 15 characters)

NOFINDLANABYNAME

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : NoFindLanaByName

+ href="oafw-1-4-release-notes.doc#_Value___: NoFindLanaByName">NoFindLanaByName

Valid values : '1' or '0'

RXMAXMTU

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : RxMaxMTU

+ href="oafw-1-4-release-notes.doc#_Value_:_RxMaxMTU">RxMaxMTU

Valid values : numeric

SECURITYLEVEL

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : SecurityLevel

+ href="oafw-1-4-release-notes.doc#_Value_:_SecurityLevel">SecurityLevel

Valid values : '1' or '0'

SMBAUTHTYPE

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : SMBAuthType

+ href="oafw-1-4-release-notes.doc#_Value___: smbAuthType">SMBAuthType

Valid values : '0','1' or '2'

STOREANSIFILENAMES

Registry key : (OpenAFS Client)

+ href="oafw-1-4-release-notes.doc#_(OpenAFS_Client):">(OpenAFS Client)

Registry value : StoreAnsiFilenames

+ href="oafw-1-4-release-notes.doc#_Value___: StoreAnsiFilenames">StoreAnsiFilenames

Valid values : '0' or '1'

USEDNS

Registry key : (Service parameters)

+ href="oafw-1-4-release-notes.doc#_(Service_parameters):">(Service parameters)

Registry value : UseDNS

+ href="oafw-1-4-release-notes.doc#_Value_:_UseDNS">UseDNS

Valid values : '1' or '0'

CREDSSTARTUP

Valid values : '1' or '0'

Controls whether AFSCreds.exe starts @@ -5016,7 +5833,7 @@ releases of OpenAFS.

CREDSAUTOINIT

Valid values : '-a' or ''

Enables automatic initialization.

@@ -5024,7 +5841,7 @@ releases of OpenAFS.

CREDSIPCHDET

Valid values : '-n' or ''

Enables IP address change detection.

@@ -5032,7 +5849,7 @@ releases of OpenAFS.

CREDSQUIET

Valid values : '-q' or ''

Enables quiet mode.

@@ -5040,7 +5857,7 @@ releases of OpenAFS.

CREDSRENEWDRMAP

Valid values : '-m' or '

Enables renewing drive map at startup.

@@ -5048,7 +5865,7 @@ releases of OpenAFS.

CREDSSHOW

Valid values : '-s' or ''

Enables displaying the credential manager window when @@ -5060,12 +5877,12 @@ releases of OpenAFS.

7.2.2 Existing Registry Entries

You can change existing registry values subject to the restrictions -mentioned in the Windows Platform SDK. -Pay special attention to component key paths and try to only change the -'Value' column in the 'Registry' table. -If you want to add additional registry keys please refer to section 3 -(Additional resources).

You can change existing registry values subject to the +restrictions mentioned in the Windows Platform SDK. Pay special attention to component key paths +and try to only change the 'Value' column in the 'Registry' table. If you want to add additional registry keys +please refer to section 3 (Additional resources).

7.2.3 Replacing Configuration Files

@@ -5088,39 +5905,40 @@ here places the file in the same directory as the MSI for deployment.

The walkthrough below is to add a custom 'CellServDB' file.

1. Disable the component that contains the configuration file that you want to replace.

1.1. Locate and select the 'Component' table in the 'Tables' list.

1.2. In the Component table, locate the component you need to change ( Ctrl-F invokes the 'Find' dialog). The component names -are listed below in section 7.2.3.1.7.2.3.1. For this example, the component name is 'elf_CellServDB'.

1.3. Go to the 'Condition' column of the component.

1.4. Enter @@ -5130,25 +5948,25 @@ undefined property always evaluates to false).

Note that you can also use this step to disable other configuration files without providing replacements.

2. Add a new component containing the new configuration file.

2.1. Select the 'Component' table in the 'Tables' list.

2.2. Select 'Tables'->'Add Row' (Ctrl-R).

2.3. Enter @@ -5251,19 +6069,19 @@ 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.

3. Add a new feature to hold the new component.

3.1. Select the 'Feature' table.

3.2. Add @@ -5377,8 +6195,8 @@ a new row (Ctrl-R or 'Tables'->'Add Row') with the following values:

It is important to create the new -feature under the 'feaClient' feature, which will ensure that the configuration +

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 @@ -5386,24 +6204,24 @@ this feature from the feature selection dialog during an interactive installatio style='mso-spacerun:yes'> A value of 30 for 'Level' allows this feature to be installed by default (on a 'Typical' installation).

The 'Attributes' value is -msidbFeatureAttributesDisallowAdvertise (8), which is set on all features in -the OpenAFS MSI. The OpenAFS MSI is not designed -for an advertised installation.

The 'Attributes' value is msidbFeatureAttributesDisallowAdvertise +(8), which is set on all features in the OpenAFS MSI. The OpenAFS MSI is not designed for an +advertised installation.

4. Join the component and the feature.

4.1. Select the 'FeatureComponents' table.

4.2. Add @@ -5439,19 +6257,19 @@ a new row with the following values:

5. Add an entry to the 'File' table.

5.1. Select the 'File' table.

5.2. Add @@ -5550,22 +6368,22 @@ the MSI instead of embedding the file in it. cabinet streams.

Finally, the 'Sequence' value of -1000 will be used later to distinguish the file as being in a separate source -location than the other files in the MSI.

+1000 will be used later to distinguish the file as being in a separate source location +than the other files in the MSI.

6. Set a media source for the file.

6.1. Select the 'Media' table.

6.2. Add @@ -5604,14 +6422,14 @@ a row with the following values :

(leave other fields blank)

The sequence number of 1000 -designates this as the media source for the newly added file.

The sequence number of 1000 designates +this as the media source for the newly added file.

7.2.3.1 Components for Configuration Files

CellServDB: 'cpf_CellServDB' -(ID {D5BA4C15-DBEC-4292-91FC-B54C30F24F2A})

CellServDB: +'cpf_CellServDB' (ID {D5BA4C15-DBEC-4292-91FC-B54C30F24F2A})

7.2.4 Adding Domain Specific Registry Keys

@@ -5620,7 +6438,8 @@ Adding Domain Specific Registry Keys keys.

-Refer to Appendix A section +Refer to Appendix A section 2.1 for more information.

Columns that are @@ -5641,7 +6460,7 @@ feature and component to hold the new registry keys.

          (new row)
+ style='mso-tab-count:1'>        (new row)
            Feature            : 'feaDomainKeys'
            Feature Parent

          (new row)
-           Component        (new row)
+             Component     : 'rcm_DomainKeys'
            ComponentId : '{4E3FCBF4-8BE7-40B2-A108-C47CF743C627}'
@@ -5678,14 +6497,14 @@ feature and component to hold the new registry keys.

'FeatureComponents' - table:

+ 'FeatureComponents' table:

          (new row)
+ style='mso-tab-count:1'>        (new row)
            Feature            : 'feaDomainKeys'
            Component             Root                : 2
            Key                 : 'SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\ATHENA.MIT.EDU'
+ 2'>                 : + 'SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\ATHENA.MIT.EDU'
            Name              : 'LogonOptions'
            Value

          (new row)
+ style='mso-tab-count:1'>        (new row)
            Feature            : 'feaFreelanceKeys'
            Feature Parent

          (new row)
-           Component        (new row)
+             Component     : 'rcm_FreelanceKeys'
            ComponentId : '{4E3B3CBF4-9AE7-40C3-7B09-C48CF842C583}'
@@ -5892,7 +6712,7 @@ feature and component to hold the new registry keys.

          (new row)
+ style='mso-tab-count:1'>        (new row)
            Feature            : 'feaFreelanceKeys'
            Component -

'Registry' table:

'Registry' + table:

@@ -5928,9 +6749,8 @@ feature and component to hold the new registry keys.

2'>                 : 'SOFTWARE\OpenAFS\Client\Freelance'
            Name              : '0'
-          Value                    : +           Value              : 'athena.mit.edu#athena.mit.edu:root.cell.'
            Component     : 'rcm_FreelanceKeys'

@@ -5947,8 +6767,8 @@ feature and component to hold the new registry keys.

2'>                 : 'SOFTWARE\OpenAFS\Client\Freelance'
            Name              : '1'
-           Value                    : +             Value              : '.athena.mit.edu%athena.mit.edu:root.cell.'
            Component     : 'rcm_FreelanceKeys'

@@ -5978,8 +6798,8 @@ feature and component to hold the new registry keys.

2'>                 : 'SOFTWARE\OpenAFS\Client\Freelance\Symlinks'
            Name              : '0'
-            Value                    : +             Value              : 'athena:athena.mit.edu.'
            Component     : 'rcm_FreelanceKeys'

@@ -5996,8 +6816,8 @@ feature and component to hold the new registry keys.

2'>                 : 'SOFTWARE\OpenAFS\Client\Freelance\Symlinks'
            Name              : '1'
-           Value                    : +             Value              : '.athena:.athena.mit.edu.'
            Component     : 'rcm_FreelanceKeys'

@@ -6020,24 +6840,23 @@ new components and features for those.

It is beyond the scope of this document to provide a comprehensive overview of how to add new resources through a transform. Please refer to the "Windows -Installer" documentation for details. -The relevant section is at :

+style='mso-spacerun:yes'> Please refer to the "Windows Installer" +documentation for details. The relevant +section is at :

http://msdn.microsoft.com/library/en-us/msi/setup/using_transforms_to_add_resources.asp

A sample walkthrough of adding a new configuration file is in section 2.3.

Add new features under the 'feaClient' or 'feaServer' as -appropriate and set the 'Level' column for those features to equal the 'Level' -for their parent features for consistency. -Note that none of the features in the OpenAFS for Windows MSI package -are designed to be installed to run from 'source' or 'advertised'.Add new features under the 'feaClient' or 'feaServer' as appropriate +and set the 'Level' column for those features to equal the 'Level' for their +parent features for consistency. Note +that none of the features in the OpenAFS for Windows MSI package are designed +to be installed to run from 'source' or 'advertised'. It is recommended that you set 'msidbFeatureAttributesFavorLocal' (0), 'msidbFeatureAttributesFollowParent' -(2) and 'msidbFeatureAttributesDisallowAdvertise' (8) attributes for new -features.

+(2) and 'msidbFeatureAttributesDisallowAdvertise' (8) attributes for new features.

If you are creating new components, retain the same component GUID when creating new transforms against new releases of the OpenAFS @@ -6059,35 +6878,32 @@ command line options for MSITRAN.EXE.

7.4. Upgrades

The MSI package is designed to replace (or uninstall) -previous versions of OpenAFS for Windows during installation. Previous versions are installations that used -the NSIS (.EXE) installer or an MSI that has a known Upgrade Code and a -different Product Code. The MSI does not -directly upgrade an existing installation. -This is intentional and ensures that development releases which do not -have strictly increasing version numbers are properly upgraded.

The MSI package is designed to uninstall previous versions +of OpenAFS for Windows during installation. +Note that it doesn't directly upgrade an existing installation. This is intentional and ensures that +development releases which do not have strictly increasing version numbers are +properly upgraded.

Versions of OpenAFS that are upgraded by the MSI package -are:

Versions of OpenAFS that are upgraded by the MSI package are:

1) OpenAFS MSI package
Upgrade code {6823EEDD-84FC-4204-ABB3-A80D25779833}
-All versions regardless of Product Code

+Up to current release

2) MIT's Transarc AFS MSI package
Upgrade code {5332B94F-DE38-4927-9EAB-51F4A64193A7}
-All versions up to 3.6.2

+Up to version 3.6.2

3) OpenAFS @@ -6102,40 +6918,12 @@ style='mso-spacerun:yes'> deployments will fail on machines that have the OpenAFS NSIS package installed.

If you have used a different MSI package to install OpenAFS -and wish to upgrade it you can author rows into the 'Upgrade' table as -described in the Platform SDK.

+and wish to upgrade it you can author rows into the 'Upgrade' table as described +in the Platform SDK.

When performing an upgrade with msiexec.exe execute the MSI with the repair options "vomus".

7.4.1. OpenAFS MSI Product Codes

- -

Release 1.3

- - - - - - -

i386_w2k

{CCAF9E14-976E-46C0-8A1B-A218EAB7ADC5}

- -

Release 1.4 and later

- -

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.

Variable: IsServiceConfigured()
-
The value Cell is used to determine if the AFS Client Service - has been properly configured or not.
+
The value Cell is used to determine if the AFS Client + Service has been properly configured or not.

@@ -7312,12 +8104,13 @@ Credentials System Tray Tool parameters

Value: ShowTrayIcon

Value: + ShowTrayIcon

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 +

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].

@@ -7328,7 +8121,7 @@ Credentials System Tray Tool parameters -

Value: EnableKFW

Type: DWORD {0, 1}
Default: 1
Function: KFW_is_available()

@@ -7343,8 +8136,9 @@ Credentials System Tray Tool parameters -

Value: Use524

Value: + Use524

Type: DWORD {0, 1}
Default: 0
Function: KFW_use_krb524()

@@ -7359,13 +8153,14 @@ Credentials System Tray Tool parameters -

Value: AfscredsShortcutParams

Value: + AfscredsShortcutParams

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.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 @@ -7395,8 +8190,8 @@ Credentials System Tray Tool parameters height:92.0pt'> -

Value: Authentication - Cell

Value: + Authentication Cell

Type: REG_SZ
Default: <none>
Function: Afscreds.exe GetDefaultCell()

@@ -7417,8 +8212,8 @@ Credentials System Tray Tool parameters height:124.75pt'> -

Value: "afs cell - name"

Value: + "afs cell name"

Type: DWORD {0, 1}
Default: <none>
Function: LoadRemind(), SaveRemind()

@@ -7441,12 +8236,12 @@ Credentials System Tray Tool parameters height:98.5pt'> -

Value: "upper case - drive letter"

Value: + "upper case 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 +

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

@@ -7464,8 +8259,8 @@ Credentials System Tray Tool parameters height:98.5pt'> -

Value: "upper case - drive letter"

Value: + "upper case drive letter"

Type: REG_SZ
Default: <none>

These values are used to store @@ -7485,7 +8280,8 @@ Client Service Environment Variables mso-border-insideh:.75pt outset windowtext;mso-border-insidev:.75pt outset windowtext'> -

Variable: AFS_RPC_ENCRYPT

Variable: + AFS_RPC_ENCRYPT

Values: "OFF" disables the use of RPC encryption any other value allows RPC encryption to be used
@@ -7494,12 +8290,13 @@ Client Service Environment Variables -

Variable: AFS_RPC_PROTSEQ

Variable: + AFS_RPC_PROTSEQ

Values:            "ncalrpc" - local RPC
-                        "ncacn_np" +                         "ncacn_np" - named pipes
-                        "ncacn_ip_tcp" +                         "ncacn_ip_tcp" - tcp/ip
Default: local RPC

diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes_files/header.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes_files/header.htm index ba0bbe7eb..c1bd4e4e1 100644 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes_files/header.htm +++ b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes_files/header.htm @@ -1,8 +1,8 @@ +xmlns:st1="urn:schemas:contacts" xmlns="http://www.w3.org/TR/REC-html40"> @@ -10,9 +10,8 @@ xmlns="http://www.w3.org/TR/REC-html40"> - + name="Street"/> + name="address"/> + name="place"/> + name="PlaceType"/> + diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes_files/preview.wmf b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes_files/preview.wmf index df409e6c3..40bf0991c 100644 Binary files a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes_files/preview.wmf and b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes_files/preview.wmf differ diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/toc.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/toc.htm index 7e6b1a3bd..7a65f7d58 100644 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/toc.htm +++ b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/toc.htm @@ -15,17 +15,17 @@ xmlns="http://www.w3.org/TR/REC-html40"> Jeffrey Altman Jeffrey Altman - 2 + 1 0 - 2005-09-25T20:11:00Z - 2005-11-30T07:09:00Z + 2005-09-25T21:11:00Z + 2005-09-25T21:11:00Z 1 - 1586 - 9043 + 2360 + 13453 Secure Endpoints Inc. - 75 - 21 - 10608 + 112 + 31 + 15782 11.6568 Error! Bookmark not defined.

2. System Requirements. Error! Bookmark not defined.2. System Requirements. Error! Bookmark not defined.

2.1 Supported Operating Systems2.1 Supported Operating Systems. Error! Bookmark not defined.

2.2 Disk Space. Error! Bookmark not defined.

2.3 Additional Software2.3 Additional Software. . Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

3. Operational Notes. Error! Bookmark not defined.

3.1. Requirements for Kerberos 5 -Authentication. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417043">3.1. Requirements for Kerberos +5 AuthenticationError! Bookmark not defined.

3.2. Use of the Microsoft Loopback Adapter3.2. Use of the Microsoft +Loopback Adapter Error! Bookmark not defined.

3.3. Using Freelance (Dynamic Root) Mode to -Improve Mobility. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417045">3.3. Using Freelance (Dynamic +Root) Mode to Improve MobilityError! Bookmark not defined.

3.4. Locating AFS Volume Database Servers3.4. Locating AFS Volume +Database Servers. Error! Bookmark not defined.

3.5. Obtaining AFS Tokens as a Part of -Windows Logon. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417047">3.5. Obtaining AFS Tokens as a +Part of Windows LogonError! Bookmark not defined.

3.6. AFS System Tray Command Line Options3.6. AFS System Tray Command +Line Options. . Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

3.7. The AFS Client Admins Authorization -Group. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417049">3.7. The AFS Client Admins +Authorization GroupError! Bookmark not defined.

3.8. OpenAFS support for UNC paths3.8. OpenAFS support for UNC +paths. Error! Bookmark not defined.

3.9. OpenAFS includes aklog.exe3.9. OpenAFS includes aklog.exe. Error! Bookmark not -defined.

+text-underline:none'>. Error! Bookmark not defined.

3.10. OpenAFS Servers on Windows are -Unsupported. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417052">3.10. OpenAFS Servers on +Windows are UnsupportedError! Bookmark not defined.

3.11. OpenAFS Debugging Symbol files3.11. OpenAFS Debugging Symbol +files. . Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

3.12. Maximum File Size is 2GB3.12. Maximum File Size is 2GB.. .. Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

3.13. Encrypted AFS File Access3.13. Encrypted AFS File Access. . Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

3.14. Authenticated Access to the OpenAFS -Client Service. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417056">3.14. Authenticated Access to +the OpenAFS Client ServiceError! Bookmark not defined.

3.15. No More INI Files3.15. No More INI Files. . Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

3.16. Microsoft Windows Internet Connection -Firewall Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417058">3.16. Microsoft Windows +Internet Connection FirewallError! Bookmark not defined.

3.17. Browsing AFS from the Explorer Shell -and Office. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417059">3.17. Browsing AFS from the +Explorer Shell and OfficeError! Bookmark not defined.

3.18. Byte Range Locking3.18. Byte Range Locking. Error! Bookmark not -defined.

+text-underline:none'>. Error! Bookmark not defined.

3.19. Automatic Discarding of AFS Tokens at -Logoff. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417061">3.19. Automatic Discarding of +AFS Tokens at LogoffError! Bookmark not defined.

3.20. Terminal Server installations3.20. Terminal Server +installations. Error! Bookmark not defined.

3.21. Hidden Dot Files. Error! Bookmark not defined.3.21. Hidden Dot Files. Error! Bookmark not defined.

3.22. Status Cache Limits3.22. Status Cache Limits. Error! Bookmark not defined.

3.23. NETBIOS over TCP/IP must be enabled3.23. NETBIOS over TCP/IP must +be enabled. . Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

3.24. OpenAFS binaries are digitally signed3.24. OpenAFS binaries are +digitally signed. Error! Bookmark not defined.

3.25. Maximum Size of the AFSCache File3.25. Maximum Size of the +AFSCache File. Error! Bookmark not defined.

3.26. Filename Character Sets3.26. Filename Character Sets. Error! Bookmark not -defined.

+text-underline:none'>. Error! Bookmark not defined.

3.27. Known Character Set Issues with Roaming -Profiles. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417069">3.27. Known Character Set +Issues with Roaming ProfilesError! Bookmark not defined.

3.28. The AFSCache File3.28. The AFSCache File. Error! Bookmark not -defined.

+text-underline:none'>. Error! Bookmark not defined.

3.29. Restricting OpenAFS Client Service -Start and Stop. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417071">3.29. Restricting OpenAFS +Client Service Start and StopError! Bookmark not defined.

3.30. The @sys Name List3.30. The @sys Name List Error! Bookmark not defined.

3.31. Symlinks to AFS UNC paths3.31. Symlinks to AFS UNC paths. Error! Bookmark not defined.

3.32. Cache Manager Debugging Now Supported3.32. Cache Manager Debugging +Now Supported. Error! Bookmark not defined.

3.33. Windows Logon Caching vs. Kerberos -Logons. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417075">3.33. Windows Logon Caching vs. +Kerberos LogonsError! Bookmark not defined.

3.34. Initial Server Preferences3.34. Initial Server +Preferences. Error! Bookmark not defined.

3.35. File Timestamps. Error! Bookmark not defined.

3.36. Windows RPC client support must be -installed. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417078">3.36. Windows RPC client +support must be installedError! Bookmark not defined.

3.37. Generating Minidumps of the OpenAFS -Client Service. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417079">3.37. Generating Minidumps of +the OpenAFS Client ServiceError! Bookmark not defined.

3.38. AFS Client Universally Unique -Identifiers. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417080">3.38. AFS Client Universally +Unique IdentifiersError! Bookmark not defined.

4. How to Debug Problems with OpenAFS for -Windows: Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417081">4. How to Debug Problems with +OpenAFS for Windows:Error! Bookmark not defined.

4.1. pioctl debugging (IoctlDebug registry -key) Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417082">4.1. pioctl debugging +(IoctlDebug registry key)Error! Bookmark not defined.

4.2. afsd_service initialization log -(%WinDir%\TEMP\afsd_init.log) Error! -Bookmark not defined.4.2. afsd_service +initialization log (%WinDir%\TEMP\afsd_init.log) Error! Bookmark not defined.

4.3. afsd_service debug logs (fs trace {-on, --off, -dump} ->%WinDir%\TEMP\afsd.log) Error! Bookmark not defined.

4.4. Using SysInternals DbgView and FileMon -Tools. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417085">4.4. Using SysInternals +DbgView and FileMon ToolsError! Bookmark not defined.

4.5. Microsoft MiniDumps4.5. Microsoft MiniDumps (fs minidump -> %WinDir%\TEMP\afsd.dmp) Error! Bookmark not -defined.

+text-underline:none'> Error! Bookmark not defined.

4.6. Single Sign-on (Integrated Logon) -debugging. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417087">4.6. Single Sign-on (Integrated +Logon) debuggingError! Bookmark not defined.

4.7. RX (AFS RPC) debugging (rxdebug)4.7. RX (AFS RPC) debugging +(rxdebug) Error! Bookmark not defined.

4.8. Cache Manager debugging (cmdebug)4.8. Cache Manager debugging +(cmdebug) Error! Bookmark not defined.

4.9. Persistent Cache consistency check4.9. Persistent Cache +consistency check. Error! Bookmark not defined.

5. Reporting Bugs: Error! Bookmark not defined.

6. How to Contribute to the Development of -OpenAFS for Windows. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417092">6. How to Contribute to the +Development of OpenAFS for WindowsError! Bookmark not defined.

6.1. The USENIX OpenAFS Fund6.1. The USENIX OpenAFS Fund. . Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

6.2. Secure Endpoints Inc.6.2. Secure Endpoints Inc. Error! Bookmark not defined.

6.3. The MIT Kerberos Account6.3. The MIT Kerberos Account Error! Bookmark not defined.

6.4. Direct contributions of code and/or -documentation. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417096">6.4. Direct contributions of +code and/or documentationError! Bookmark not defined.

6.5. OpenAFS for Windows Mailing Lists6.5. OpenAFS for Windows +Mailing Lists. Error! Bookmark not defined.

7. MSI Deployment Guide7. MSI Deployment Guide. Error! Bookmark not -defined.

+text-underline:none'>. Error! Bookmark not defined.

7.1. Introduction. Error! Bookmark not defined.

7.2. Configuration Options7.2. Configuration Options. . Error! Bookmark not -defined.

+text-underline:none'>Error! Bookmark not defined.

7.3 Additional Resources7.3 Additional Resources. Error! Bookmark not defined.

7.4. Upgrades. Error! Bookmark not defined.

Appendix A: Registry ValuesAppendix A: Registry Values. Error! Bookmark not -defined.

+text-underline:none'>. Error! Bookmark not defined.

A.1. Service parametersA.1. Service parameters. Error! Bookmark not -defined.

+text-underline:none'>. Error! Bookmark not defined.

A.2. Integrated Logon Network provider -parameters. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417105">A.2. Integrated Logon Network +provider parametersError! Bookmark not defined.

A.2.1 Domain specific configuration keys for -the Network Provider Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417106">A.2.1 Domain specific +configuration keys for the Network ProviderError! Bookmark not defined.

A.3. AFS Credentials System Tray Tool -parameters. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417107">A.3. AFS Credentials System +Tray Tool parametersError! Bookmark not defined.

A.4 OpenAFS Client Service Environment -Variables. Error! Bookmark not -defined.

+href="oafw-1-4-release-notes.doc#_Toc115417108">A.4 OpenAFS Client Service +Environment VariablesError! Bookmark not defined.

XE "Kerberos 5" -3.1.1. -Active Directory +

4.1. pioctl -debugging (IoctlDebugIoctlDebug registry key)

(Service parameters):

(Network provider):

(Network + provider):

(OpenAFS Client):

(OpenAFS + Client):

7.2.3.1 Components for Configuration Files

7.4.1. OpenAFS MSI Product Codes

Release 1.3

Release 1.4 and later

Value: CacheSize

Value: + CacheSize

Value: LogoffPreserveTokens

Value: + LogoffPreserveTokens

Value: Mountroot

Value: + Mountroot

Value: CachePath

Value: + CachePath

Value: NetbiosName

Value: + NetbiosName

Value: TraceBufferSize

Value: + TraceBufferSize

Value: SysName

Value: + SysName

Value: SecurityLevel

Value: + SecurityLevel

Value: UseDNS

Value: + UseDNS

Value: FreelanceClient

Value: + FreelanceClient

Value: HideDotFiles

Value: + HideDotFiles

Value: Cell

Value: Cell

Value: RxMaxMTU

Value: + RxMaxMTU

Value: TraceOption

Value: + TraceOption

Value: NoFindLanaByName

Value: + NoFindLanaByName

XE "Kerberos 5"
-
3.1.1. -Active Directory
+

4.1. pioctl -debugging (IoctlDebug IoctlDebug registry key)