From 5da4137cbe2574fc8602bd7ffaeaf8d85bd9e010 Mon Sep 17 00:00:00 2001 From: Jeffrey Altman Date: Sun, 29 Jun 2008 06:08:00 +0000 Subject: [PATCH] windows-remove-ibm-docs-20080628 LICENSE MIT Remove (from the en_US distributions) the IBM Quick Guide and IBM Release Notes. Update references and installers. --- doc/man-pages/NTMakefile | 2 + .../en_US/html/InstallGd/awqbg000.htm | 43 - .../en_US/html/InstallGd/awqbg002.htm | 64 - .../en_US/html/InstallGd/awqbg003.htm | 1203 ----------------- .../en_US/html/InstallGd/awqbg004.htm | 341 ----- .../en_US/html/ReleaseNotes/awrns000.htm | 43 - .../en_US/html/ReleaseNotes/awrns002.htm | 135 -- .../en_US/html/ReleaseNotes/awrns003.htm | 98 -- .../en_US/html/ReleaseNotes/awrns004.htm | 238 ---- .../en_US/html/ReleaseNotes/awrns005.htm | 179 --- .../en_US/html/ReleaseNotes/awrns006.htm | 209 --- .../en_US/html/ReleaseNotes/awrns007.htm | 151 --- .../Documentation/en_US/html/index.htm | 25 +- src/WINNT/install/NSIS/OpenAFS.nsi | 4 - src/WINNT/install/wix/feature.wxi | 3 +- src/WINNT/install/wix/files.wxi | 9 +- 16 files changed, 8 insertions(+), 2739 deletions(-) delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg000.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg002.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg003.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg004.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns000.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns002.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns003.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns004.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns005.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns006.htm delete mode 100755 src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns007.htm diff --git a/doc/man-pages/NTMakefile b/doc/man-pages/NTMakefile index 79d1ba520e..040e443669 100644 --- a/doc/man-pages/NTMakefile +++ b/doc/man-pages/NTMakefile @@ -25,6 +25,8 @@ # NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +!INCLUDE ..\..\src\config\NTMakefile.$(SYS_NAME) + install: @echo Building man pages in HTML format perl generate-html diff --git a/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg000.htm b/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg000.htm deleted file mode 100755 index ae88d5af4e..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg000.htm +++ /dev/null @@ -1,43 +0,0 @@ - - -Quick Beginnings - - - - - - - - - - - -

Quick Beginnings

-

[Return to Library] [Table of Contents] [Bottom of Topic] [Next Topic] [Index]

-AFS for Windows
-Quick Beginnings
-

Version 3.6 -

Document Number SC09-4564-00 -

CT6Q8NA -

First Edition (April 2000) -

This edition applies to: -

-
IBM AFS for Windows, Version 3.6 -
-

and to all subsequent releases and modifications until otherwise indicated -in new editions. -

This softcopy version is based on the printed edition of this book. -Some formatting amendments have been made to make this information more -suitable for softcopy. -

Order publications through your IBM representative or through the IBM -branch office serving your locality. -

© Copyright International Business Machines Corporation 1999. All rights reserved. -

-

[Return to Library] [Table of Contents] [Top of Topic] [Next Topic] [Index]

- -

-
© IBM Corporation 2000. All Rights Reserved - - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg002.htm b/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg002.htm deleted file mode 100755 index 1333341c3d..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg002.htm +++ /dev/null @@ -1,64 +0,0 @@ - - -Quick Beginnings - - - - - - - - - - - -

Quick Beginnings

-

[Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index]

-

Table of Contents

-

IBM AFS for Windows Quick Beginnings
-

