From 06fe869a7c14875e410d476890c0a97b0ae93d68 Mon Sep 17 00:00:00 2001 From: Jeffrey Altman Date: Tue, 27 Sep 2005 01:44:35 +0000 Subject: [PATCH] STABLE14-windows-release-notes-20050926 Document MSI Product Codes (cherry picked from commit 1512b602134bf46d78671628e438a5b7f9155524) --- .../en_US/html/ReleaseNotes/relnotes.htm | 3350 +++++++---------- .../ReleaseNotes/relnotes_files/header.htm | 14 +- .../ReleaseNotes/relnotes_files/preview.wmf | Bin 15892 -> 15482 bytes 3 files changed, 1291 insertions(+), 2073 deletions(-) diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes.htm index 1b5128fdf..7465239a4 100644 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes.htm +++ b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/relnotes.htm @@ -1,8 +1,8 @@ +xmlns="http://www.w3.org/TR/REC-html40"> @@ -12,8 +12,9 @@ xmlns:st1="urn:schemas:contacts" xmlns="http://www.w3.org/TR/REC-html40"> OpenAFS for Windows 1.4.0 Release Notes + + name="address"/> + name="Street"/> + name="PlaceType"/> - + name="place"/> 1. +class=MsoHyperlink>1. Installer Options. PAGEREF _Toc115417109 \h 1

+mso-no-proof:yes'>

2. -System Requirements. . 2

+mso-no-proof:yes'>

3. -Operational Notes. . 2

+mso-no-proof:yes'>

4. -How to Debug Problems with OpenAFS for Windows: PAGEREF +_Toc115417112 \h 11

+mso-no-proof:yes'>

5. -Reporting Bugs: 13

+mso-no-proof:yes'>

6. -How to Contribute to the Development of OpenAFS for Windows. PAGEREF +_Toc115417114 \h 14

+mso-no-proof:yes'>

7. -MSI Deployment Guide. . 15

+mso-no-proof:yes'>

Appendix -A: Registry Values. . 26

+mso-no-proof:yes'>

1. Installer Options

+style='mso-element:field-end'>1. Installer Options

It can be installed either as a new installation or an upgrade from previous versions of OpenAFS for Windows or IBM AFS for Windows.  Installers are provided in two forms:

-

1.        an executable (.exe) that is built using the Nullsoft Scriptable Installation System, or

-

2.        a Windows Installer package (.msi) that is built using WiX and can be customized for organizations via the use of MSI Transforms -(see MSI -Deployment Guide)

+(see MSI Deployment Guide)

-

2. System Requirements

+

2. System Requirements

-

2.1 Supported +

2.1 Supported Operating Systems

·       Microsoft Windows 2000 Workstation

·       Microsoft Windows 2000 Server

·       Microsoft Windows XP Home

·       Microsoft Windows XP Professional

·       Microsoft Windows 2003 Server

·       Microsoft Windows 2003 R2 Server

-

2.1.1 Unsupported -Operating Systems

+

2.1.1 +Unsupported Operating Systems

·       Microsoft Windows 95

·       Microsoft Windows 98

·       Microsoft Windows 98 OSR2

·       Microsoft Windows ME

·       Microsoft NT

·       Microsoft Windows Vista (as of Beta 1 bugs in Windows prevent its use)

·       All @@ -3567,26 +2777,26 @@ those operating systems must be supported. style='mso-spacerun:yes'>  The last version with support for Windows NT 4.0 is 1.2.10.

-

2.2 Disk Space

+

2.2 Disk Space

Up to 60mb required for the OpenAFS binaries plus 100MB for the default AFSCache file.   (The size of the AFSCache file may be adjusted via the Registry after installation.)

-

2.3 Additional +

2.3 Additional Software

MIT Kerberos for Windows 2.6.x if Kerberos 5 authentication support is desired.

-

3. Operational Notes

+

3. Operational Notes

-

3.1. Requirements +

3.1. Requirements for Kerberos 5 Authentication

The Kerberos 4 infrastructure on which the OpenAFS 1.2 @@ -3610,8 +2820,8 @@ Transarc servers do not support Kerberos 5.

-

3.1.1. Active -Directory

+

3.1.1. +Active Directory

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

-

3.1.2. Using -the krb524 service

+

3.1.2. +Using the krb524 service

Some organizations which have AFS cell names and Kerberos realm names which differ by more then just lower and upper case rely on a @@ -3660,18 +2870,18 @@ a win in all situations except when the cell name does not match the realm name and the principal names placed into the ACL’s 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.

-

3.2. Use of the +

3.2. Use of the Microsoft Loopback Adapter

By itself the OpenAFS Client Service does not provide robust @@ -3695,19 +2905,19 @@ 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 name "AFS" and the name of the machine on the MLA's IP Address that 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:

+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:

·        stop the AFS Client Service

·       Networks" to the MLA

·       Microsoft Networks" from the MLA

·        Disable and then re-enable the MLA

·      

When the MLA is not installed the unique NETBIOS name published by OpenAFS SMB server is "MACHINE-AFS".  One of the benefits of using the MLA is that -the NETBIOS name does not have to be published on any adapter other than the -MLA.  Therefore the chosen name is no -longer required to be unique.  Instead -the NETBIOS name associated with the AFS Client Service is simply -"AFS" and portable UNC paths of the form \\AFS\cellname\path can now -be used on all machines.

-

3.3. Using +

3.3. Using Freelance (Dynamic Root) Mode to Improve Mobility

Traditionally, when the OpenAFS Client Service starts it must be able to access the "root.afs" volume of the default cell.  The "root.afs" volume contains the set of mount points to the "root.cell" volumes of -various cells the administrator of the default cell believes should be accessible.  If the "root.afs" volume is -inaccessible when the client service is started, the service will terminate -unexpectedly.  Since many users now use -laptops or otherwise operate in disconnected environments in which a VPN may be -required to access the cell's servers, it is often the case that the +various cells the administrator of the default cell believes should be +accessible.  If the "root.afs" +volume is inaccessible when the client service is started, the service will +terminate unexpectedly.  Since many users +now use laptops or otherwise operate in disconnected environments in which a +VPN may be required to access the cell's servers, it is often the case that the "root.afs" volume for the default cell is not reachable and the OpenAFS Client Service will not successfully start.

To allow the OpenAFS Client Service to operate in these environments, a fake "root.afs" volume is dynamically constructed from mount points and symlinks stored in the local registry.  This method of operation is referred to as -Freelance mode.

+style='mso-spacerun:yes'>  This method of operation is referred to as Freelance +mode.

The content of the fake “root.afs” volume is dynamically modified as cells are accessed.  When the @@ -3805,14 +3015,13 @@ points may be removed using the "fs rmmount" command.

>fs rmmount \\AFS\athena.mit.edu

-

>fs rmmount -\\AFS\.athena.mit.edu

+

>fs rmmount \\AFS\.athena.mit.edu

Symlinks may also be created within the Freelance “root.afs” volume.

-

>symlink make \\afs\link -\\afs\athena.mit.edu\user\j\a\jaltman

+

>symlink make +\\afs\link \\afs\athena.mit.edu\user\j\a\jaltman

      >symlink list \\afs\link

@@ -3842,21 +3051,22 @@ style='mso-spacerun:yes'> style='mso-element:field-end'> 

-

3.4. Locating AFS +

3.4. Locating AFS Volume Database Servers

The OpenAFS for Windows client will use DNS AFSDB records to -discover the location of AFS Volume Database servers when entries are not present -in the client's CellServDB file (\%PROGRAMFILES%\OpenAFS\Client\CellServDB).

-

3.5. Obtaining +

3.5. Obtaining AFS Tokens as a Part of Windows Logon

OpenAFS for Windows installs a WinLogon Network Provider to @@ -3868,14 +3078,14 @@ 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.

+style='mso-spacerun:yes'>  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.

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.

+style='mso-spacerun:yes'>  OpenAFS does not provide tools for +synchronizing the Windows and Kerberos user accounts and passwords.

When KFW is configured, Integrated Logon will use it to obtain tokens.  The Kerberos 5 tickets @@ -3890,13 +3100,12 @@ Kerberos KDC is inaccessible at logon time.

multiple cells.  For further information on how to configure this feature read the TheseCells value in Appendix -A.

