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.
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.
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.
This document has the following organization:
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, version 3.6 includes the following components:
The AFS Server runs AFS server processes and includes the AFS Server Configuration Wizard to facilitate setup.
The AFS Control Center includes 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.
The AFS Client provides direct access to the AFS filespace, enabling users to manage files and directories in AFS. The AFS Client includes the AFS Light Gateway.
AFS Light provides access to the AFS filespace via an AFS Light Gateway machine, enabling users to manage files and directories in AFS.
AFS Supplemental Documentation provides additional AFS system administration information and includes the following documents: IBM AFS Administration Guide and IBM AFS Administration Reference.
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. |
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.
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.
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.
Installation of AFS for Windows is complete.
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.
Installing the AFS Client for Windows NT makes the following changes to your system:
The Documentation program entry allows access to the AFS online documentation set that is provided with AFS for Windows.
The Client program subgroup enables users to access the AFS Client property box and the AFS Client Online Help.
Installing AFS Light for Windows 95 and Windows 98 makes the following changes to your system:
The Documentation program entry allows access to the AFS online documentation set that is provided with AFS for Windows.
The Light program subgroup enables users to access the AFS Light property box and the AFS Light Online Help.
Installing the AFS Server for Windows NT makes the following changes to your system:
The Documentation program entry allows access to the AFS online documentation set that is provided with AFS for Windows.
The Server program subgroup enables users to access the AFS Server Quick-Start Wizard.
Installing the AFS Control Center for Windows NT makes the following changes to your system:
The Documentation program entry allows access to the AFS online documentation set that is provided with AFS for Windows.
The Control Center program subgroup enables users to access the Account Manager and the Server Manager.
Installing the AFS Supplemental Documentation makes the following changes to your system:
This section describes the documentation that is provided with AFS for Windows and details the procedures for accessing this documentation.
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.
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.
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.
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.
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. |
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 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.
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.
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.
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.
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. |
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.
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.
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:
The following constraints apply to the form of an internet domain name that can be used as the name of an AFS cell:
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.
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. |
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.
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.
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: | If the Backup Server is configured on any Database Server in the cell, it must be configured on all Database Servers in the cell. |
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.
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.
The root AFS volumes are two volumes that every AFS cell must include in its file system. They are named:
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.
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.
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. |
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. |
To configure the AFS Server into an existing AFS cell:
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.
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.
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. |
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.
The root AFS volumes are two volumes that every AFS cell must include in its file system. They are named:
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. |
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. |
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.)
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. |
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.
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. |
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.
The AFS Control Center is now configured.
This section outlines uninstallation prerequisites, provides instructions for uninstalling AFS for Windows, and lists the changes that the uninstallation process makes to your system.
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.
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:
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.
Uninstalling the AFS Client makes the following changes to your system:
Note: | The directories are not removed if they contain any files other than those installed by the AFS for Windows setup program. |
Uninstalling AFS Light makes the following changes to your system:
Note: | The directories are not removed if they contain any files other than those installed by the AFS for Windows setup program. |
Uninstalling the AFS Server makes the following changes to your system:
Note: | These directories are not removed if they contain any files other than those installed by the AFS for Windows setup program. Also, if you chose to preserve configuration information, some files in the \Program Files\Ibm\Afs\Server directory are not removed. |
Uninstalling the AFS Control Center makes the following changes to your system:
Note: | These directories are not removed if they contain any files other than those installed by the AFS for Windows setup program. |
Uninstalling the AFS supplemental documentation makes the following changes to your system:
Note: | These directories are not removed if they contain any files other than those installed by the AFS for Windows setup program. |