-
  • Introduction -
  • Document Overview - -
  • Audience -
  • Organization -
    •  -
  • Installing AFS for Windows - -
  • AFS for Windows Components -
  • Installation Options -
  • Upgrading From an Earlier Version -
  • To Install AFS for Windows -
  • Changes Made to Your System -
    •  -
  • AFS for Windows Documentation - -
  • The Online Documentation Directory -
  • The CD-ROM Documentation Directory -
  • Online Help -
    •  -
  • Configuring AFS for Windows - -
  • To Configure the AFS Client -
  • To Configure the AFS Client as an AFS Light Gateway -
  • To Configure AFS Light -
  • To Configure the AFS Server -
  • To Configure the AFS Control Center -
    •  -
  • Uninstalling AFS for Windows - -
  • Reinstalling and Upgrading -
  • Uninstallation Prerequisites -
  • To Uninstall AFS for Windows -
  • Changes Made to Your System -
    •  -

    Index
    -

    -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg003.htm b/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg003.htm deleted file mode 100755 index 7914c7ff8d..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg003.htm +++ /dev/null @@ -1,1203 +0,0 @@ - - -Quick Beginnings - - - - - - - - - - - -

    Quick Beginnings

    -

    [Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index]

    -

    IBM AFS for Windows Quick Beginnings

    -

    Introduction

    - - -

    AFS(R) is an enterprise file system that provides consistent -file access by way of a shared filespace. By joining the local file -systems of several File Server machines, AFS presents a single filespace -independent of machine boundaries. Files are stored on different -machines in the computer network but are accessible from all machines across -the enterprise. -

    IBM AFS for Windows(R), version 3.6 extends the full -capabilities of AFS to Microsoft(R) Windows operating -systems. -

    Document Overview

    -

    - -This document summarizes installation prerequisites, provides detailed -instructions on how to install, configure, and uninstall AFS for Windows, and -outlines the changes made to your system during the installation and -uninstallation processes. This document also describes the -documentation provided with AFS for Windows. -

    Audience

    -

    - -This document provides information for system administrators and users -responsible for the installation and configuration of the products included in -AFS for Windows. This document assumes that system administrators are -familiar with system administration in general and that users are familiar -with the basic terms and concepts of the Microsoft Windows operating -systems. -

    Organization

    -

    This document has the following organization: -

    -

    Installing AFS for Windows

    -

    This section outlines installable combinations of AFS components, -describes the procedure for installing AFS for Windows, and lists the changes -that the installation process makes to your system. -

    AFS for Windows Components

    -

    - -AFS for Windows, version 3.6 includes the following components: -

    -

    Installation Options

    -

    - - - -You can install the components of AFS for Windows in various combinations, -based on your Windows operating system. Refer to the IBM AFS for -Windows Release Notes for details on the specific software requirements -for each AFS for Windows component. Note that if you are installing the -AFS Server, you must also install the AFS Client, unless the AFS Client, -version 3.6 is already installed on the machine. Follow the -installation procedure described in To Install AFS for Windows regardless of the components you are installing. -
    Note: - - - - - -You have the option of altering the AFS for Windows setup program to disable -all but the client component. Such a client-only setup program renders -users unable to install any components other than the AFS Client. To -perform a client-only installation, create the file setup.co -in the same directory as the other installation files; the setup program -then only allows the AFS Client to be installed. Note that the contents -of the setup.co file are irrelevent. Follow the -installation procedure described in To Install AFS for Windows regardless of the type of installation you are -performing. -
    -

    Upgrading From an Earlier Version

    -

    - - - -On a Windows NT machine, it is not necessary to uninstall the -components of AFS for Windows for the purpose of upgrading the software; -you can install this release of AFS for Windows on your system -without removing or unconfiguring your existing software. To -upgrade AFS for Windows, follow the installation procedure described in To Install AFS for Windows. During the installation process, the -previous-version AFS component is upgraded and the AFS configuration -information is preserved. -

    On a Windows 95 or Windows 98 machine, you must uninstall the -previously-installed AFS Light component, as described in To Uninstall AFS for Windows, before upgrading AFS Light. -

    Note that the AFS for Windows installation tool does not allow a -user to install AFS components that have different version numbers. If -you have more than one AFS for Windows component installed on your machine, -you cannot update one component without updating all of the other components -as well. -

    To Install AFS for Windows

    - - - - - - - -

    Before installing AFS for Windows, refer to your IBM AFS for Windows -Release Notes for a detailed description of the installation -prerequisites. If you are running any other Windows applications, it is -recommended that you exit from them before installing AFS for Windows. -

      -

    1. Insert the AFS for Windows installation disk into your CD-ROM -drive. -

    2. Run the AFS for Windows setup program by using one of the -following methods: -
        -

      • From the Start menu, select Run. Type -drive:\setup where drive is -the drive letter of your CD-ROM drive. Click OK. -

      • In the Windows Explorer, select your CD-ROM drive, and -double-click the setup.exe program. -
      -

    3. The Welcome dialog box appears. Select the Next button -to continue with the installation process. -

    4. The Select Components dialog box appears. -
        -

      • In the Components box, select the AFS for Windows components -that you want to install or upgrade. See Installation Options for information on the various combinations of components -that can be installed on a Windows machine. Note that if you are -installing the AFS Server, you must also select to install (or upgrade) the -AFS Client, unless the AFS Client, version 3.6 is already installed on -your system. -

      • The Destination Folder box indicates the default drive and -directory in which the selected components will be installed. The -default drive is the drive where Windows is installed. The default -directory on that drive is \Program Files\Ibm\Afs. To select -another drive, directory, or both, select the Browse button. -
        Note:If you are upgrading from a previous-version of AFS for Windows or -reinstalling AFS for Windows, the installation directory that you choose must -be the same as the installation directory that was used by the -previously-installed version. -
        -
      -

      Select the Next button to continue with the installation -process. -

    5. The application files for the selected AFS for Windows components are -installed on your system. When the installation process finishes, the -Setup Complete dialog box appears, indicating that you must restart your -system before you can use the installed AFS products. Select Yes, -I want to restart my computer now, and then select the Finish -button. Your system is shut down and then restarted. -

      Installation of AFS for Windows is complete. -

    -

    Changes Made to Your System

    -

    - -This section describes the changes that are made to your system by installing -each AFS for Windows component. The information in this section is -based upon the default installation settings. -

    Changes made to your system by installing the AFS Client

    -

    Installing the AFS Client for Windows NT makes the following changes to -your system: -

    -

    Changes made to your system by installing AFS Light

    -

    Installing AFS Light for Windows 95 and Windows 98 makes the following -changes to your system: -

    -

    Changes made to your system by installing the AFS Server

    -

    Installing the AFS Server for Windows NT makes the following changes to -your system: -

    -

    Changes made to your system by installing the AFS Control Center

    -

    Installing the AFS Control Center for Windows NT makes the following -changes to your system: -

    -

    Changes made to your system by installing the AFS Supplemental Documentation

    -

    Installing the AFS Supplemental Documentation makes the following -changes to your system: -

    -

    AFS for Windows Documentation

    -

    This section describes the documentation that is provided with AFS for -Windows and details the procedures for accessing this documentation. -

    The Online Documentation Directory

    - - -

    Regardless of the components you install on your system, a documentation -directory is created. The default location is \Program -Files\Ibm\Afs\Documentation. This directory includes the IBM -AFS for Windows Quick Beginnings and IBM AFS for Windows Release -Notes. These same documents are available from the Documentation -index accessed from the Documentation entry in the Start -menu. -

    If you install the AFS Supplemental Documentation, then the documentation -directory also includes the following documents: IBM AFS -Administration Guide and IBM AFS Administration -Reference. These same documents are available from the -Documentation index accessed from the Documentation entry in the -Start menu. -

    To access the online documentation directory:

    -
      -

    1. From the Start menu, choose Programs, then choose -IBM AFS, then choose Documentation. -

    2. Select the document that you want to view. -
    -

    The CD-ROM Documentation Directory

    - - -

    The AFS for Windows CD-ROM contains a documentation directory. This -directory includes the following documentation: IBM AFS for Windows -Quick Beginnings, IBM AFS for Windows Release Notes, IBM -AFS Administration Guide, and IBM AFS Administration -Reference. The documentation is provided in HTML and PDF -formats. -

    To access the CD-ROM documentation directory:

    -
      -

    1. Insert the AFS for Windows CD-ROM into your machine's CD-ROM -drive. -

    2. Follow one of the paths listed below. Note that CD is -the drive letter of your CD-ROM drive. -
        -

      • For HTML documentation, follow the path -CD:\Documentation\Html. -

      • For PDF documentation, follow the path -CD:\Documentation\Pdf. -
      -
    -

    Online Help

    - - -

    Online help is installed along with each AFS for Windows component. -The online help documentation describes the features available from each -component. Use the Help menus and Help buttons -located on most dialog boxes to access the online help. You can get -help on topics by browsing the contents page, using the index to locate -topics, and using Find, the online help search engine. -

    Configuring AFS for Windows

    -

    - - -This section details the configuration procedure for each of the components of -AFS for Windows. You must configure the components on your system -before you can use AFS. -

    To Configure the AFS Client

    - - -
    Note:If you intend to configure the AFS Server on your Windows NT system, you do -not need to configure the AFS Client. The AFS Client is configured -automatically when the AFS Server is configured. In addition, if you -upgraded to this version of AFS for Windows from a previous-version AFS -Client, configuration information is preserved. You do not need to -reconfigure the AFS Client. -
    -
      -

    1. From the Start menu, choose Settings, then choose -Control Panel. -

    2. Double-click the AFS Client Configuration icon. The AFS -Client Configuration utility opens, displaying the General -tab. -

    3. In the Cell Name box, enter the name of the AFS cell in which -the machine is to be a client. -

    4. Select the AFS Cells tab. If the cell in which the -machine is to be a client is not listed in the list of AFS cells, choose the -Add button. The New Cell dialog box opens. Enter the -cell name in the AFS Cell box and a short description in the -Description box. -

      Choose the Add button. The Add Server dialog box -opens. In the Server Name box, enter the name of a Volume -Location Server in the selected cell. Choose OK to close the -Add Server dialog box. Repeat this process, adding information for all -Volume Location Servers in the cell. (If you do not know the names of -the Volume Location Servers in the AFS cell, consult your AFS system -administrator.) After all server information has been entered, choose -OK to close the New Cell dialog box. -

    5. Select the General tab and choose the Start Service -button to start the AFS Client service. -

    6. Select the Drive Letters tab. To map a drive letter on -the Windows NT machine to the AFS filespace, choose the Add -button. The Map Drive Letter dialog box opens. -

    7. In the Drive Letter box, select the drive to be mapped to the -AFS filespace or accept the default. In the AFS -Path box, indicate the AFS location to which you want to map the -selected drive, for example, /afs. If desired, enter a -description of the AFS drive mapping in the Description box. -Choose OK to connect the drive to the specified place in the AFS -filespace. -

    8. Choose OK to close the AFS Client Configuration utility. -

      The AFS Client is now configured in the selected AFS cell and the AFS -filespace can be accessed via the selected drive mapping in the Windows NT -Explorer. -

    -

    To Configure the AFS Client as an AFS Light Gateway

    - - - -

    You can configure the AFS Client on your Windows NT machine to serve as an -AFS Light Gateway. Your AFS Client, configured as an AFS Light Gateway, -makes it possible for AFS Light users to access the AFS filespace. -

      -

    1. Configure the AFS Client as detailed in To Configure the AFS Client. -

    2. From the Start menu, choose Settings, then choose -Control Panel. -

    3. Double-click the AFS Client Configuration icon. The AFS -Client Configuration utility opens, displaying the General -tab. -

    4. Select the Provide an AFS Light Gateway option. -

    5. Choose OK. -
        -

      • If the AFS Client service is running, a message box appears, informing you -that the service must be restarted. Choose Yes to restart -the AFS Client service and enable the AFS Light Gateway. -

      • If the AFS Client service is stopped, a message box appears, informing you -that you must start the AFS Client service. Choose Yes to -start the AFS Client service and enable the AFS Light Gateway. -
      -

    6. - -Add cell entries to your AFS Light Gateway's cell database. Note -that in order for an AFS Light user to access a cell, an entry for the cell -must exist in both the AFS Light cell database and the AFS Light Gateway cell -database. Incorrect or missing information about a cell in the gateway -machine's cell database renders light client machines unable to access -files. -

      To add an entry to the cell database: -

      Access the AFS Cells tab from the AFS Light Configuration -utility and choose the Add button. The New Cell dialog box -opens. Enter the cell name in the AFS Cell box and a short -description in the Description box. -

      Choose the Add button. The Add Server dialog box -opens. In the Server Name box, enter the name of a Volume -Location Server in the selected cell. Choose OK to close the -Add Server dialog box. Repeat this process, adding information for all -Volume Location Servers in the cell. (If you do not know the names of -the Volume Location Servers in the AFS cell, consult your AFS system -administrator.) After all server information has been entered, choose -OK to close the New Cell dialog box. -

    -

    - - - -The Windows NT machine is now configured as an AFS Light Gateway. Once -configured as an AFS Light Gateway, your AFS Client machine must be able to -authenticate AFS Light users in a Windows context. This authentication -can be achieved via a domain user account or via synchronized -machine user accounts. A domain user account is a user -account in a Windows domain. A machine user account is a user account -that is valid only on a particular host machine. -

    When the AFS Light Gateway is configured into a Windows domain, the AFS -Light user must log onto either a domain user account in the domain to which -the gateway belongs or a machine user account with the same username and -password as that of a domain user account in the gateway domain. -

    If machine user accounts are employed, then these accounts must be -synchronized on the AFS Light Gateway and AFS Light machines. A user -must log onto an AFS Light machine with the same username and password as that -of a machine user account that is defined on the AFS Light Gateway -machine. -

    To Configure AFS Light

    - - -

    AFS Light accesses the AFS filespace via an AFS Light Gateway. -Before configuring AFS Light, you must have a Windows NT machine running the -AFS Client and configured as an AFS Light Gateway. See To Configure the AFS Client as an AFS Light Gateway for more information. -

      -

    1. From the Start menu, choose Settings, then choose -Control Panel. -

    2. Double-click the AFS Light Configuration icon. The AFS -Light Configuration utility opens, displaying the General -tab. - - -

    3. In the Gateway box, enter the name of a Windows NT machine that -is configured as an AFS Light Gateway and click Connect Now. -The name of the gateway machine is the gateway's NetBIOS service name, in -the form mach-afs, where mach is the -host computer name up to a maximum of 11 characters. AFS Light must be -able to resolve this service name in order to communicate with the gateway -machine. Name resolution can be achieved by adding the gateway's -NetBIOS service name to the client's LMHOSTS file or to the appropriate -DNS or WINS servers. If the AFS Light machine and its AFS Light Gateway -machine reside on the same subnet, then no additional configuration is -required. -

      AFS Light automatically becomes a member of the same cell as its AFS Light -Gateway. The name of the cell is displayed in the Cell Name -box. -
      Note:If the AFS Light Gateway machine is in the same domain as the AFS Light -machine and the hostname of the gateway machine in this domain is -xyz-pc, you can specify the computer name in the Gateway -box as either xyz-pc or -xyz-pc.xcompany.com. -
      -

    4. Select the AFS Cells tab. If the cell to which the -machine belongs is not listed in the list of AFS cells, choose the -Add button. The New Cell dialog box opens. Enter the -cell name in the AFS Cell box and a short description in the -Description box. -

      Choose the Add button. The Add Server dialog box -opens. In the Server Name box, enter the name of a Volume -Location Server in the selected cell. Choose OK to close the -Add Server dialog box. Repeat this process, adding information for all -Volume Location Servers in the cell. (If you do not know the names of -the Volume Location Servers in the AFS cell, consult your AFS system -administrator.) After all server information has been entered, choose -OK to close the New Cell dialog box. -

      Note that an identical entry must exist in the AFS Light Gateway's -cell database (afsdcell.ini file) in order for the AFS Light -user to authenticate to the cell. See To Configure the AFS Client as an AFS Light Gateway for more information on synchronizing the gateway -machine's cell database with your light client's cell -database. -

    5. Select the Drive Letters tab. To map a drive letter on -the Windows machine to the AFS filespace, choose the Add -button. The Map Drive Letter dialog box opens. -

    6. In the Drive Letter box, select the drive to be mapped to the -AFS filespace or accept the default. In the AFS -Path box, indicate the AFS location to which you want to map the -selected drive, for example, /afs. If desired, enter a -description of the AFS drive mapping in the Description box. -Choose OK to connect the drive to the specified place in the AFS -filespace. -

    7. Choose OK to close the AFS Light Configuration utility. -

      AFS Light is now configured in the specified AFS cell and the AFS filespace -can be accessed via the drive mapping in the Windows Explorer. -

    -

    To Configure the AFS Server

    - - -

    The configuration process starts the services needed to run the AFS Server -and sets up AFS partitions on your Windows NT machine. Using the AFS -Configuration Wizard, you can quickly configure the AFS Server as either the -first server in a new AFS cell or as a server in an existing AFS cell. -Note that if you have upgraded to this version of the AFS Server, -previous-version configuration information is preserved; you do not need -to reconfigure the server. -

    - -To configure the AFS Server as the first AFS Server in a cell: -

      -

    1. From the Start menu, choose Programs, then choose -IBM AFS, then choose Server, and then choose -Configuration Wizard. The AFS Server Quick-Start -Wizard opens. -

    2. Choose the Next button. The Cell and Server Information -dialog box appears. -

    3. Choose the This will be the first server in a new AFS cell -option. -

    4. In the Cell Name box, enter a name for the new AFS cell. -

      The following constraints apply to the form of an internet domain name that -can be used as the name of an AFS cell: -

        -

      • The cell name must be unique in order to distinguish your AFS cell from -all others in the AFS global namespace. -

      • The cell name can contain as many as 64 characters; however, shorter -names are recommended. -

      • The cell name must include only lowercase characters, numbers, -underscores, dashes, and periods to ensure portability between different -operating system types. -

      • The cell name can include any numbers or letters, which are conventionally -separated by periods. -

      • The cell name must end in a suffix that indicates the type of institution -to which it belongs. Some of the standard suffixes are -.com, for business and other commercial organizations, -.edu, for educational institutions such as universities, -.gov, for government institutions, and -.mil, for military institutions. -
      -

    5. In the Password box, enter the character string to serve as the -password for the AFS Server principal account in the cell -(afs). All AFS Servers obtain AFS tokens as this principal, -and the Authentication Server's Ticket Granting Service (TGS) module uses -this password to encrypt the server tickets that AFS Clients present to -servers during mutual authentication. -

    6. In the Verify password box, retype the initial AFS password for -the AFS Server principal account for this cell to confirm the password -selection. -

    7. Choose the Next button. The Administrative Information -dialog box appears. -

    8. In the Name box, enter a username to serve as a generic AFS -administrative account for this cell (generally, admin.) -

      - -Use of a generic administrative account means that you do not need to grant -privileges to each system administrator. Instead, each administrator -knows the name and password of this generic administrative account and uses -this identity to authenticate to AFS when performing tasks that require -administrative privileges. -

    9. In the Password box, enter a character string to serve as the -password for the AFS administrative account. -

    10. In the Verify password box, retype the password for the AFS -administrative account to confirm the password selection. -

    11. Specify the AFS User ID (UID) to assign to the AFS administrative -account: -
        -

      • (Recommended) To automatically assign the next available UID to the AFS -administrative account, choose the Use the next available AFS UID -option. -

      • To assign a specific UID to the AFS administrative account, choose the -Use this AFS ID option and enter the desired UID in the entry -box. -
        Note:It is not generally recommended that you assign a specific UID to a new AFS -account, unless you need to make the AFS UID match an existing UNIX -UID. -
        -
      -

    12. Choose the Next button. The File Service dialog box -appears. -

      - -AFS File Servers deliver requested files and data from the server to AFS -Clients. File Servers store files and data, handle requests for -copying, moving, creating, and deleting files and directories, and keep track -of status information about each file and directory on the server. -

      Because you are configuring the first AFS Server in a new cell, the File -Service must be configured on the server, and will be configured -automatically. -

    13. Choose the Next button. The Database Service dialog box -appears. -

      - -Every AFS cell must contain at least one Database Server. Each Database -Server runs the Database processes that maintain the AFS databases: the -Authentication Database, the Protection Database, the Volume Location -Database, and optionally the Backup Database. -

      Because you are configuring the first AFS Server in a new cell, the -Database Service must be configured on the server, and will be configured -automatically. -

    14. Choose the Next button. The Backup Server dialog box -appears. -

      - -A Backup Server maintains the Backup Database where information related to the -Backup system is stored. The Backup Server enables the AFS system -administrator to back up data in the AFS filespace from volumes to -tape. The data can then be restored from tape in the event that it is -lost from the file system (for example, if a system or disk failure causes -data to be lost). -

    15. Choose the Yes, configure as a Backup Server option if you want -to configure this AFS Server as a Backup Server. If you do not want to -configure this AFS Server as a Backup Server, choose the No, do not -configure as a Backup Server option. -
      Note:If the Backup Server is configured on any Database Server in the cell, it -must be configured on all Database Servers in the cell. -
      -

    16. Choose the Next button. The AFS Partition dialog box -appears. -

      - -Every AFS File Server must have at least one partition designated exclusively -to storing AFS volumes, and all AFS volumes must reside on partitions that -have been designated as AFS partitions. On a Windows NT machine, only -NTFS volumes can be designated as AFS partitions. In addition, AFS -partitions can be created only on NTFS volumes that are empty (or contain only -the Windows NT Recycle Bin). -

      Because you are configuring the first AFS Server in a new cell, you must -designate an AFS partition on the server. -

    17. In the list of NTFS volumes, choose the volume you want to designate as an -AFS partition. In the AFS Partition Name box, enter the last -part of the partition name. -
      Note:There can exist up to 256 AFS partitions on an AFS Server. By -convention, each partition is named /vicepx, where -x is one or two lowercase letters of the English alphabet. -AFS partitions can be named /vicepa, /vicepb, and so on -up to /vicepz. Additional partitions can be named -/vicepaa through vicepaz and so on up to -/vicepiv. -
      -

      It is strongly recommended that you use the NTFS volume drive letter as the -last letter of the partition name. -

    18. Choose the Next button. The Root AFS Volumes dialog box -appears. -

      - - - -The root AFS volumes are two volumes that every AFS cell must include in its -file system. They are named: -

        -

      • root.afs, for the volume corresponding to the top -(/afs) level of the AFS filespace -

      • root.cell, for the volume mounted just below -/afs at the cell's name (for example, -/afs/yourcompany.com in the -yourcompany.com cell) -
      -

      Because you are configuring the first AFS Server in a new cell, the -cell's root volumes must be created on the server, and will be created -automatically during the configuration of the server. -

    19. Choose the Next button. The Replication dialog box -appears. -

      - -If you want to be able to take advantage of the replication capabilities of -AFS, the AFS root volumes must be replicated. The replication process -creates one or more read-only copies of an AFS volume, and distributes these -copies to one or more other sites (AFS partitions and servers). -Replication increases system efficiency and improves data availability by -making the contents of an AFS volume accessible on one or more AFS File Server -machines. -

      Because you are configuring the first AFS Server in a new cell, the -cell's root volumes must be replicated on the server, and will be -replicated automatically during the configuration of the server. -

    20. Choose the Next button. The System Control Service -dialog box appears. -

      - -In cells running the domestic version of AFS for Windows, the System Control -Server distributes new versions of AFS Server configuration information to all -AFS servers. It is generally recommended that you designate the first -server in an AFS cell as the System Control Server. (Cells running the -international version of AFS for Windows do not use the System Control Server -to distribute system configuration files.) -
      Note:The role of System Control Server can later be assigned to a different server -machine if desired. However, depending on the number of AFS servers in -the cell, the process of assigning the role to another machine can be very -time-consuming. -
      -

    21. To configure this AFS Server as the System Control Server for the AFS -cell, choose the Configure as the System Control Server -option. If you do not want to configure this AFS Server as the System -Control Server for the AFS cell, choose the Do not configure as the -System Control Server option. -

    22. Choose the Next button. The Configure the System dialog -box appears. -

      A list of the steps that will be taken to configure this AFS Server is -displayed, enabling you to review the steps before starting the actual -configuration process. -
      Note:To return to a previous step to review or modify your selections, choose the -Back button. -
      -

    23. To begin configuration of the AFS Server on this machine, choose the -Configure button. The AFS Server is configured according to -your specifications. The progress bar at the bottom of the dialog box -indicates the steps in progress. A message box appears indicating that -configuration is complete. -
    -

    - -To configure the AFS Server into an existing AFS cell: -

      -

    1. From the Start menu, choose Programs, then choose -IBM AFS, then choose Server, and then choose -Configuration Wizard. The AFS Server Quick-Start -Wizard opens. -

    2. Choose the Next button. The Cell and Server Information -dialog box appears. -

    3. Choose the Make this host a server in an existing AFS cell -option. -

    4. In the Cell Name box, enter the name of the AFS cell to which -you want to add the new AFS Server. -

    5. Choose the Next button. The Administrative Information -dialog box appears. -

    6. In the Name box, enter the username of the AFS administrative -account, for example admin, or the username of an AFS user account -with administrative privileges. -

    7. In the Password box, enter the password for the AFS -administrative account or the AFS user account with administrative privileges -entered in the Name box. -

    8. In the AFS Server box, enter the hostname of a running AFS -Server in this AFS cell. AFS configuration information will be -retrieved from the server for use in configuring this new AFS Server. -

    9. Choose the Next button. The File Service dialog box -appears. -

      - -AFS File Servers deliver requested files and data from the server to AFS -Clients. File Servers store files and data, handle requests for -copying, moving, creating, and deleting files and directories, and keep track -of status information about each file and directory on the server. -

      To configure this AFS Server as a File Server, choose the Yes, -configure as a File Server option. If you do not want to -configure this AFS Server as a File Server, choose the No, do not -configure as a File Server option. -

    10. Choose the Next button. The Database Service dialog box -appears. -

      - -Every AFS cell must contain at least one Database Server. Each Database -Server runs the Database processes that maintain the AFS databases: the -Authentication Database, the Protection Database, the Volume Location -Database, and optionally the Backup Database. -

      To configure this AFS Server as a Database Server, choose the Yes, -configure as a Database Server option. If there is a System -Control Server in the AFS cell to which you are adding the server, enter its -hostname in the System Control Server box. AFS configuration -information (for example, the list of AFS Database Servers maintained in the -CellServDB file on each AFS Server machine) will be updated by this -server. If you do not want to configure this AFS Server as a Database -Server, choose the No, do not configure as a Database Server -option. -

    11. Choose the Next button. The Backup Server dialog box -appears. -

      - -A Backup Server maintains the Backup Database where information related to the -Backup system is stored. The Backup Server enables the AFS system -administrator to back up data in the AFS filespace from volumes to -tape. The data can then be restored from tape in the event that it is -lost from the file system (for example, if a system or disk failure causes -data to be lost). -
      Note:The Backup Server can only be configured on a machine that is configured as a -Database Server. Also, if the Backup Server is configured on any -Database Server in the cell, it must be configured on all Database -Servers in the cell. -
      -

    12. Choose the Yes, configure as a Backup Server option if you want -to configure this AFS Server as a Backup Server. If you do not want to -configure this AFS Server as a Backup Server, choose the No, do not -configure as a Backup Server option. -

    13. Choose the Next button. The AFS Partition dialog box -appears. -

      If you are configuring this AFS Server as a File Server, you must specify -an NTFS volume to designate as an AFS partition. Every AFS File Server -must have at least one partition designated exclusively to storing AFS -volumes, and all AFS volumes must reside on partitions that have been -designated as AFS partitions. On a Windows NT machine, only NTFS -volumes can be designated as AFS partitions. In addition, AFS -partitions can be created only on NTFS volumes that are empty (or contain only -the Windows NT Recycle Bin). -

      To designate a volume as an AFS partition, choose the Yes, create a -partition option. In the list of NTFS volumes, choose the volume -that you want to designate as an AFS partition. In the AFS -Partition Name box, enter the last part of the partition name. -
      Note:There can exist up to 256 AFS partitions on an AFS Server. By -convention, each partition is named /vicepx, where -x is one or two lowercase letters of the English alphabet. -AFS partitions can be named /vicepa, /vicepb, and so on -up to /vicepz. Additional partitions can be named -/vicepaa through vicepaz and so on up to -/vicepiv. -
      -

      It is strongly recommended that you use the NTFS volume drive letter as the -last letter of the partition name. -

      If you do not want to designate a volume as an AFS partition, choose the -No, do not create a partition option. -

    14. Choose the Next button. The Root AFS Volumes dialog box -appears. -

      The root AFS volumes are two volumes that every AFS cell must include in -its file system. They are named: -

        -

      • root.afs, for the volume corresponding to the top -(/afs) level of the AFS filespace -

      • root.cell, for the volume mounted just below -/afs at the cell's name (for example, -/afs/yourcompany.com in the -yourcompany.com cell) -
      - -Because you are adding this AFS Server to an existing AFS cell, the root AFS -volumes already exist in the cell, and the AFS Configuration Wizard indicates -that you do not need to create the root volumes. -
      Note:If for some reason the root AFS volumes do not yet exist in this AFS cell, -you can choose the Yes, create the root volumes option to create -the root volumes on this AFS Server. -
      -

    15. Choose the Next button. The Replication dialog box -appears. -

      If you want to be able to take advantage of the replication capabilities of -AFS, the AFS root volumes must be replicated. The replication process -creates one or more read-only copies of an AFS volume, and distributes these -copies to one or more other sites (AFS partitions and servers). -Replication increases system efficiency and improves data availability by -making the contents of an AFS volume accessible on one or more AFS File Server -machines. -

      Because you are adding this AFS Server to an existing AFS cell, the root -AFS volumes are probably already replicated, and the AFS Server Configuration -Wizard indicates that you do not need to replicate the root AFS -volumes. -
      Note:If for some reason the root AFS volumes are not yet replicated in this AFS -cell, you can choose the Yes, replicate the root volumes option to -replicate the AFS cell's root volumes on this AFS Server. -
      -

    16. Choose the Next button. The System Control Service -dialog box appears. -

      In cells running the domestic version of AFS for Windows, the System -Control Server distributes new versions of AFS Server configuration -information to all AFS servers and the System Control Client machines obtain -common AFS configuration files from the System Control machine. (Cells -running the international version of AFS for Windows do not use the System -Control Server to distribute system configuration files or the System Control -Client to obtain these files.) -

    17. To configure this AFS Server as the System Control Server for the AFS -cell, choose the Configure as the System Control Server -option. To configure this AFS Server as a System Control Client, choose -the Configure as a System Control Client option and enter the -hostname of the System Control Server in this AFS cell. The AFS Server -will obtain new versions of AFS Server configuration information from the -server specified. If you do not want to configure this AFS Server as -the System Control Server for the AFS cell or as a System Control Client, -choose the Do not configure as the System Control Client or Server -option. -

    18. Choose the Next button. The Configure the System dialog -box appears. -

      A list of the steps that will be taken to configure this AFS Server is -displayed, enabling you to review the steps before starting the actual -configuration process. -
      Note:To return to a previous step to review or modify your selections, choose the -Back button. -
      -

    19. To begin configuration of the AFS Server on this machine, choose the -Configure button. If you are configuring the AFS Server into -an AFS cell in which there are Database Servers running a version of AFS older -than version 3.5, a dialog box appears prompting you to enter the AFS -principal password. -

      The AFS Server is configured according to your specifications. The -progress bar at the bottom of the dialog box indicates the steps in -progress. A message box appears indicating that configuration is -complete. -

    -

    To Configure the AFS Control Center

    - - -
    Note:If you have installed the AFS Control Center in combination with the AFS -Server, or the AFS Client, or both, then you do not need to configure the AFS -Control Center. The AFS Control Center is automatically configured when -the AFS Server or AFS Client is configured. If you have installed the -AFS Control Center only, then the Control Center must be configured on your -system before it can be used. -
    -
      -

    1. From the Start menu, choose Settings, then choose -Control Panel. -

    2. Double-click the AFS Control Center icon. The AFS -Control Center Properties dialog box appears. -

    3. In the Default Cell box, enter the full name of the AFS cell to -be administered by default. -

    4. If the cell to be administered by the AFS Control Center is not listed in -the list of AFS cells, choose the Add button. The New Cell -dialog box opens. Enter the cell name in the AFS Cell box -and a short description in the Description box. -

      Choose the Add button. The Add Server dialog box -opens. In the Server Name box, enter the name of a Volume -Location Server in the selected cell. Choose OK to close the -Add Server dialog box. Repeat this process, adding information for all -Volume Location Servers in the cell. After all server information has -been entered, choose OK to close the New Cell dialog box. -

    5. Choose OK to close the AFS Control Center Properties dialog -box. -
    -

    The AFS Control Center is now configured. - -

    Uninstalling AFS for Windows

    -

    This section outlines uninstallation prerequisites, provides -instructions for uninstalling AFS for Windows, and lists the changes that the -uninstallation process makes to your system. - - -

    Reinstalling and Upgrading

    -

    On a Windows NT machine, it is not necessary to uninstall -the components of AFS for Windows for the purpose of reinstalling or upgrading -the software. To reinstall or upgrade AFS for Windows, follow the -installation procedure described in To Install AFS for Windows. During the installation process, the -previously-installed AFS components are replaced. AFS configuration -information is preserved. -

    On a Windows 95 or Windows 98 machine, you must uninstall the -previously-installed AFS Light component, as described in To Uninstall AFS for Windows, before reinstalling or upgrading AFS Light. - - - -

    Uninstallation Prerequisites

    -

    Uninstalling AFS results in the deletion of all AFS application -files. These files cannot be deleted if other applications are using -them. For this reason, you must close all AFS dialog boxes before -uninstalling AFS for Windows. -

    If you are uninstalling the AFS Server for the purpose of decommissioning -the machine, the following prerequisites are necessary to avoid loss of -data: -

      -

    1. If the AFS Server is functioning as a File Server, move all read/write -volumes to another AFS File Server, and remove all read-only volumes. -

    2. Unconfigure the AFS Server. Open the AFS Server Configuration -utility and choose the Server tab. Clear all check boxes and -choose OK. -
    - - - - - - - -

    To Uninstall AFS for Windows

    -
      -

    1. From the Start menu, choose Settings, then choose -Control Panel. -

    2. Double-click the Add/Remove Programs icon. The -Add/Remove Programs Properties dialog box appears, displaying the -Install/Uninstall tab. -

    3. Close the Control Panel. -

    4. Select the AFS component to be uninstalled, and select the -Add/Remove button. The Confirm File Deletion dialog box -appears, verifying that you want to remove the selected AFS for Windows -component. Click Yes to continue with the uninstallation -procedure. -

    5. An AFS message box appears asking if you want to preserve configuration -information. Select Yes to preserve configuration -information or No to delete all configuration information. -(No configuration information is associated with the AFS Supplemental -Documentation component. If you are removing this component from your -system, the AFS message box does not appear.) -

    6. The Remove Programs from your Computer dialog box opens, displaying the -components being removed from your system. -
      Note:A message box can possibly appear asking if you want to remove shared AFS -files that are no longer needed by other components. Click Yes To -All to completely remove the selected AFS component. -
      -
    -

    The selected AFS for Windows component is now uninstalled. If you -installed a combination of AFS for Windows components, you must repeat Steps -4-6 to remove each component separately. -

    Changes Made to Your System

    - -

    Changes made to your system by uninstalling the AFS Client

    -

    Uninstalling the AFS Client makes the following changes to your -system: -

    -

    Changes made to your system by uninstalling AFS Light

    -

    Uninstalling AFS Light makes the following changes to your -system: -

    -

    Changes made to your system by uninstalling the AFS Server

    -

    Uninstalling the AFS Server makes the following changes to your -system: -

    -

    Changes made to your system by uninstalling the AFS Control Center

    -

    Uninstalling the AFS Control Center makes the following changes to your -system: -

    -

    Changes made to your system by uninstalling the AFS supplemental documentation

    -

    Uninstalling the AFS supplemental documentation makes the following -changes to your system: -

    -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg004.htm b/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg004.htm deleted file mode 100755 index 507c334a0e..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/InstallGd/awqbg004.htm +++ /dev/null @@ -1,341 +0,0 @@ - - -Quick Beginnings - - - - - - - - - - - -

    Quick Beginnings

    -

    [Return to Library] [Contents] [Previous Topic] [Bottom of Topic]

    -

    -

    Index

    -A -B -C -D -F -G -I -L -M -O -R -S -U -
    -A - -
  • AFS - -
  • client - -
  • overview -(1) -
    •  -
  • components -(1) -
  • configuration - -
  • AFS Client -(1) -
  • AFS Control Center -(1) -
  • AFS Light -(1) -
  • AFS Light Gateway -(1) -
  • AFS Server -(1) -
  • overview -(1) -
    •  -
  • control center - -
  • overview -(1) -
    •  -
  • installation options -(1) -
  • installation procedure -(1) -
  • light - -
  • overview -(1) -
    •  -
  • overview -(1) -
  • reinstalling -(1) -
  • server - -
  • overview -(1) -
    •  -
  • supplemental documentation component -(1) -
  • uninstallation prerequisites -(1) -
  • uninstallation procedure -(1) -
  • upgrading -(1) -
    •  -
  • AFS Client -(1) - -
  • setup.co file -
  • client-only installation -(1) -
  • configuration -(1) -
  • configure as AFS Light Gateway -(1) -
  • installation -(1) -
  • overview -(1) -
  • uninstallation -(1) -
    •  -
  • AFS Control Center - -
  • configuration -(1) -
  • installation -(1) -
  • overview -(1) -
  • uninstallation -(1) -
    •  -
  • AFS Light - -
  • configuration -(1) -
  • gateway machine -(1) -
  • installation -(1) -
  • overview -(1) -
  • uninstallation -(1) -
    •  -
  • AFS Light Gateway - -
  • authenticating AFS Light users -(1) -
  • configuration -(1) -
  • synchronizing the cell database -(1) -
    •  -
  • AFS partitions -(1) -
  • AFS Server - -
  • configuration - -
  • as first server in a cell -(1) -
  • as server in an existing cell -(1) -
  • overview -(1) -
    •  -
  • installation -(1) -
  • overview -(1) -
  • uninstallation -(1) -
    •  -
  • audience -(1) -
    •  -B - -
  • Backup Server - -
  • configuring in a new cell -(1) -
  • configuring in an existing cell -(1) -
    •  -
    •  -C - -
  • CD-ROM documentation -(1) -
  • client - -
  • overview -(1) -
    •  -
  • client-only installation -(1) -
  • configuration -(1) -
  • control center - -
  • overview -(1) -
    •  -
    •  -D - -
  • Database Server - -
  • configuring in a new cell -(1) -
  • configuring in an existing cell -(1) -
    •  -
  • documentation - -
  • CD-ROM -(1) -
  • online -(1) -
  • online help -(1) -
    •  -
  • domain user accounts -(1) -
    •  -F - -
  • File Server - -
  • configuring in a new cell -(1) -
  • configuring in an existing cell -(1) -
    •  -
    •  -G - -
  • gateway machine name -(1) -
  • generic administrative account -(1) -
    •  -I - -
  • installation - -
  • changes made to your system -(1) -
  • client-only installation -(1) -
  • possible component combinations -(1) -
  • procedure -(1) -
  • upgrading from an earlier version -(1) -
    •  -
  • installation options -(1) -
  • installation procedure -(1) -
    •  -L - -
  • light - -
  • overview -(1) -
    •  -
    •  -M - -
  • machine user accounts -(1) -
    •  -O - -
  • online documentation -(1) -
  • online help -(1) -
  • overview - -
  • AFS -(1) -
  • document -(1) -
    •  -
    •  -R - -
  • reinstalling -(1) -
  • replication - -
  • when configuring a new cell -(1) -
    •  -
  • root AFS volumes - -
  • when configuring a new cell -(1) -
  • when configuring a server in an existing cell -(1) -
    •  -
  • root.afs -(1) -
  • root.cell -(1) -
    •  -S - -
  • server - -
  • overview -(1) -
    •  -
  • setup.co file -(1) -
  • System Control Server - -
  • in a new AFS cell -(1) -
    •  -
    •  -U - -
  • uninstallation - -
  • changes made to your system -(1) -
  • overview -(1) -
  • prerequisites -(1) -
  • procedure -(1) -
    •  -
  • uninstallation prerequisites -(1) -
  • uninstallation procedure -(1) -
  • upgrading -(1) -
    •  -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns000.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns000.htm deleted file mode 100755 index 11d0e209a4..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns000.htm +++ /dev/null @@ -1,43 +0,0 @@ - - -Release Notes - - - - - - - - - - - -

    Release Notes

    -

    [Return to Library] [Table of Contents] [Bottom of Topic] [Next Topic] [Index]

    -AFS for Windows
    -Release Notes
    -

    Version 3.6 -

    Document Number GC09-4559-00 -

    0000000 -

    First Edition (April 2000) -

    This edition applies to: -

    -
    IBM AFS for Windows, Version 3.6 -
    -

    and to all subsequent releases and modifications until otherwise indicated -in new editions. -

    This softcopy version is based on the printed edition of this book. -Some formatting amendments have been made to make this information more -suitable for softcopy. -

    Order publications through your IBM representative or through the IBM -branch office serving your locality. -

    © Copyright International Business Machines Corporation 2000. All rights reserved. -

    -

    [Return to Library] [Table of Contents] [Top of Topic] [Next Topic] [Index]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns002.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns002.htm deleted file mode 100755 index 89f33369b6..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns002.htm +++ /dev/null @@ -1,135 +0,0 @@ - - -Release Notes - - - - - - - - - - - -

    Release Notes

    -

    [Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index]

    -

    Table of Contents

    -

    Introduction
    -

    -
  • Overview -
  • About the Release Notes - -
  • Audience -
  • Document Organization -
    •  -

    AFS Client Release Notes
    -

    -
  • Introduction -
  • AFS Client Installation Requirements - -
  • Hardware -
  • Software -
  • Administrative Privilege Requirement -
    •  -
  • Product Notes - -
  • Additional Configuration Options Available Via the Client Interface -
  • AFS Client Cache Location Is Now Configurable -
  • Mapping Global Drives to the AFS Filespace -
  • AFS Client Computer Name Must Correspond to the Name Service Host Name -
  • AFS Command-Line Binaries -
  • The AFS Client Must Be Installed in a Directory Whose Path Contains Only ANSI Characters -
  • Disabling All but the Client Component of the AFS for Windows Setup Program -
  • Temporary Files -
  • National Language Support for the AFS Client -
  • The kpwvalid Password Strength Checker Is Not Used on Windows Systems -
  • Configurable LAN Adapter Number -
  • WinLogon Graphical Identification and Authentication (GINA) Modules and AFS Authentication -
  • Cell Database Is Maintained During Upgrade -
    •  -
  • Limitations and Restrictions - -
  • Symbolic Links to AFS Files and Directories -
  • AFS Client Can Fail to Load When Network Drives Are in the Application Path -
    •  -

    AFS Light Release Notes
    -

    -
  • Introduction -
  • AFS Light Installation Requirements - -
  • Hardware -
  • Software -
  • Administrative Privilege Requirement -
    •  -
  • Product Notes - -
  • Accessing AFS via the AFS Light Gateway -
  • AFS Light for Windows 95 Requires the Windows Sockets 2 Update -
  • AFS Command-Line Binaries -
  • AFS Light Must Be Installed in a Directory Whose Path Contains Only ANSI Characters -
  • Temporary Files -
  • National Language Support for AFS Light -
  • The kpwvalid Password Strength Checker Is Not Used on Windows Systems -
    •  -
  • Limitations and Restrictions - -
  • Encryption Not Supported in Simplified Chinese Version -
  • Symbolic Links to AFS Files and Directories -
    •  -

    AFS Server Release Notes
    -

    -
  • Introduction -
  • AFS Server Installation Requirements - -
  • Hardware -
  • Software -
  • Administrative Privilege Requirement -
    •  -
  • Product Notes - -
  • Support for Volumes That Are Greater Than 2 GB -
  • Encryption Routines Used by the System Control Server Are Included with All Versions of AFS for Windows -
  • AFS Server Computer Name Must Correspond to the Name Service Host Name -
  • Time Clock Synchronization -
  • Securing AFS Server Machines -
  • Shutting Down AFS File Server Machines -
  • Obtaining Crash Dump Files in the Event of Server Problems -
  • The AFS Server Must Be Installed in a Directory Whose Path Contains Only ANSI Characters -
  • Temporary Files -
  • National Language Support for the AFS Server -
  • The kpwvalid Password Strength Checker Is Not Used on Windows Systems -
  • Configuring a Server into a Cell with pre-3.5 Database Servers Requires the Principal Password -
    •  -
  • Limitations and Restrictions - -
  • AFS bosserver Process Does Not Execute the Notifier Program When a Process Terminates -
    •  -

    AFS Control Center Release Notes
    -

    -
  • Introduction -
  • AFS Control Center Installation Requirements - -
  • Hardware -
  • Software -
  • Administrative Privilege Requirement -
    •  -
  • Product Notes - -
  • The AFS Control Center Must Be Installed in a Directory Whose Path Contains Only ANSI Characters -
  • Temporary Files -
  • National Language Support for the AFS Control Center -
  • The kpwvalid Password Strength Checker Is Not Used on Windows Systems -
  • Tokens Obtained for Control Center Applications Expire after 25 Hours -
  • Server Manager Displays All Server Entries Referenced in the Volume Location Database (VLDB) -
    •  -
  • Limitations and Restrictions -

    • -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns003.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns003.htm deleted file mode 100755 index acc35b39fd..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns003.htm +++ /dev/null @@ -1,98 +0,0 @@ - - -Release Notes - - - - - - - - - - - -

    Release Notes

    -

    [Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index]

    -

    Introduction

    -

    Overview

    -

    AFS(R) is a distributed file system that provides -secure, reliable access to information across an enterprise. By -seamlessly uniting the directories and files on individual file server -machines into one file system accessible from any desktop, AFS presents users -with a single filespace independent of machine boundaries. -

    AFS offers several advantages. It improves the availability of files -by employing client-side caching and replication of frequently accessed data -across multiple file servers. AFS provides powerful security to protect -the information stored in the filespace. In addition, AFS is highly -scalable. Virtually unlimited additional server and client machines can -be added as needed to an AFS configuration with little impact on existing -server and client machines. This enables the file system to grow with -the enterprise. -

    AFS for Windows includes the following products: -

    -

    About the Release Notes

    -

    This document contains important information about AFS for Windows, -version 3.6. This document summarizes the installation -prerequisites, product notes, and specific limitations and restrictions of -this release. -

    -
    Note:AFS for Windows users can view the README.txt file to check -for any additional AFS for Windows information that became available since the -writing of this document. The README.txt file is -installed in the AFS for Windows -Installation\documentation directory when AFS for Windows is -installed. -
    -

    Audience

    -

    This document is written for system administrators responsible for the -installation, configuration, and use of the products included in AFS for -Windows. This document assumes that readers are familiar with system -administration in general and with the use of AFS. -

    Document Organization

    -

    The document has the following organization: -

    -

    Each section describes installation requirements, product notes, and -limitations and restrictions for the specified AFS for Windows -component. Also, where applicable, descriptions of new features and -enhancements that are made available in this release of AFS for Windows are -included. -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns004.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns004.htm deleted file mode 100755 index d640a7552a..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns004.htm +++ /dev/null @@ -1,238 +0,0 @@ - - -Release Notes - - - - - - - - - - - -

    Release Notes

    -

    [Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index]

    -

    AFS Client Release Notes

    -

    Introduction

    -

    This section contains important information about the AFS Client -component of AFS for Windows, version 3.6. The AFS Client -provides direct access to the AFS filespace from a PC running Windows NT, -enabling users to manage files and directories in AFS. The AFS Client -includes the AFS Light Gateway, which enables AFS Light users to access the -AFS filespace. -

    AFS Client Installation Requirements

    -

    Your system must meet the following hardware, software, and -administrative privilege requirements to install the AFS Client. -

    Hardware

    -

    The hardware requirements for installing the AFS Client are: -

    -

    Software

    -

    The software requirements for installing the AFS Client are: -

    -

    Administrative Privilege Requirement

    -

    You must be a member of the local Administrators group on -your Windows system in order to install, configure, and start the AFS -Client. -

    Product Notes

    -

    This section highlights important general information about the AFS -Client component of AFS for Windows, version 3.6. It includes -descriptions of new features and enhancements made available in this release -of the AFS Client. -

    Additional Configuration Options Available Via the Client Interface

    -

    The AFS Client Configuration utility's Advanced tab now -includes options for configuring logon parameters, diagnostic parameters, and -other miscellaneous configuration parameters. From the -Advanced tab, you can also configure global drive mappings. -Many of these configuration options were formerly available to AFS Client -users as registry settings. -

    The Advanced tab is accessed from the Windows Control -Panel. To display the Advanced tab: -

      -

    1. From the Start menu, choose Settings, then choose -Control Panel. -

    2. Double-click the AFS Client Configuration icon to display the -AFS Client Configuration utility. -

    3. Choose the Advanced tab. -
    -

    AFS Client Cache Location Is Now Configurable

    -

    The AFS Client Cache is stored in a file named AFSCache, -rather than in the system paging file. By default, the cache is stored -on the drive where Windows is installed. The size of the AFS Client -Cache is limited by available free disk space. The cache size must be -at least 1 MB. The default cache size is 20480 KB (20MB). -

    The location of the AFS Client Cache can now be changed. Changing -the cache location is useful when there is not sufficient available free disk -space on the drive where Windows is installed. To change the cache -location, enter a valid, fully qualified filename in the Cache Path -field on the AFS Client Configuration's Advanced tab. -

    Mapping Global Drives to the AFS Filespace

    -

    The AFS Client's graphical user interface can now be used to map -global drives to places in the AFS filespace. Global drives are mapped -to the AFS filespace when the IBM AFS Client service starts; users are -not required to be logged on. To map global drives to AFS: -

      -

    1. From the Start menu, choose Settings, then choose -Control Panel. -

    2. Double-click the AFS Client Configuration icon to display the -AFS Client Configuration utility. Select the Advanced -tab. -

    3. Click Add. The Map Global Drive dialog box -appears. In the Drive Letter box, choose a network drive or -accept the default. In the AFS Path box, type a path to the -AFS filespace. If desired, enter a short name to be associated with the -specified drive letter and AFS path in the Description box. -Note that a drive letter description can have no more than 12 characters and -cannot contain spaces or tabs. -

    4. Click OK to establish the connection. The drive letter -and AFS path appear on the Global Drives dialog box. The drive letter -now appears in your Windows NT Explorer. -
    -

    AFS Client Computer Name Must Correspond to the Name Service Host Name

    -

    The computer name of an AFS Client machine (as displayed in the -Computer Name field on the Identification tab of the -Network dialog box) must correspond to the host name assigned to the computer -by the name service (normally the Domain Name Service, or DNS) used to map -names to Internet Protocol (IP) addresses. For example, if the machine -on which the AFS Client is installed has the computer name -afsclient1 and is in the yourcompany.com domain, -the corresponding DNS entry for the machine must be -afsclient1.yourcompany.com. -

    AFS Command-Line Binaries

    -

    The AFS Client includes administration-oriented command suites such as -bos, kas, vos, and pts. -Execute the commands within these suites from the Windows Command -Prompt. -

    The AFS Client Must Be Installed in a Directory Whose Path Contains Only ANSI Characters

    -

    The AFS for Windows software must be installed in a directory whose -path contains only ANSI characters, for example the default directory -C:\Program Files. -

    Disabling All but the Client Component of the AFS for Windows Setup Program

    -

    You have the option of altering the AFS for Windows setup program to -disable all but the client component. Such a client-only setup program -renders users unable to install any components other than the AFS -Client. To perform a client-only installation, create the file -setup.co in the same directory as the other installation -files; the setup program then allows only the AFS Client to be -installed. Note that the contents of the setup.co -file are irrelevant. Follow the installation procedure described in -IBM AFS for Windows Quick Beginnings regardless of the type of -installation you are performing. -

    Temporary Files

    -

    The AFS Client for Windows occasionally creates temporary files. -To control where such files are created, set your environment variable (TMP or -TEMP) to the fully qualified path of the preferred temporary directory. -If you do not specify a temporary directory, then any temporary files are -created in the current working directory of the process that creates the -files. -

    National Language Support for the AFS Client

    -

    AFS provides national language support for the AFS Client graphical -user interface (GUI) tools and documentation, including support for -bidirectional scripts (Hebrew, Arabic, etc.). The language -strings installed are determined by your machine's system default locale, -as specified in the Control Panel's Regional Settings Properties dialog -box. If no language strings exist for the current locale, then English -language strings are installed by default. -
    Note:The system default locale for a machine can be different than the -user locale (specified by a user) on the machine. However, -the language strings installed with AFS for Windows are always determined by -the system default locale. -
    -

    The kpwvalid Password Strength Checker Is Not Used on Windows Systems

    -

    When an AFS user password is changed from a Windows system, the -kpwvalid program is not used to check the quality of the -new password. (On UNIX systems, if a kpwvalid program exists -in the same directory as the kpasswd program, the -kpwvalid program checks the quality of every new user -password.) -

    Configurable LAN Adapter Number

    -

    The LAN Adapter (LANA) number used by the AFS Client service must match -the LANA number setting on your Windows system. By default, the AFS -Client service is configured to use LANA number 0 (zero). -

    You can now use the AFS Client's graphical user interface tools to -modify the value of the LANA number used by the AFS Client service. To -change the LANA number, enter a new value in the Lan Adapter Number -field on the AFS Client Configuration's Advanced tab. -You must restart the AFS Client service after modifying this parameter. -

    Alternatively, if you do not want to change the default LANA number used by -the AFS Client service to match the NetBIOS Configuration of your Windows NT -machine, you can instead modify your system's LANA number setting to -match the AFS default setting (0). Access the -Services tab on the Control Panel's Network -application. Choose NetBIOS Interface, and select the -Properties button. Enter 0 (zero) in the -Lana Number field. You must restart your machine after -making changes to this Windows setting. -

    WinLogon Graphical Identification and Authentication (GINA) Modules and AFS Authentication

    -

    The AFS Client includes the header files and libraries required to -build a WinLogon Graphical Identification and Authentication (GINA) module -that obtains AFS tokens. These header files and libraries are installed -in the <AFS for Windows Installation -Directory>\afs\client\program directory. In addition, -a sample program with compiling and linking instructions is provided in -<AFS for Windows Installation -Directory>\afs\client\program\sample\token.c. -

    Cell Database Is Maintained During Upgrade

    -

    When the AFS Client software is upgraded, the AFS Client cell database -file (afsdcell.ini) located in the Windows -directory is not replaced, in order to preserve local cell configuration -information. However, a copy of the cell database as distributed by the -vendor is installed in the AFS Client program directory. -

    -

    Limitations and Restrictions

    -

    This section briefly describes the known limitations and restrictions -in the AFS Client component of AFS for Windows, version 3.6. -

    Symbolic Links to AFS Files and Directories

    -

    Symbolic links to directories are treated as directories, and symbolic -links to files appear as files in Windows NT systems. Neither appear as -links. -

    Currently, you cannot use the Windows interface (the Windows NT Explorer, -for example) to delete symbolic links or create symbolic links in the AFS -filespace. If you attempt to delete a directory that is a symbolic link -using the Windows interface, the directory's contents are deleted. -The directory itself is not deleted. If you attempt to delete a file -that is a symbolic link using the Windows interface, the link is removed, -rather than the target file. -

    To create and delete symbolic links to AFS files and directories, use the -symlink.exe program that is provided with AFS for Windows, -version 3.6. Execute symlink commands from your -Windows NT Command Prompt. -

    AFS Client Can Fail to Load When Network Drives Are in the Application Path

    -

    When loading an application (such as the AFS Client), Windows NT -searches for the application's dynamic-link libraries (DLLs). One -of the places that Windows searches for an application's DLLs is in each -directory specified in the Path environment variable. In the Path -environment variable, if a network path is defined before the path that -contains a DLL, the application can possible fail to load. -

    Most services (such as the AFS Client) do not have security access to -network drives specified in the Path environment variable. When a -network drive is encountered in the path and the application does not have the -permission to access the network, Windows fails to distinguish between an -Access Denied error caused by a process which cannot access a file and a -process which cannot access the network drive that contains the file. -Because this distinction cannot be made, the operating system assumes that the -file exists but cannot be accessed by the process. This error causes -the system to discontinue the search for the DLLs and assume that a DLL cannot -be accessed. Since Windows believes that a DLL is inaccessible, it -fails to load the application. -

    In order to avoid this problem, ensure that the directory to an -application's DLLs comes before any network drives in the path. -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns005.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns005.htm deleted file mode 100755 index 6da536f0ba..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns005.htm +++ /dev/null @@ -1,179 +0,0 @@ - - -Release Notes - - - - - - - - - - - -

    Release Notes

    -

    [Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index]

    -

    AFS Light Release Notes

    -

    Introduction

    -

    This section contains important information about the AFS Light -component of AFS for Windows, version 3.6. AFS Light provides -access to the AFS filespace from a PC running Windows 95 or Windows 98, -enabling users to manage files and directories in AFS. AFS Light -accesses the AFS filespace via an AFS Client machine that is configured as an -AFS Light Gateway. -

    AFS Light Installation Requirements

    -

    Your system must meet the following hardware, software, and -administrative privilege requirements to install AFS Light. -

    Hardware

    -

    The hardware requirements for installing AFS Light are: -

    -

    Software

    -

    The software requirements for installing AFS Light are: -

    -

    Administrative Privilege Requirement

    -

    No administrative privileges are required to install and configure AFS -Light. -

    Product Notes

    -

    This section highlights important general information about the AFS -Light component of AFS for Windows, version 3.6. -

    Accessing AFS via the AFS Light Gateway

    -

    AFS Light accesses the AFS filespace through an AFS Light -Gateway. In order to use AFS Light, you must have at least one machine -in the same domain as the AFS Light machine running the AFS Client for -Windows, version 3.5 or the AFS Client for Windows, version -3.6. -

    -

    AFS Light for Windows 95 Requires the Windows Sockets 2 Update

    -

    To run AFS Light on a Windows 95 machine, you must install the Windows -Sockets 2 update if it is not yet installed. This update is available -for download from the Microsoft Web site. -

    AFS Command-Line Binaries

    -

    When installed on a Windows 98 system, AFS Light includes -administration-oriented command suites such as bos, kas, -vos, and pts. Execute the commands within these -suites from the Windows Command Prompt. The command suites are -not available when AFS Light is installed on a Windows 95 -system. -

    -

    AFS Light Must Be Installed in a Directory Whose Path Contains Only ANSI Characters

    -

    The AFS for Windows software must be installed in a directory whose -path contains only ANSI characters, for example the default directory -C:\Program Files. -

    Temporary Files

    -

    AFS Light for Windows occasionally creates temporary files. To -control where such files are created, set your environment variable (TMP or -TEMP) to the fully qualified path of the preferred temporary directory. -If you do not specify a temporary directory, then any temporary files are -created in the current working directory of the process that creates the -files. -

    National Language Support for AFS Light

    -

    AFS provides national language support for the AFS Light graphical user -interface (GUI) tools and documentation, including support for bidirectional -scripts (Hebrew, Arabic, etc.). The language strings installed -are determined by your machine's system default locale, as specified in -the Control Panel's Regional Settings Properties dialog box. If no -language strings exist for the current locale, then English language strings -are installed by default. -
    Note:The system default locale for a machine can be different than the -user locale (specified by a user) on the machine. However, -the language strings installed with AFS for Windows are always determined by -the system default locale. -
    -

    The kpwvalid Password Strength Checker Is Not Used on Windows Systems

    -

    When an AFS user password is changed from a Windows system, the -kpwvalid program is not used to check the quality of the -new password. (On UNIX systems, if a kpwvalid program exists -in the same directory as the kpasswd program, the -kpwvalid program checks the quality of every new user -password.) -

    Limitations and Restrictions

    -

    This section briefly describes the known limitations and restrictions -in the AFS Light component of AFS for Windows, version 3.6. -

    Encryption Not Supported in Simplified Chinese Version

    -

    The Simplified Chinese version of Microsoft Windows 98 does not support -encryption, which is needed to transmit AFS passwords from AFS Light to the -AFS Light Gateway. In order for AFS Light users to obtain AFS tokens -when using the Simplified Chinese version of Microsoft Windows 98, encryption -in AFS must be disabled. -

    To disable encryption in AFS, add the following line to your Windows -Autoexec.bat file: -

    set AFS_RPC_ENCRYPT=OFF