-

3.6. AFS System +

3.6. AFS System Tray Command Line Options

The AFS System Tray tool (afscreds.exe) supports several @@ -3955,15 +3164,13 @@ 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.

-

3.7. The “AFS +

3.7. The “AFS Client Admins” Authorization Group

The OpenAFS for Windows 1.4 client supports a local Windows @@ -3976,76 +3183,76 @@ following fs.exe commands are now restricted to members of the "AFS Client Admins" group:

·       checkservers with a non-zero timer value

·       setcachesize

·       newcell

·       sysname with a new sysname list

·       exportafs

·       setcell

·       setserverprefs

·       storebehind

·       setcrypt

·       cscpolicy

·       trace

-

The creation or removal of mount points and symlinks in the -Freelance “root.afs” volume are also restricted to members of the “AFS Client -Admins” group.

+

The creation or removal of mount points and symlinks in the Freelance +“root.afs” volume are also restricted to members of the “AFS Client Admins” +group.

The initial membership of the "AFS Client Admins" group when created by the installer is equivalent to the local @@ -4059,17 +3266,16 @@ Administrators. Admins" group.

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

-

3.8. OpenAFS +

3.8. OpenAFS support for UNC paths

The OpenAFS 1.4 client supports UNC paths everywhere. XE "4nt.exe"

-

3.9. OpenAFS +

3.9. OpenAFS includes aklog.exe

The OpenAFS 1.4 Client ships with its own version of @@ -4124,8 +3330,8 @@ tokens

 

-

   -d = output -debugging information.

+

   -d = output debugging information.

   cell = zero or more cells for which tokens will be obtained

@@ -4139,16 +3345,17 @@ the directory for which authentication is required

   -noprdb = don't try to determine AFS ID.

-

   -5 or -4 = -use Kerberos V (default) or Kerberos IV tickets

+

   -5 or -4 = use Kerberos V (default) or +Kerberos IV tickets

   -m = use krb524d to convert Kerberos V tickets to Kerberos IV

-

3.10. OpenAFS +

3.10. OpenAFS Servers on Windows are Unsupported

The AFS Server functionality provided with OpenAFS 1.4 might @@ -4161,7 +3368,7 @@ should not be stored in an OpenAFS Server on Windows.

going to be used with the OpenAFS AFS Server:

·       When @@ -4170,7 +3377,7 @@ off. manipulate the contents of the root.afs volume for the hosted cell.

·       The @@ -4180,8 +3387,8 @@ MIT Kerberos for Windows should not be installed or must be disabled.

-

3.11. OpenAFS +

3.11. OpenAFS Debugging Symbol files

The OpenAFS for Windows installers now include Debugging @@ -4192,21 +3399,21 @@ style='mso-spacerun:yes'> versions are:

·       whether or not the binaries were compiled with optimization

·       whether the debug symbols are installed by default

·       whether @@ -4214,8 +3421,8 @@ additional debug statements were compiled into the binaries

-

3.12. Maximum +

3.12. Maximum File Size is 2GB

OpenAFS for Windows does not support files larger than @@ -4226,8 +3433,8 @@ Installable File System will allow larger files to be supported.

-

3.13. Encrypted +

3.13. Encrypted AFS File Access

The OpenAFS for Windows installer by default activates a @@ -4235,9 +3442,9 @@ weak form of encrypted data transfer between the AFS client and the AFS servers.  This is often referred to as "fcrypt" mode.

-

3.14. -Authenticated Access to the OpenAFS Client Service

+

3.14. Authenticated +Access to the OpenAFS Client Service

OpenAFS 1.4 supports authenticated SMB connections using either NTLM or GSS SPNEGO (NTLM).  In @@ -4258,21 +3465,20 @@ authentication mode will be used that does not require access to the user's password.  Instead, Windows will internally recognize the request as coming from a local logon session.

-

3.15. No More INI +

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.

+(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 @@ -4280,20 +3486,20 @@ file to the new CellServDB file. Windows registry.   OpenAFS 1.4 will not process the contents of the “afsddbmt.ini”.

-

3.16. Microsoft +

3.16. Microsoft Windows Internet Connection Firewall

-

The OpenAFS 1.4 Client is compatible with the Internet Connection -Firewall that debuted with Windows XP SP2 and Windows 2003 SP1.The OpenAFS 1.4 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 adjusted to allow the receipt of incoming callback messages from the AFS file server.  In addition, the appropriate Back Connection registry entries are added to allow SMB authentication to be performed across the Microsoft Loopback Adapter.

-

3.17. Browsing +

3.17. Browsing AFS from the Explorer Shell and Office

The OpenAFS 1.4 Client Service implements the CIFS Remote @@ -4313,33 +3519,31 @@ Locking

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.   OpenAFS does not currently support byte -range locks.   It is strongly recommended -that files not be edited within AFS if they might be accessed by multiple users -or multiple processes on a single machine.

+style='mso-spacerun:yes'>   OpenAFS does not currently support byte range +locks.   It is strongly recommended that +files not be edited within AFS if they might be accessed by multiple users or +multiple processes on a single machine.

-

3.19. Automatic +

3.19. Automatic 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.

+determine when the profile has been successfully written back to the network.  It is therefore unsafe to release the user's +tokens.  Whether or not the profile has +been loaded from the registry can be determined for Local Accounts, Active +Directory accounts and NT4 accounts.

If there is a need to disable this functionality, the LogoffPreserveTokens -registry value can be used. (see Appendix +style='mso-bidi-font-style:italic'>LogoffPreserveTokens +registry value can be used. (see Appendix A.)

-

3.20. Terminal +

3.20. Terminal Server installations

When installing the NSIS (.exe) installer under Terminal @@ -4348,8 +3552,8 @@ Panel. AFS not running properly.  The AFS Server should not be installed on a machine with Terminal Server installed.

-

3.21. Hidden Dot +

3.21. Hidden Dot Files

AFS is a UNIX native file system. automatically given the Hidden attribute so they will not normally be displayed.

-

3.22. Status +

3.22. Status Cache Limits

The Status Cache (AFS Configuration Control Panel: Advanced @@ -4371,16 +3575,16 @@ style='mso-spacerun:yes'> 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.

+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.  Each entry requires approximately 1.2K.  In OpenAFS 1.4, the default number of Status Cache entries is 10,000.

-

3.23. NETBIOS +

3.23. NETBIOS over TCP/IP must be enabled

"Netbios over TCP/IP" must be active on the @@ -4389,8 +3593,8 @@ style='mso-spacerun:yes'> disabled on the machine, then communication with the AFS Client Service will be impossible.

-

3.24. OpenAFS +

3.24. OpenAFS binaries are digitally signed

The OpenAFS Client Service and related binaries distributed @@ -4405,15 +3609,13 @@ hours of support time have been wasted tracking down problems caused by the mixture of files from different releases. 

-

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.

-

3.25. Maximum +

3.25. Maximum Size of the AFSCache File

The maximum cache size is approximately 1.3GB. -

3.26. Filename +

3.26. Filename Character Sets

OpenAFS for Windows implements an SMB server which is used @@ -4483,11 +3685,11 @@ characters:

08/06  206  86  a ring

-

     [ç]  135  - 08/07  207  87  c - cedilla

+

     [ç]  + 135  08/07  207  + 87  c cedilla

     [ê]  136  08/08  210 style='mso-spacerun:yes'>  92  AE diphthong

     [ô]  147  - 09/03  223  93  o - circumflex

+ style='mso-spacerun:yes'>  147  09/03  + 223  93  o circumflex

     [ö]  148  09/04  224 diaeresis

     [ò]  149  - 09/05  225  95  o + 09/05  225  95  o grave

     [û]  150  @@ -4615,16 +3817,16 @@ 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.

- -

3.27. Known +href="#_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 @@ -4636,8 +3838,8 @@ support UNICODE. some sites run logoff scripts (assigned by group policy) which rename all files to use only the supported characters for the locale.

-

3.28. The +

3.28. The AFSCache File

The AFS Cache file is stored by default at %TEMP%\AFSCache @@ -4655,8 +3857,8 @@ compressed and should consist of as few fragments as possible.   Significant performance gains can be achieved by defragmenting the AFSCache file with Sysinternal's Contig utility.

-

3.29. Restricting +

3.29. Restricting OpenAFS Client Service Start and Stop

A new command line tool, afsdacl.exe, can be used to @@ -4673,9 +3875,8 @@ afsd service by any ordinary user.

    Usage : afsdacl [-set | -reset] [-show]

-

          -set   -: Sets the DACL

+

          +-set   : Sets the DACL

          -reset : Reset the DACL

@@ -4683,8 +3884,8 @@ style='mso-spacerun:yes'>

          -show  : Show current DACL (SDSF)

-

3.30. The @sys +

3.30. The @sys Name List

The default @sys name list in OpenAFS 1.4 is set to @@ -4693,16 +3894,17 @@ style='mso-spacerun:yes'> "ia64_win64" and "amd64_win64" for amd 64-bit processors when those platforms are supported.

-

3.31. Symlinks to +

3.31. Symlinks to AFS UNC paths

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.

+However, please use /afs/... as the Windows UNC form will not work on +UNIX.

-

3.32. Cache +

3.32. Cache Manager Debugging Now Supported

OpenAFS for Windows 1.4 implements the Cache Manager @@ -4718,37 +3920,35 @@ can be queried with cmdebug.exe.

Where: -long   print all info

-

       --addrs  print only host interfaces

+

       -addrs  print only host interfaces

       -cache  print only cache configuration

-

3.33. Windows +

3.33. Windows Logon Caching vs. Kerberos Logons

If you are a site which utilizes MIT/Heimdal Kerberos -principals to logon to Windows via a cross-realm relationship with a -multi-domain Windows forest, you must enable Windows logon caching unless the -workstation is Windows Vista Beta 1 or later.

+principals to logon to Windows via a cross-realm relationship with a multi-domain +Windows forest, you must enable Windows logon caching unless the workstation is +Windows Vista Beta 1 or later.

-

3.34. Initial +

3.34. Initial Server Preferences

VLDB and File Server Preferences can now be provided initial values using registry keys.  This is useful for managed machines in a Windows domain which are centrally located (e.g., in a computing lab.)  See Appendix -A for details on the "Server -Preferences" keys.

+href="#_Appendix_A:_Registry_Values">Appendix A for details on the "Server Preferences" keys.

-

3.35. File +

3.35. File Timestamps

OpenAFS 1.4 reports timestamps on files stored in AFS in UTC @@ -4767,14 +3967,14 @@ AFS had changed.

It should be noted that UNIX based operating systems (such as Solaris) do not appear to report file times to applications in UTC.  They do preserve the relative local -time.  This may confuse some users who are -used to being able to compare the timestamp in an UNIX shell with the timestamp -from the Windows explorer.  During DST, -these two times will no longer agree even though they are in fact representing -the same moment in time.

- -

3.36. Windows RPC +time.  This may confuse some users who +are used to being able to compare the timestamp in an UNIX shell with the +timestamp from the Windows explorer.  +During DST, these two times will no longer agree even though they are in +fact representing the same moment in time.

+ +

3.36. Windows RPC client support must be installed

If the installer refuses to install and complains about an @@ -4793,8 +3993,8 @@ are present and that they refer to the dll "rpcrt4.dll":

   HKLM "SOFTWARE\Microsoft\RPC\ClientProtocols" "ncacn_http"

-

3.37. Generating +

3.37. Generating Minidumps of the OpenAFS Client Service

OpenAFS 1.4 adds a new command, "fs @@ -4804,8 +4004,8 @@ afsd_service.exe process. can be very helpful when debugging the AFS Client Service when it is unresponsive to SMB/CIFS requests.

-

3.38. AFS Client +

3.38. AFS Client Universally Unique Identifiers

The OpenAFS for Windows 1.4 client implements Universally @@ -4819,9 +4019,9 @@ style='mso-spacerun:yes'> client installed, the AFSCache files must be deleted as part of the cloning process.

-

4. How to Debug +

4. How to Debug Problems with OpenAFS for Windows:

OpenAFS for Windows provides a wide range of tools to assist @@ -4829,13 +4029,12 @@ you in debugging problems. 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 +

4.1. pioctl +debugging (IoctlDebug registry key)

pioctl (path-based ioctl) calls are used by various tools to @@ -4843,7 +4042,7 @@ communicate with the AFS Client Service. Some of the operations performed include:

·       setting/querying @@ -4851,49 +4050,49 @@ tokens afscreds.exe)

·       setting/querying ACLs

·       setting/querying cache parameters

·       flushing files or volumes

·       setting/querying server preferences

·       querying path location

·       checking the status of servers and volumes

·       setting/querying @@ -4924,8 +4123,8 @@ style='mso-spacerun:yes'> KnowledgeBase can be used as a reference to help you determine the configuration probem with your system.

-

4.2. afsd_service +

4.2. afsd_service initialization log (%WinDir%\TEMP\afsd_init.log)

Every time the AFS Client Service starts it appends data @@ -4941,15 +4140,15 @@ 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.  If value is set to 0, the file -will be allowed to grow indefinitely.

- -

4.3. afsd_service +href="#_Value___:_MaxLogSize">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.

+ +

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

When attempting to debug the behavior of the SMB/CIFS Server @@ -4958,12 +4157,9 @@ being performed. Client Service keeps an in memory log of many of its actions.   The default number of actions preserved at any one time is 5000.  This can be -adjusted with the registry -value:

+adjusted with the registry value:

-

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

+

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

  REG_DWORD  TraceBufferSize

@@ -4973,22 +4169,19 @@ value. to clear to the log and "fs trace -dump" to output the contents of the log to the file.

-

4.4. Using +

4.4. Using SysInternal’s DbgView and FileMon Tools

-

An alternatve option to the use of "fs trace -dump" -to capture internal OpenAFS Client Service events is to use a tool such as -Sysinternal's DbgView to capture real-time debugging output.  When the OpenAFS Client Service starts and Bit -2 of the TraceOption -value in the registry is set, all trace log events are output using the Windows -Debug Monitor interface (OutputDebugString).  -

+

An alternatve option to the use of "fs trace +-dump" to capture internal OpenAFS Client Service events is to use a tool +such as Sysinternal's DbgView to capture real-time debugging output.  When the OpenAFS Client Service starts and +Bit 2 of the TraceOption value in the +registry is set, all trace log events are output using the Windows Debug +Monitor interface (OutputDebugString). 

-

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

+

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

REG_DWORD   TraceOption = 0x04

@@ -4999,8 +4192,8 @@ generation of log messages.

Sysinternal’s FileMon utility can be use to monitor the file operations requested by applications and their success or failure.   Restrict FileMon to monitor Network Volumes -only in order to reduce the output to just the CIFS requests.   

+only in order to reduce the output to just the CIFS requests.  

Turn on the Clock Time option in both tools to make it easier to synchronize the application requests @@ -5008,8 +4201,8 @@ and the resulting OpenAFS Client Service operations.   The captured data can be stored to files for inclusion in bug reports.

-

4.5. Microsoft +

4.5. Microsoft MiniDumps
(fs minidump -> %WinDir%\TEMP\afsd.dmp)

@@ -5020,15 +4213,14 @@ with access to the source code and a debugger. of a MiniDump file containing the state of all of the threads in the AFS Client Service process.

-

4.6. Single +

4.6. Single Sign-on (Integrated Logon) debugging

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:

+href="#_Value__:_TraceOption">TraceOption registry value:

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

@@ -5040,8 +4232,8 @@ registry value:

Event Handlers to log information to the Windows Event Log: Application under the name “AFS Logon".

-

4.7. RX (AFS RPC) +

4.7. RX (AFS RPC) debugging (rxdebug)

The rxdebug.exe tool can be used to query a variety of @@ -5099,8 +4291,8 @@ connections

       -peers           show peers

-

4.8. Cache +

4.8. Cache Manager debugging (cmdebug)

The cmdebug.exe tool can be used to query the state of the @@ -5116,9 +4308,9 @@ style='mso-spacerun:yes'>

Where: -long       print all info

-

       --refcounts  print only cache -entries with positive reference counts

+

       -refcounts  +print only cache entries with positive reference counts

       -callbacks  print only cache @@ -5132,8 +4324,8 @@ interfaces

-cache      print only cache configuration

-

4.9. Persistent +

4.9. Persistent Cache consistency check

The persistent cache is stored in a Hidden System file at @@ -5141,12 +4333,12 @@ Cache consistency check

problem with the persistent cache that prevent the AFS Client Service from being able to start a validation check on the file can be performed.

-

  -afsd_service.exe --validate-cache <cache-path>

+

  afsd_service.exe +--validate-cache <cache-path>

-

5. Reporting Bugs:

+

5. Reporting Bugs:

Bug reports should be sent to openafs-bugs@openafs.org.

Configuring DrWatson to generate dump files for crashes:

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

·       click Start > Run... 

·       type drwtsn32 <enter>.

·       Select either a Crash Dump Type: Mini or Full.

·       Clear Dump Symbol Table

·       Clear Append to Existing Log file.

·       Check Dump All Thread Contexts.

·       Check Create Crash Dump File

·       Next run the monitoring module of Dr. Watson:

·       click Start > Run...

·       type drwatson <enter>.

·       Once @@ -5255,9 +4447,9 @@ them and attach them to your e-mail.

When reporting a error, please be sure to include the version of OpenAFS.

-

6. How to Contribute to +

6. How to Contribute to the Development of OpenAFS for Windows

Contributions to the development of OpenAFS for Windows are @@ -5265,19 +4457,19 @@ continuously needed. take many forms including cash donations, support contracts, donated developer time, and even donated tech writer time.

-

6.1. The USENIX +

6.1. The USENIX OpenAFS Fund

USENIX, a 501c3 non-profit corporation, has formed the USENIX OpenAFS Fund in order to accept tax deductible donations on behalf of the OpenAFS Elders. The donated funds -will be allocated by the OpenAFS Elders to fund OpenAFS development, -documentation, project management, and maintaining openafs.org.

+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-anchor-horizontal: +column;mso-element-left:.05pt;mso-element-top:372.8pt;mso-height-rule:exactly'> @@ -5285,7 +4477,8 @@ mso-element-top:372.8pt'> 9.0pt;padding-bottom:0pt;padding-left:9.0pt'>

USENIX OpenAFS Fund
+ mso-element-anchor-horizontal:column;mso-element-left:.05pt;mso-element-top: + 372.8pt;mso-height-rule:exactly'>USENIX OpenAFS Fund
USENIX Association
2560 Ninth St., Suite 215
@@ -5304,55 +4497,51 @@ mso-element-top:372.8pt'> 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'>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

@@ -5378,21 +4567,21 @@ name="_Toc115417098">7. MSI -Deployment Guide +style='mso-bookmark:_Toc115417098'>7. +MSI Deployment Guide

-

7.1. Introduction

+

7.1. Introduction

A MSI installer option is available for those who wish to use Windows Installer for installing OpenAFS and for organizations that wish to @@ -5412,15 +4601,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.

@@ -5447,8 +4636,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

-

and then checking the resulting openafs-test.msi to see if -all changes you have made above to openafs-modified.msi is present in +

and then checking the resulting openafs-test.msi to see if all +changes you have made above to openafs-modified.msi is present in openafs-test.msi.  'msitran' will complain if some modification in the transform can not be successfully applied.

@@ -5505,19 +4694,18 @@ complain if some modification in the transform can not be successfully applied.< the MSI databases directly when editing openafs-modified.msi.  More details are given below.

-

7.2. Configuration -Options

+

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

@@ -5535,12 +4723,11 @@ 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 +referenced by the same text used in Appendix A.

Strings are quoted using single quotes (e.g. 'a string'). An @@ -5554,14 +4741,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.        @@ -5569,7 +4756,7 @@ style='font:7.0pt "Times New Roman"'>        tables on the left.

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

4.        @@ -5592,28 +4779,24 @@ desired value.

mso-border-insideh:.75pt outset windowtext;mso-border-insidev:.75pt outset windowtext'>
-
(Service parameters):
-

[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\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]
@@ -5628,10 +4811,9 @@ entries associated with OpenAFS for Windows.

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

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

Registry value : CachePath

@@ -5641,22 +4823,19 @@ entries associated with OpenAFS for Windows.

-
AFSCACHESIZE
+
AFSCACHESIZE

Registry key    : (Service - parameters)

-

Registry value : CacheSize

+ href="#_(Service_parameters):">(Service parameters)

+

Registry value : CacheSize

Valid values    : numeric

-
AFSCELLNAME
+
AFSCELLNAME

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : Cell

Valid values    : @@ -5665,10 +4844,9 @@ entries associated with OpenAFS for Windows.

-
FREELANCEMODE
+
FREELANCEMODE

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : FreelanceClient

Valid values    : '1' @@ -5677,10 +4855,9 @@ entries associated with OpenAFS for Windows.

-
HIDEDOTFILES
+
HIDEDOTFILES

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : HideDotFiles

Valid values    : '1' @@ -5689,28 +4866,23 @@ entries associated with OpenAFS for Windows.

-
LOGONOPTIONS
+
LOGONOPTIONS

Registry key    : (Network - provider)

+ href="#_(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="#_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
+
MOUNTROOT

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : Mountroot

Valid values    : @@ -5719,34 +4891,31 @@ entries associated with OpenAFS for Windows.

-
NETBIOSNAME
+
NETBIOSNAME

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : NetbiosName

+ href="#_Value___:_NetbiosName">NetbiosName

Valid values    : string (at most 15 characters)

-
NOFINDLANABYNAME
+
NOFINDLANABYNAME

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : NoFindLanaByName

+ href="#_Value___:_NoFindLanaByName">NoFindLanaByName

Valid values    : '1' or '0'

-
RXMAXMTU
+
RXMAXMTU

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : RxMaxMTU

Valid values    : @@ -5755,10 +4924,9 @@ entries associated with OpenAFS for Windows.

-
SECURITYLEVEL
+
SECURITYLEVEL

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : SecurityLevel

Valid values    : '1' @@ -5767,34 +4935,31 @@ entries associated with OpenAFS for Windows.

-
SMBAUTHTYPE
+
SMBAUTHTYPE

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : SMBAuthType

+ href="#_Value___:_smbAuthType">SMBAuthType

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

-
STOREANSIFILENAMES
+
STOREANSIFILENAMES

Registry key    : (OpenAFS - Client)

+ href="#_(OpenAFS_Client):">(OpenAFS Client)

Registry value : StoreAnsiFilenames

-

Valid values    : '0' or - '1'

+ href="#_Value___:_StoreAnsiFilenames">StoreAnsiFilenames

+

Valid values    : '0' + or '1'

-
USEDNS
+
USEDNS

Registry key    : (Service - parameters)

+ href="#_(Service_parameters):">(Service parameters)

Registry value : UseDNS

Valid values    : '1' @@ -5820,9 +4985,10 @@ including such options may not apply to future releases of OpenAFS.

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

Valid values    : '1' or '0'

+ style='mso-spacerun:yes'>    : + '1' or '0'

Controls whether AFSCreds.exe starts up automatically when the user logs on.  When CREDSSTARTUP is '1' a shortcut is added to the 'Startup' folder @@ -5832,7 +4998,7 @@ including such options may not apply to future releases of OpenAFS.

-
CREDSAUTOINIT
+
CREDSAUTOINIT

Valid values    : '-a' or ''

Enables automatic initialization.

@@ -5840,7 +5006,7 @@ including such options may not apply to future releases of OpenAFS.

-
CREDSIPCHDET
+
CREDSIPCHDET

Valid values    : '-n' or ''

Enables IP address change detection.

@@ -5848,7 +5014,7 @@ including such options may not apply to future releases of OpenAFS.

-
CREDSQUIET
+
CREDSQUIET

Valid values    : '-q' or ''

Enables quiet mode.

@@ -5856,7 +5022,7 @@ including such options may not apply to future releases of OpenAFS.

-
CREDSRENEWDRMAP
+
CREDSRENEWDRMAP

Valid values    : '-m' or '’

Enables renewing drive map at startup.

@@ -5864,7 +5030,7 @@ including such options may not apply to future releases of OpenAFS.

-
CREDSSHOW
+
CREDSSHOW

Valid values    : '-s' or ''

Enables displaying the credential manager window when @@ -5904,40 +5070,39 @@ 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 @@ -5947,25 +5112,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 @@ -6068,19 +5233,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 @@ -6194,8 +5359,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 @@ -6203,24 +5368,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 @@ -6256,19 +5421,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 @@ -6367,22 +5532,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 @@ -6424,11 +5589,11 @@ style='mso-spacerun:yes'>

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

@@ -6437,9 +5602,8 @@ Adding Domain Specific Registry Keys

keys.

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

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

    Columns that are unspecified should be left empty.

@@ -6459,7 +5623,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}'
@@ -6497,14 +5660,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            Root                : 2
            Key                 : 'SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST'
+ 2'>                 : + 'SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST'
            Name              : 'FailLoginsSilently'
            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}'