-
    -

    Note that disabling encryption introduces a potential security risk because -AFS passwords are transmitted to the AFS Client Gateway in an unencrypted form -when tokens are obtained. -

    Symbolic Links to AFS Files and Directories

    -

    Symbolic links to directories are treated as directories, and symbolic -links to files appear as files in Windows 98 and Windows 95 systems. -Neither appear as symbolic links. -

    Currently, you cannot use the Windows interface (the Windows Explorer, for -example) to delete symbolic links or create symbolic links in the AFS -filespace. If you attempt to delete a directory that is a symbolic link -using the Windows interface, the directory's contents are deleted. -The directory itself is not deleted. If you attempt to delete a file -that is a symbolic link using the Windows interface, the link is removed, -rather than the target file. -

    To create and delete symbolic links to AFS files and directories, use the -symlink.exe program that is provided with AFS for Windows, -version 3.6. Execute symlink commands from your -Windows NT Command Prompt. -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns006.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns006.htm deleted file mode 100755 index 450ab152ef..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns006.htm +++ /dev/null @@ -1,209 +0,0 @@ - - -Release Notes - - - - - - - - - - - -

    Release Notes

    -

    [Return to Library] [Contents] [Previous Topic] [Bottom of Topic] [Next Topic] [Index]

    -

    AFS Server Release Notes

    -

    Introduction

    -

    This section contains important information about the AFS Server -component of AFS for Windows, version 3.6. The AFS Server runs -AFS server processes on a Windows NT machine. An AFS Server on a -Windows NT machine can be configured as one or more of the following: an -AFS File Server, an AFS Database Server, an AFS Backup Server, and an AFS -System Control Server. -

    AFS Server Installation Requirements

    -

    Your system must meet the following hardware, software, and -administrative privilege requirements to install the AFS Server component of -AFS for Windows. -

    Hardware

    -

    The hardware requirements for installing the AFS Server are: -

    -

    Software

    -

    The software requirements for installing the AFS Server are: -

    -

    Administrative Privilege Requirement

    -

    You must be a member of the local Administrators group on -your Windows system in order to install, configure, and start the AFS -Server. -

    Product Notes

    -

    This section highlights important general information about the AFS -Server component of AFS for Windows, version 3.6. Included in -this section are descriptions of new features and enhancements made available -in this release of the AFS Server. -

    Support for Volumes That Are Greater Than 2 GB

    -

    An AFS volume is a collection of related files that are organized into -a single, easily managed unit and that can be easily moved between File Server -machines to facilitate load balancing across the network. Each AFS -volume has a specific quota associated with it. A volume's quota -specifies the maximum amount of disk space the information in the volume can -occupy. Quota is set on a per volume basis, so it can be increased for -volumes that contain more data and decreased for volumes that do not need the -additional space. AFS for Windows, version 3.6 now supports -volumes with quotas greater than 2 GB. -

    Encryption Routines Used by the System Control Server Are Included with All Versions of AFS for Windows

    -

    Encryption routines used by the Update Service on the System Control -Server machine are now being included with all versions of AFS for -Windows due to the relaxation of United States government export -regulations. Previously, government regulations prohibited the export -of these encryption routines. Thus, sites that were not running the -United States distribution of AFS were not able to use a System Control Server -to distribute configuration files, because doing so permitted sensitive system -information to be transmitted unencrypted. Now, all sites can use a -System Control Server machine to distribute new versions of AFS Server -configuration information to all AFS File Server machines. -

    AFS Server Computer Name Must Correspond to the Name Service Host Name

    -

    The computer name of an AFS Server machine (as displayed in the -Computer Name field on the Identification tab of the -Network dialog box) must correspond to the host name assigned to the computer -by the name service (normally the Domain Name Service, or DNS) used to map -names to Internet Protocol (IP) addresses. For example, if the machine -on which the AFS Server is installed has the computer name -afsserver1 and is in the yourcompany.com domain, -the corresponding DNS entry for the machine must be -afsserver1.yourcompany.com. -

    Time Clock Synchronization

    -

    To support security and database replication protocols, the time clocks -on all machines running AFS servers must be synchronized. Time -synchronization software can be obtained from numerous sources; for -example, Microsoft distributes the timeserv time synchronization -service with the Windows NT Server Resource Kit. -

    Securing AFS Server Machines

    -

    If the machine on which the AFS Server software is installed is not -secure (that is, if nonadministrative personnel are able to log into the -machine), then it is strongly recommended that the AFS Server software -directories and all AFS partitions on the machine be secured as appropriate -for the environment and file system type. However, when securing AFS -Server machines, ensure that the Windows NT local SYSTEM principal -has full access to the AFS software and all AFS partitions; otherwise AFS -processes will not be able to run. -

    Shutting Down AFS File Server Machines

    -

    Before shutting down a Windows NT machine that is running as an AFS -File Server, always stop the AFS File Server on the machine. -

    When the AFS File Server is started on a machine, the process creates a -salvage file. When the File Server is stopped manually, this salvage -file is removed. However, if a Windows NT machine is shut down while -the AFS File Server is still running, this salvage file is not removed. -When the machine is subsequently restarted, the File Server starts -automatically and, upon noticing the presence of the salvage file, executes -the Salvager. Because running the Salvager can be very time consuming, -it is always preferable to stop the AFS File Server on a machine before -shutting the machine down to avoid unnecessarily executing the Salvager -process. -

    Use one of the following procedures to shut down the AFS File Server on a -Windows NT machine. -

    -

    -
    Note:In general, machines that are running as AFS File Servers are shut down only -to perform preventative maintenance. -
    -

    Obtaining Crash Dump Files in the Event of Server Problems

    -

    It is recommended that you configure all AFS Server machines to create -a crash dump file in the event of a server failure. This information is -important for technical support personnel to use in order to diagnose a server -problem. Consult your Microsoft Windows NT documentation for -information on how to configure the Dr. Watson utility to generate a -binary crash dump file automatically when an application error occurs. -

    The AFS Server Must Be Installed in a Directory Whose Path Contains Only ANSI Characters

    -

    The AFS for Windows software can only be installed in a directory whose -path contains only ANSI characters, for example the default directory -C:\Program Files. -

    Temporary Files

    -

    The AFS Server for Windows occasionally creates temporary files. -To control where such files are created, set your environment variable (TMP or -TEMP) to the fully qualified path of the preferred temporary directory. -If you do not specify a temporary directory, then any temporary files are -created in the current working directory of the process that creates the -files. -

    National Language Support for the AFS Server

    -

    AFS provides national language support for the AFS Server graphical -user interface (GUI) tools and documentation, including support for -bidirectional scripts (Hebrew, Arabic, etc.). The language -strings installed are determined by your machine's system default locale, -as specified in the Control Panel's Regional Settings Properties dialog -box. If no language strings exist for the current locale, then English -language strings are installed by default. -
    Note:The system default locale for a machine can be different than the -user locale (specified by a user) on the machine. However, -the language strings installed with AFS for Windows are always determined by -the system default locale. -
    -

    The kpwvalid Password Strength Checker Is Not Used on Windows Systems

    -

    When an AFS user password is changed from a Windows system, the -kpwvalid program is not used to check the quality of the -new password. (On UNIX systems, if a kpwvalid program exists -in the same directory as the kpasswd program, the -kpwvalid program checks the quality of every new user -password.) -

    Configuring a Server into a Cell with pre-3.5 Database Servers Requires the Principal Password

    -

    If you configure the AFS Server for Windows, version 3.6, into -an AFS cell in which the Database Servers are running a version of AFS older -than version 3.5, during the configuration process a dialog box prompts -you to provide the AFS principal password. -

    -
    Note:If for some reason the AFS principal password is unknown, you can instead -enter the 24-character string of octal digits representing the AFS -principal's key. To obtain the octal key, issue either the -kas examine command or boslistkeys command on an AFS -Database Server machine. Note, the server must be running in -noauth mode in order to display the AFS principal's octal -key. -
    -

    Limitations and Restrictions

    -

    This section briefly describes the known limitations and restrictions -in the AFS Server component of AFS for Windows, version 3.6. -

    AFS bosserver Process Does Not Execute the Notifier Program When a Process Terminates

    -

    The AFS bosserver process does not currently execute the -registered notifier command (if one is specified) when a process under its -control terminates. -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic] [Next Topic] [Index]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns007.htm b/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns007.htm deleted file mode 100755 index 2557a94fa9..0000000000 --- a/src/WINNT/doc/install/Documentation/en_US/html/ReleaseNotes/awrns007.htm +++ /dev/null @@ -1,151 +0,0 @@ - - -Release Notes - - - - - - - - - - - -

    Release Notes

    -

    [Return to Library] [Contents] [Previous Topic] [Bottom of Topic]

    -

    AFS Control Center Release Notes

    -

    Introduction

    -

    This section contains important information about the AFS Control -Center component of AFS for Windows, version 3.6. The AFS -Control Center provides two powerful graphical user interface (GUI) tools to -assist AFS system administrators in AFS cell administration: the AFS -Server Manager and the AFS Account Manager. -

    AFS Control Center Installation Requirements

    -

    Your system must meet the following hardware, software, and -administrative privilege requirements to install the AFS Control Center -component of AFS for Windows. -

    Hardware

    -

    The hardware requirements for installing the AFS Control Center -are: -

    -

    Software

    -

    The software requirements for installing the AFS Control Center -are: -

    -

    Administrative Privilege Requirement

    -

    You must be a member of the local Administrators group on -your Windows system in order to install the AFS Control Center. -

    Product Notes

    -

    This section highlights important general information about the AFS -Control Center component of AFS for Windows, version 3.6. -

    The AFS Control Center Must Be Installed in a Directory Whose Path Contains Only ANSI Characters

    -

    The AFS for Windows software can only be installed in a directory whose -path contains only ANSI characters, for example the default directory -C:\Program Files. -

    Temporary Files

    -

    The AFS Control Center for Windows occasionally creates temporary -files. To control where such files are created, set your environment -variable (TMP or TEMP) to the fully qualified path of the preferred temporary -directory. If you do not specify a temporary directory, then any -temporary files are created in the current working directory of the process -that creates the files. -

    National Language Support for the AFS Control Center

    -

    AFS provides national language support for the AFS Control Center -graphical user interface (GUI) tools and documentation, including support for -bidirectional scripts (Hebrew, Arabic, etc.). The language -strings installed are determined by your machine's system default locale, -as specified in the Control Panel's Regional Settings Properties dialog -box. -
    Note:The system default locale for a machine can be different than the -user locale (specified by a user) on the machine. However, -the language strings installed with AFS for Windows are always determined by -the system default locale. -
    -

    If no language strings exist for the current locale, then English language -strings are installed by default. -

    The kpwvalid Password Strength Checker Is Not Used on Windows Systems

    -

    When an AFS user password is changed from a Windows system, the -kpwvalid program is not used to check the quality of the -new password. (On UNIX systems, if a kpwvalid program exists -in the same directory as the kpasswd program, the -kpwvalid program checks the quality of every new user -password.) -

    Tokens Obtained for Control Center Applications Expire after 25 Hours

    -

    In order to use either the AFS Server Manager or the AFS Account -Manager, users must obtain AFS tokens. The lifetime of tokens obtained -in either application is always 25 hours and 25 minutes, regardless of the -Maximum Ticket Lifetime designated for the user. -

    Server Manager Displays All Server Entries Referenced in the Volume Location Database (VLDB)

    -

    The AFS Server Manager displays a server icon for every server entry in -the Volume Location Database (VLDB). If an AFS server has been -decommissioned, but its VLDB entry has not been removed, then the Server -Manager continues to display an icon for the server. -

    To remove an obsolete AFS File Server entry from the VLDB on a Database -Server running AFS version 3.5 or later, issue the following -command: -

    -

    vos changeaddr <ip_address> -remove