@@ -6711,7 +5874,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:

@@ -6748,8 +5910,9 @@ 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'

@@ -6766,9 +5929,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'

@@ -6798,8 +5960,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'

@@ -6816,8 +5978,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'

@@ -6829,9 +5991,9 @@ feature and component to hold the new registry keys.

athena.mit.edu cell's root.afs volume as well as a read-write mountpoint.  Aliases are also provided using symlinks.

-

7.3 Additional +

7.3 Additional Resources

If you want to add registry keys or files you need to create @@ -6849,21 +6011,22 @@ Installer" documentation for details.

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 MSI package.

-

After making the adjustments to the MSI database using ORCA.EXE -you can generate a transform with MSITRAN.EXE as follows :

+

After making the adjustments to the MSI database using +ORCA.EXE you can generate a transform with MSITRAN.EXE as follows :

(Modified MSI package is 'openafs-en_US_new.msi' and the original MSI package is 'openafs-en_US.msi'.  @@ -6875,35 +6038,38 @@ original MSI package is 'openafs-en_US.msi'.

See the Platform SDK documentation for information on command line options for MSITRAN.EXE.

-

7.4. Upgrades

+

7.4. Upgrades

-

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.

+

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.

-

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}
-Up to current release

+All versions regardless of Product Code

-

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

+All versions up to 3.6.2

-

3)      OpenAFS @@ -6914,16 +6080,101 @@ All versions

1.3.65 had a bug where it couldn't be uninstalled properly in unattended mode.  Therefore the MSI package will not try to uninstall an OpenAFS NSIS package if running unattended.  This means that group policy based deployments -will fail on machines that have the OpenAFS NSIS package installed.

+style='mso-spacerun:yes'>  This means that group policy based +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

+ + + + + + + + + + +
+

amd64_w2k  

+ 		+

{CC59770C-4690-4531-BAEB-55A5A6D2EEB9}

+
+

i386_w2k   

+ 		+

{B2220B3E-B61D-4CC7-9D4B-17BA918D049C}

+
+ +

Release 1.5

+ + + + + + + + + + +
+

amd64_w2k  

+ 		+

{A0A7B986-CF35-499C-9400-9A987F218127}

+
+

i386_w2k   

+ 		+

{E832F832-C937-46BC-8C1D-BC7EF6F3F62F}

+
+

Appendix A: Registry Values

-

A.1. Service +

A.1. Service parameters

The service parameters primarily affect the behavior of @@ -6948,14 +6199,13 @@ the AFS client service (afsd_service.exe).

-

Value: - LANadapter
+
Value: LANadapter

Type: DWORD
Default: -1
Variable: LANadapter

LAN adapter number to use.  This is the lana number of the LAN adapter - that the SMB server should bind to.  If + style='mso-spacerun:yes'>  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. -

Value: - CacheSize
+
Value: CacheSize

Type: DWORD
Default: 98304 (CM_CONFIGDEFAULT_CACHESIZE)
Variable: cm_initParams.cacheSize

@@ -6980,7 +6229,7 @@ the AFS client service (afsd_service.exe).

-
Value: ChunkSize
+
Value: ChunkSize

Type: DWORD
Default: 17 (CM_CONFIGDEFAULT_CHUNKSIZE)
Variable: cm_logChunkSize (cm_chunkSize = 1 << cm_logChunkSize)

@@ -6991,7 +6240,7 @@ the AFS client service (afsd_service.exe).

-
Value: Daemons
+
Value: Daemons

Type: DWORD
Default: 2 (CM_CONFIGDEFAULT_DAEMONS)
Variable: numBkgD

@@ -7002,7 +6251,7 @@ the AFS client service (afsd_service.exe).

-
Value: ServerThreads
+
Value: ServerThreads

Type: DWORD
Default: 25 (CM_CONFIGDEFAULT_SVTHREADS)
Variable: numSvThreads

@@ -7013,7 +6262,7 @@ the AFS client service (afsd_service.exe).

-
Value: Stats
+
Value: Stats

Type: DWORD
Default: 10000 (CM_CONFIGDEFAULT_STATS)
Variable: cm_initParams.nStatCaches

@@ -7023,9 +6272,8 @@ the AFS client service (afsd_service.exe).

-
Value: - LogoffPreserveTokens
+
Value: LogoffPreserveTokens

Type: DWORD {1,0}
Default : 0

If enabled (set to 1), the Logoff Event handler will not @@ -7036,7 +6284,7 @@ the AFS client service (afsd_service.exe).

-
Value: RootVolume
+
Value: RootVolume

Type: REG_SZ
Default: "root.afs"
Variable: cm_rootVolumeName

@@ -7046,9 +6294,8 @@ the AFS client service (afsd_service.exe).

-
Value: - Mountroot
+
Value: Mountroot

Type: REG_SZ
Default: "/afs"
Variable: cm_mountRoot

@@ -7059,16 +6306,15 @@ the AFS client service (afsd_service.exe).

/afs/athena.mit.edu/foo/bar/baz and cm_mountRoot is "/afs", then the path is interpreted as \\afs\all\athena.mit.edu\foo\bar\baz.  If a path does not start with with - cm_mountRoot, the path is assumed to be relative and suffixed to the reference - directory (i.e. directory where the symlink exists)

+ cm_mountRoot, the path is assumed to be relative and suffixed to the + reference directory (i.e. directory where the symlink exists)

-
Value: - CachePath
+
Value: CachePath

Type: REG_SZ or REG_EXPAND_SZ
Default: "%TEMP%\AFSCache"
Variable: cm_CachePath

@@ -7081,8 +6327,7 @@ the AFS client service (afsd_service.exe).

-
Value: - NonPersistentCaching
+
Value: NonPersistentCaching

Type: DWORD [0..1]
Default: 0
Variable: buf_CacheType

@@ -7096,12 +6341,12 @@ the AFS client service (afsd_service.exe).

-
Value: ValidateCache
+
Value: ValidateCache

Type: DWORD [0..2]
Default: 1
Variable: buf_CacheType

-

This value determines if and when persistent cache validation - is performed.

+

This value determines if and when persistent cache + validation is performed.

0 - Validation is disabled
1 - Validation is performed at startup
2 - Validation is performed at shutdown

@@ -7110,20 +6355,19 @@ the AFS client service (afsd_service.exe).

-
Value: TrapOnPanic
+
Value: TrapOnPanic

Type: DWORD {1,0}
Default: 0
Variable: traceOnPanic

-

Issues a breakpoint in the event of a panic. (breakpoint: - _asm int 3).

+

Issues a breakpoint in the event of a panic. + (breakpoint: _asm int 3).

-
Value: - NetbiosName
+
Value: NetbiosName

Type: REG_EXPAND_SZ
Default: "AFS"
Variable: cm_NetbiosName

@@ -7136,7 +6380,7 @@ the AFS client service (afsd_service.exe).

-
Value: IsGateway
+
Value: IsGateway

Type: DWORD {1,0}
Default: 0
Variable: isGateway

@@ -7147,14 +6391,14 @@ the AFS client service (afsd_service.exe).

When IsGateway is non-zero, the LAN adapter detection code will avoid binding to a loopback adapter.  This will ensure that the NetBIOS name will - be of the form hostname-AFS instead of the value set by the "NetbiosName" - registry value.

+ be of the form hostname-AFS instead of the value set by the + "NetbiosName" registry value.

-
Value: ReportSessionStartups
+
Value: ReportSessionStartups

Type: DWORD {1,0}
Default: 0
Variable: reportSessionStartups

@@ -7167,9 +6411,8 @@ the AFS client service (afsd_service.exe).