-
    -

    where ip_address is the Internet Protocol (IP) address of the -server machine that has been decommissioned. -

    On AFS Database Servers running a version of AFS older than version -3.5, there is currently no command for removal of obsolete server -entries in the VLDB. However, to prevent the AFS Server Manager from -displaying decommissioned servers, you can modify the Windows NT Registry so -that the AFS Server Manager disregards all machines with IP addresses of a -specified pattern. -

    To prevent the AFS Server Manager from displaying server machines with IP -addresses of a specified pattern, use the following steps to modify the -Windows NT Registry: -

      -

    1. From the Start menu, choose Run. In the Open box, type -regedit, and then choose OK. The Windows NT -Registry Editor opens. -

    2. Right-click the \\HKEY_LOCAL_MACHINE\Software\TransarcCorporation\AFS -Control Center key. From the context menu that opens, choose -New, and then choose DWORD Value. A New Value -entry is added to the key. -

    3. Specify the name of the new value entry by typing -IgnoreBadAddrs as the new value. -

    4. Double-click the new IgnoreBadAddrs entry. The Edit -DWORD Value dialog box opens. -

    5. In the Value data box, specify in hexadecimal notation the IP -address or range of IP addresses to ignore. For example, to instruct -the AFS Server Manager to disregard any machines listed in the VLDB with IP -addresses match the pattern 10.0.0.*, enter -0A0000FF in the Value data box. (The -hexadecimal value FF represents a wildcard.) -

    6. Choose OK to close the Edit DWORD value box and save the new -registry entry. -

    7. Close the Registry Editor. -
    -

    -
    Note:To take advantage of this feature, it is advisable to change the IP addresses -of any decommissioned servers in the VLDB to easily recognizable unused IP -addresses in a specific range, for example -10.0.0.1, -10.0.0.2, -10.0.0.3 etc. Then add the -IgnoreBadAddrs registry entry as described in the previous steps to -instruct the AFS Server Manager to ignore all IP addresses within the -specified range. -
    -

    Limitations and Restrictions

    -

    There are currently no known limitations and restrictions for the AFS -Control Center component of AFS for Windows, version 3.6. -

    [Return to Library] [Contents] [Previous Topic] [Top of Topic]

    - -

    -
    © IBM Corporation 2000. All Rights Reserved -     - - - diff --git a/src/WINNT/doc/install/Documentation/en_US/html/index.htm b/src/WINNT/doc/install/Documentation/en_US/html/index.htm index 63adde69bd..be99f633c6 100755 --- a/src/WINNT/doc/install/Documentation/en_US/html/index.htm +++ b/src/WINNT/doc/install/Documentation/en_US/html/index.htm @@ -204,16 +204,13 @@ style='mso-fareast-font-family:"MS Mincho"'>

    Welcome to the OpenAFS for Windows online documentation set!

    -

    The documentation set includes the OpenAFS for Windows Release Notes and the -IBM AFS for Windows 3.6 product notes and installation and configuration -information for the AFS Server, AFS - Control Center, -AFS Client, and AFS Light products. The OpenAFS for Windows online +

    The documentation set includes the OpenAFS for Windows Release Notes. +The OpenAFS for Windows online documentation set also includes the following administrative documentation: the -IBM AFS Administration Reference and the IBM AFS Administration Guide. +OpenAFS Command Reference and the IBM AFS Administration Guide.

    -

    Although the IBM AFS documentation is out of date, OpenAFS does not have +

    Although the IBM AFS Administration Guide is out of date, OpenAFS does not have revised documentation to replace it at the current time.

    Online Documentation:

    @@ -232,20 +229,6 @@ mso-fareast-font-family:Symbol;mso-bidi-font-family:Symbol'>·         OpenAFS Command Reference

    -

    ·         -IBM AFS for -Windows 3.6 Quick Beginnings

    - -

    ·         -IBM AFS for -Windows 3.6 Release Notes

    -

    - + @@ -269,7 +269,6 @@ - diff --git a/src/WINNT/install/wix/files.wxi b/src/WINNT/install/wix/files.wxi index 9144872ea6..cb36e1f4b8 100644 --- a/src/WINNT/install/wix/files.wxi +++ b/src/WINNT/install/wix/files.wxi @@ -984,7 +984,6 @@ - @@ -993,6 +992,7 @@ + @@ -1034,13 +1034,6 @@ - - - - - - -