-
Value: - TraceBufferSize
+
Value: TraceBufferSize

Type: DWORD
Default: 5000 (CM_CONFIGDEFAULT_TRACEBUFSIZE)
Variable: traceBufSize

@@ -7179,23 +6422,22 @@ the AFS client service (afsd_service.exe).

-
Value: - SysName
+
Value: SysName

Type: REG_SZ
Default: "i386_nt40"
Variable: cm_sysName

-

Provides an initial value for "fs sysname".  The string can contain one or more - replacement values for @sys in order of preference separated by whitespace.

+

Provides an initial value for "fs + sysname".  The string can contain + one or more replacement values for @sys in order of preference separated by + whitespace.

-
Value: - SecurityLevel
+
Value: SecurityLevel

Type: DWORD {1,0}
Default: 0
Variable: cryptall

@@ -7205,9 +6447,8 @@ the AFS client service (afsd_service.exe).

-
Value: - UseDNS
+
Value: UseDNS

Type: DWORD {1,0}
Default: 1
Variable: cm_dnsEnabled

@@ -7220,9 +6461,8 @@ the AFS client service (afsd_service.exe).

-
Value: - FreelanceClient
+
Value: FreelanceClient

Type: DWORD {1,0}
Default: 0
Variable: cm_freelanceEnabled

@@ -7232,9 +6472,8 @@ the AFS client service (afsd_service.exe).

-
Value: - HideDotFiles
+
Value: HideDotFiles

Type: DWORD {1,0}
Default: 1
Variable: smb_hideDotFiles

@@ -7246,7 +6485,7 @@ the AFS client service (afsd_service.exe).

-
Value: MaxMpxRequests
+
Value: MaxMpxRequests

Type: DWORD
Default: 50
Variable: smb_maxMpxRequests

@@ -7257,7 +6496,7 @@ the AFS client service (afsd_service.exe).

-
Value: MaxVCPerServer
+
Value: MaxVCPerServer

Type: DWORD
Default: 100
Variable: smb_maxVCPerServer

@@ -7267,8 +6506,8 @@ the AFS client service (afsd_service.exe).

-
Value: Cell
+
Value: Cell

Type: REG_SZ
Default: <none>
Variable: rootCellName

@@ -7279,7 +6518,7 @@ the AFS client service (afsd_service.exe).

-
Value: RxNoJumbo
+
Value: RxNoJumbo

Type: DWORD {0,1}
Default: 0
Variable: rx_nojumbo

@@ -7290,9 +6529,8 @@ the AFS client service (afsd_service.exe).

-
Value: - RxMaxMTU
+
Value: RxMaxMTU

Type: DWORD
Default: -1
Variable: rx_mtu

@@ -7305,8 +6543,7 @@ the AFS client service (afsd_service.exe).

-
Value: - ConnDeadTimeout
+
Value: ConnDeadTimeout

Type: DWORD
Default: 60 (seconds)
Variable: ConnDeadtimeout

@@ -7322,28 +6559,26 @@ the AFS client service (afsd_service.exe).

-
Value: - HardDeadTimeout
+
Value: HardDeadTimeout

Type: DWORD
Default: 120 (seconds)
Variable: HardDeadtimeout

The Hard Dead Time is enforced to be at least double the - ConnDeadTimeout.  The provides an opportunity - for at least one retry.

+ ConnDeadTimeout.  The provides an + opportunity for at least one retry.

-
Value: - TraceOption
+
Value: TraceOption

Type: DWORD {0-15}
Default: 0

Enables logging of debug output to the Windows Event Log.

-

Bit 0 enables logging of "Logon Events" - processed by the Network Provider and Winlogon Event Notification Handler.Bit 0 enables logging of "Logon Events" processed + by the Network Provider and Winlogon Event Notification Handler. 

Bit 1 enables logging of events captured by the AFS Client Service.

@@ -7355,7 +6590,7 @@ the AFS client service (afsd_service.exe).

-
Value: AllSubmount
+
Value: AllSubmount

Type: DWORD {0, 1}
Default: 1

Variable: allSubmount (smb.c)

@@ -7368,9 +6603,8 @@ the AFS client service (afsd_service.exe).

-
Value: - NoFindLanaByName
+
Value: NoFindLanaByName

Type: DWORD {0, 1}
Default: 0

Disables the attempt to identity the network adapter to @@ -7380,7 +6614,7 @@ the AFS client service (afsd_service.exe).

-
Value: MaxCPUs
+
Value: MaxCPUs

Type: DWORD {1..32} or {1..64} depending on the architecture
Default: <no default>

@@ -7393,9 +6627,8 @@ the AFS client service (afsd_service.exe).

-
Value: - smbAuthType
+
Value: smbAuthType

Type: DWORD {0..2}
Default: 2

If this value is specified, it defines the type of SMB @@ -7411,9 +6644,8 @@ the AFS client service (afsd_service.exe).

-
Value: - MaxLogSize
+
Value: MaxLogSize

Type: DWORD {0 .. MAXDWORD}
Default: 100K

This entry determines the maximum size of the @@ -7426,7 +6658,7 @@ the AFS client service (afsd_service.exe).

-
Value: FlushOnHibernate
+
Value: FlushOnHibernate

Type: DWORD {0,1}
Default: 1

If set, flushes all volumes before the machine goes on @@ -7445,8 +6677,8 @@ the AFS client service (afsd_service.exe).

height:65.0pt'> -
Value: - <Drive Letter:> for example "G:"
+
Value: <Drive + Letter:> for example "G:"

Type: REG_SZ

Specifies the submount name to be mapped by afsd_service.exe at startup to the provided drive letter.

@@ -7463,22 +6695,21 @@ the AFS client service (afsd_service.exe).

-
Value: +
Value: CellServDBDir

Type: REG_SZ
Default: <not defined>

-

Specifies the directory - containing the CellServDB file.  When - this value is not specified, the AFS Client install directory is used.

+

Specifies the directory containing + the CellServDB file.  When this value + is not specified, the AFS Client install directory is used.

-
Value: - VerifyServiceSignature
+
Value: VerifyServiceSignature

Type: REG_DWORD
Default: 0x1

This value can be used to disable the runtime @@ -7497,9 +6728,8 @@ the AFS client service (afsd_service.exe).

-
Value: - IoctlDebug
+
Value: IoctlDebug

Type: REG_DWORD
Default: 0x0

This value can be used to debug the cause of pioctl() @@ -7513,7 +6743,7 @@ the AFS client service (afsd_service.exe).

-
Value: MiniDumpType
+
Value: MiniDumpType

Type: REG_DWORD
Default: 0x0 (MiniDumpNormal)

This value is used to specify the type of minidump @@ -7543,20 +6773,19 @@ the AFS client service (afsd_service.exe).

-
Value: - StoreAnsiFilenames
+
Value: StoreAnsiFilenames

Type: REG_DWORD
Default: 0x0

This value can be used to force the AFS Client Service - to store filenames using the Windows system's ANSI character set instead of - the OEM Code Page character set which has traditionally been used by SMB file + to store filenames using the Windows system's ANSI character set instead of the + OEM Code Page character set which has traditionally been used by SMB file systems. 

Note: The use of ANSI characters will render access to files with 8-bit OEM file names unaccessible from Windows.  This option is of use primarily when you - wish to allow file names produced on Windows to be accessible from Latin-1 UNIX - systems and vice versa.

+ wish to allow file names produced on Windows to be accessible from Latin-1 + UNIX systems and vice versa.

@@ -7571,8 +6800,8 @@ the AFS client service (afsd_service.exe).

height:112.0pt'> -
Value: - "smb/cifs share name"
+
Value: "smb/cifs + share name"

Type: REG_SZ
Default: <none>

This key is used to map SMB/CIFS @@ -7599,8 +6828,8 @@ _Toc115416247'>Regkey:
height:138.5pt'> -

Value: - "numeric value"
+
Value: "numeric + value"

Type: REG_SZ
Default: <none>

This key is used to store dot @@ -7627,8 +6856,8 @@ _Toc115416249'>Regkey:
height:145.0pt'> -

Value: - "numeric value"
+
Value: "numeric + value"

Type: REG_SZ
Default: <none>

This key is used to store a dot @@ -7652,8 +6881,8 @@ _Toc115416249'>Regkey:
height:171.75pt'> -

Value: - "submount name"
+
Value: "submount + name"

Type: REG_EXPAND_SZ
Default: <none>

This key is used to store @@ -7684,8 +6913,8 @@ _Toc115416253'>Regkey:
height:105.5pt'> -

Value: - "hostname or ip address"
+
Value: "hostname or + ip address"

Type: REG_DWORD
Default: <none>

This key is used to specify a @@ -7708,13 +6937,13 @@ _Toc115416253'>Regkey:
height:105.5pt'> -

Value: - "hostname or ip address"
+
Value: "hostname or + ip address"

Type: REG_DWORD
Default: <none>

-

This key is used to specify a - default set of File server preferences. For each entry the value name will be - either the IP address of a server or a fully qualified domain name.This key is used to specify a default + set of File server preferences. For each entry the value name will be either + the IP address of a server or a fully qualified domain name.  The value will be the ranking.  The ranking will be adjusted by a random value between 0 and 256 prior to the preference being set.

@@ -7722,13 +6951,14 @@ _Toc115416253'>Regkey:
-

A.2. Integrated +

A.2. Integrated Logon Network provider parameters

Affects the network provider (afslogon.dll).

-

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

+

Regkey: +[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters]

@@ -7955,21 +7179,20 @@ name"]
-
Value: - FailLoginsSilently
+
Value: FailLoginsSilently

Type: DWORD
Default: 0

Do not display message boxes if @@ -7756,8 +6985,7 @@ Logon Network provider parameters

-
Value: - NoWarnings
+
Value: NoWarnings

Type: DWORD
Default: 0

Disables visible warnings during @@ -7767,8 +6995,7 @@ Logon Network provider parameters

-
Value: - AuthentProviderPath
+
Value: AuthentProviderPath

Type: REG_SZ
NSIS: %WINDIR%\SYSTEM32\afslogon.dll

Specifies the install location of the authentication @@ -7778,7 +7005,7 @@ Logon Network provider parameters

-
Value: Class
+
Value: Class

Type: DWORD
NSIS: 0x02

Specifies the class of network provider

@@ -7787,7 +7014,7 @@ Logon Network provider parameters
-
Value: DependOnGroup
+
Value: DependOnGroup

Type: REG_MULTI_SZ
NSIS: PNP_TDI

Specifies the service groups upon which the AFS Client @@ -7799,8 +7026,7 @@ Logon Network provider parameters

-
Value: - DependOnService
+
Value: DependOnService

Type: REG_MULTI_SZ
NSIS: Tcpip NETBIOS RpcSs

Specifies a list of services upon which the AFS Client @@ -7812,7 +7038,7 @@ Logon Network provider parameters

-
Value: Name
+
Value: Name

Type: REG_SZ
NSIS: "OpenAFSDaemon"

Specifies the display name of the AFS Client Service

@@ -7821,7 +7047,7 @@ Logon Network provider parameters
-
Value: ProviderPath
+
Value: ProviderPath

Type: REG_SZ
NSIS: %WINDIR%\SYSTEM32\afslogon.dll

Specifies the DLL to use for the network provider

@@ -7838,11 +7064,11 @@ Domain specific configuration keys for the Network Provider

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.

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

Domain specific registry keys are:

@@ -7866,8 +7092,7 @@ key. One per domain.)

Example:

-

 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider

+

 HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider

  |

@@ -7886,8 +7111,8 @@ style='mso-spacerun:yes'> values described in 2.1.1.  The effective values are chosen as described in 2.1.2.

-

A.2.1.1 Domain -specific configuration values

+

A.2.1.1 +Domain specific configuration values

[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider]
[HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain]
@@ -7901,8 +7126,8 @@ name"]

-
Value: +
Value: LogonOptions

Type: DWORD
Default: 0x01

@@ -7926,8 +7151,7 @@ name"]
-
Value: - FailLoginsSilentl
+
Value: FailLoginsSilentl

Type: DWORD (1|0)
Default: 0
NSIS/WiX: (not set)

@@ -7938,7 +7162,7 @@ name"]
-
Value: LogonScript
+
Value: LogonScript

Type: REG_SZ or REG_EXPAND_SZ
Default: (null)
NSIS/WiX: (only value under NP key) <install path>\afscreds.exe -:%s -x @@ -7946,8 +7170,8 @@ name"]

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 + "%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.
-
Value: LoginRetryInterval
+
Value: LoginRetryInterval

Type: DWORD
Default: 30
NSIS/WiX: (not set)

-

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.

+

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.
-
Value: - LoginSleepInterval
+
Value: LoginSleepInterval

Type: DWORD
Default: 5
NSIS/WiX: (not set)

@@ -7979,9 +7202,8 @@ name"]
-
Value: - TheseCells
+
Value: TheseCells

Type: REG_MULTI_SZ
NSIS: <not set>

When Kerberos 5 is being used, TheseCells provides a @@ -7996,24 +7218,25 @@ style='mso-spacerun:yes'> specific configuration

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.

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

1.      -NP key. ("HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider")

+NP key. +("HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider")

2.      Domains key. (NP key\"Domain")

3.      Specific domain key. (Domains key\X)

@@ -8023,28 +7246,29 @@ domains key will be ignored. configuration information in this case will come from the NP key.

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.

- -

A.2.1.3 Exceptions -to A.2.1.2

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

+ +

A.2.1.3 +Exceptions to A.2.1.2

To retain backwards compatibility, the following exceptions are made to 2.1.2.

2.1.3.1 'FailLoginsSilently'

-

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.

+

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.

2.1.3.2 'LogonScript'

@@ -8056,8 +7280,8 @@ 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.

-

A.3. AFS +

A.3. AFS Credentials System Tray Tool parameters

Affects the behavior of afscreds.exe

@@ -8071,8 +7295,7 @@ Credentials System Tray Tool parameters

-
Value: - Gateway
+
Value: Gateway

Type: REG_SZ
Default: ""
Function: GetGatewayName()

@@ -8084,12 +7307,12 @@ Credentials System Tray Tool parameters
-
Value: Cell
+
Value: Cell

Type: REG_SZ
Default: <none>
Variable: IsServiceConfigured()

-

The value Cell is used to determine if the AFS Client - Service has been properly configured or not.

+

The value Cell is used to determine if the AFS Client Service + has been properly configured or not.
@@ -8104,13 +7327,12 @@ 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].

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

-
Value: EnableKFW
+
Value: EnableKFW

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

@@ -8136,9 +7358,8 @@ Credentials System Tray Tool parameters -
Value: - Use524
+
Value: Use524

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

@@ -8153,14 +7374,13 @@ 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 @@ -8190,8 +7410,8 @@ Credentials System Tray Tool parameters height:92.0pt'> -

Value: - Authentication Cell
+
Value: Authentication + Cell

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

@@ -8212,8 +7432,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()

@@ -8236,12 +7456,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

@@ -8259,8 +7479,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 @@ -8271,8 +7491,8 @@ Credentials System Tray Tool parameters -

A.4 OpenAFS +

A.4 OpenAFS Client Service Environment Variables

mso-border-insideh:.75pt outset windowtext;mso-border-insidev:.75pt outset windowtext'> 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 c1bd4e4e1..ba0bbe7eb 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="http://www.w3.org/TR/REC-html40"> @@ -10,8 +10,9 @@ xmlns:st1="urn:schemas:contacts" xmlns="http://www.w3.org/TR/REC-html40"> + + name="address"/> + name="Street"/> + name="PlaceType"/> - + name="place"/> 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 8158584d4c66239b23d2de0224e888eae5c46f67..f59937fe324cca712f3a86d3750a96d92f9e7222 100644 GIT binary patch delta 3918 zcmZ`+e{3699e?NK;>14^$4>0nNt|=@(@B#i=PhyBy2N&tu53*cIx;78Os;)xgHpT1 z?pj7i){c5;8{qIQ2o0uH6SSZK5(yGWtu*lm2o+H=F_jjbkU&F1l`8tjCMGl~e82DA z#g|I+>F(aW_xv-_yAMVZZ!`9z(SJKmy?kNsi9|ql z*%+&3j15cTZCl?=ND|0WaZO@wTu>da)Ln0vI1yvF`ztY}{5}3*WzPmW(E&JUj zw}tX^+KQGbYRYV(q!sJ#u&eAa-dEWbKDxtx&2s!(05J94vfm4!WazXx9ObK~Du~)9 z-8S}Fu4u49mj~fRTemkcb2zFj7nO{%QpjdX%Y{5#wvEK0)gY^#ISdPV+$`<*RX0v!L;;pg-&d2$944*mU`T=q^%Yh)x zsU|-5EiU?B4qbi*5^@~w%7c;uFUX^db8L>ifV@Oann=zfo4_vtQ^h&bMzbj#PvC7* z<=7Y>)3?gfNI`2vjZ!yLbrGqP#LsPuA|p(aMV5w0m(TeKhj!Ve%L=?@9|Bwbl>a$n z?zkszi5T3l$01pN*7+J={+e5tKM%jFSK&y*h@`>C^|N-ufeK;0p|d8-RQP2>peD`K z%|ABmmz)oCw!KZd+yR}=ez@Qq4bO9QIdA{BCF2n@J}0=7OvjMx zlX$1N0|)@QkXB8n9z;GBww$doqN5e!Ax}_{#C4FnjdG1L_sblO-=oXZu-`QdH(l-a z(y~?@Q4}b-rs1w@ypM2DI&g!HYVdm=3GJ)~$hi+-q<`UFmdeo9nCMU_$Vsl1>=0HN zQs8vsr1L4R`(dvx55c>QQqyDoW}wM1$|Y;|z0R3^ zK3!gbJ534rp+~7fC&6#sJ{a{ZY+m;)NCBz<)BZ!8;bx024@1-&moo6GcgetTv*kw1 z4h$J@R4Ty--X-UEINLj|y1WDjde#ID8 z5MIIt3Y5tGG>%d@#;QbG3ZaT_tOkMjtwGP?T9!*xV@RCh41y?!Q6qMOCA!!Ix*BFeG`6iquG=VhvGq*hcQALxPm zfjw);OMD`TqG4(Lo9b+Wk3`U@Wr?s`SBRs+wG$Rf5(=_Ngp|?dsKp5v@5D-BUn7x} zRn-5+xG@BWX2~&TxGOyLDSWCppTul4Q~ulB%!@%?PFu_@ozRqArj$`KtD15;pE*PC z!ZGE{2@MCdO3_%(X5jB_dqM=5G|`hxrl=FtF$UpaWk&ejR7me($%aIm zqj~aUTvQKH!F$1ktA+&)4dZQaGcTox3hmuL`QUrS)PmLj!n5*brvHj^xp>F4tNdMhRkO#YI6;8?Ld>LvQ#4|eqh!S3G3a*)_ z4nj?Nuz~A~sGl$rjyNK@hEG~09}!-f6*WdQgu1#h(&3}RPOmNUjc#)C2*q6hPpo5kpjcz zB*LMZ3w2GnMavau*Fs(?!uws5kLHBwWDH3nMR^m0#WK^ zG$)*qP#9`xu+xC$MjDH2+069EP7OUzBp-ja=zyF=j7x)tSzr^YzIBHXis* zZFu$s;njgg*jAgVZ9;>ArPk)CFQFsq9i7)cV}ekT)W_JZXV^C^7Slax$}=FX0Vpx7uz=2`bjT91+=)W0334 z*^Sl+O+Ar;AD7KQZbYsGt+h-m9z&xe1nHi^Cu^AtC#D)A>^{Ef=V0TuKSYv2JB~lW zzcX7~TR0L5Wd6P{)iN398gP}_dhww;HX>)?Pd(we6_u^yMV8W$!3-!RVcO`9BFQ!) zFYVaNm2$Pui2eA(UAi2@KI4Pg-XV#>h29gLr0T<6LxHfxTO~z1cC3Ke51zhOujt50 ztS}9=(--vh_2F4tw;HOCVsoG@Qri$fzPX=2CD^Ez>pHf`G2URxL1=GBL`5_h7di@U7DwQpOa)Q%jd zYqtusKD13Rk?d<(R%sFg)D9ISmLU4ahQvz(Dlv)YR@O z5S2oRK~0Db`u(@-SO29S`n*Lm;&atPL?#Xz6WLt)WL|zh*tu|Sq{*eWxHQe$>RR~j ztmcvtEl^tgl0Ej|8sR5-QO|Fx-*2o|b3(k^KOg&~Ic=t9P2;w>E)LRtU0kD^A-P10 zwP&)W%CW~t>?!MmGE&nbzgijAy5-+1heiP7Y1*5l-wa8F6ljjD z;D{@28S#iEV|&Yh!$A4t%7M*EF|NRDTM+<5;v%j70}2}h*mNyFqlYwIJ<8Xrd?8F{ zNF$@LF@I6%`*K}bpOo)ZZIF}Iap|fak@MAOYWJ$S&(@dqe%b7fYC;y>3IC(k=;bw= zoCx>0H&p`v8N2lqIELYU*(`px#r0tDmJt;rs>6f=WJGG)b z=NT$N%sg#mPr>XYnTJTFX%t4oNZ2z*_qdwHIQ)uP+tUC5i^tSlT&;wY(h63Do*;uG zVaI+#B>c3=cF-;b((f(nJ@QKJp!`$q?#M&dnBi@AxWLHfGTGDF%v@^P$QO(gh5X!% zk(FX+qwV^LnLdss8&+jUuO zQO4^>J4`rfj7&(W6DzP*}IDDeH&i@9Ve9^9}2zzu~a_M#C_4`f+P6<~JPH5^N(iYdmF6PviGgelAxuX7brw zk;ZcwWBI+t!&+-p#8y1{1tsV0ma=|W?r)0AJ5B55#ik>&Yt0c${|z7XUsy9*LLd=t zgco6DCM75?ieV~zNKV)tS7Qh|l96|2#8sM!(YHw>NIR@#S$Ik-N-)Jn6|Nh;oBptE zUj-FM`J**qAH2y$fc+YQm*pEx!6=vwazU?+Fskrz>~8pcp$B63?dCmNR^Dw+QS7E# z_6@9HWhx_&R~Zl!Zz|-Fo|Hdp36_#nlz?TNY`Th3x`6?9vChBx?;1{>gH$nX9tV|` zw_3}3jcp|vna@q1H45g;bjbD_%LEoK4Yyjq?w-VsFbTk+kxi#I8tLgQ@tVS)rSKQb zRK`frL;kq@fiLDhW~TF}h#s=w`?mGVKraQ$`r}TZH(U2N9U`FVe6FbCl0R;kvLi6x%apXw9{7QMWc!0O%U6S= z(Mlz5wXLWSpHQmOZDoCfLlxWszGTyKM=(?>*q8wmqydEyK46D7wuaLZc5##t7sP<^ zz*E~)!ty#kQ3th3!K6*M^*1|7TTpFFHg_WQQd^+DLNGznZB72LT-z2Zk@0{zo1ZJB zO~XD9fCvQ=@qiC(?KW?K`TjU0=s$LFT&`NMIzK&k%G_kojuHvy`eWDe zk#^JV%u8c&YQ^1b;1;E^}#0dUpRA8R%n5h|d1cpwW$LIjc zKQ$}c+qcM6`*XD~tA$T?mh~s(KiV@oobo+6*%79`1-yk167-E82TCYEut!Az=9q#8)A=q!B*0AcFi_qMDSJF^ z-OqV+hZx#@B4_f_3@zr`-qu}J=j0G-`-}zS;X3(~t^*}yUz9=t@wnM$PAbr!J&O{^ zp5j0uth{=XX5a*Fs$e`^!M?OT%EqAA02%n3%WXTRoRQ}K?qB4kq zYh07RFrNAJF*p~gZ#&*D&#;=Kg%J)#%)%C@Lc#9CIbqT$bA!VN^^A&ak>3mjnj-aseUoe#7sq0?{;-W6SI=?mrsBldkkAI|~^SXK$Gs>nx&291GkA44nARN-Wd81ab{K~+)8mTU9T@6B*&SQeW5&{}8($p!kc~adm0M0%{|^L0Hg5m` -- 2.39.5
-
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
@@ -8290,13 +7509,12 @@ 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