Chapter 5 - Providing Server Support for the Windows 95 Client
Similar to Banyan's DOS and Windows 3.x clients, the Banyan Client for Windows 95 connects to a network server to obtain VINES Files. VINES Files contains client programs that let users access and use network resources, program messages, and help files.
As of Release 7.32(0), Windows 95 clients no longer use the WIN32 Z: drive applications (MUSER, MSERVICE, MLIST, etc.) Instead, the Windows 95 client maps its Z: drive to the DOS directory for the same language location on that server. As a result, Z: drive applications are run from the DOS directory, rather than running them from the WIN32 Z: drive. For example, instead of mapping the Windows 95 Z: drive to WIN32\USA, it is mapped to DOS\USA.
The WIN32 Z: drive applications are not installed when installing the 7.32(0) upgrade to native VINES servers with no pre-existing WIN32 Z: drive locations. WIN32 Z: drive applications are deleted when installing the 7.32(0) upgrade to native VINES servers that have pre-existing WIN32 Z: drive locations. The appropriate Z: drive applications on a StreetTalk for Windows NT server are installed from the Banyan Client Components Suite CD-ROM.
If you require your Windows 95 clients to pick up a particular revision of Z: drive applications (VCOPY, VRENAME) during login, you must install the Windows 95 7.32(0) patch only on servers of the desired revision.
As shown in Figure 5-1, client NEWREV components will be accessed from the WIN32 Z: drive area, while Z: drive applications will be accessed from the DOS directory.
The Banyan Client Components CD-ROM contains more than one language location for the Win32 client files. For each location, the CD-ROM contains the translated files for a specific location that are copied by the installation program to appropriate directories in the new language location. The Win32 client files can be installed on your server either as a new location or as an upgrade to an already existing version of the location.
Note: Do not apply the software across a dial-in line, an HDLC link, or any other type of WAN link. The installation procedure takes a very long time across any of these connections.
Win32 Client Files Installation Overview
To install server support for the Banyan Enterprise Client for Windows 95, perform the following tasks:
1. Install the Win32 client files. You do not have to install the Win32 client files on all of your network servers - only to those servers that you want to provide client files for Banyan Clients for Windows 95. Upon login, the client searches for a Win32 Z drive. If one cannot be found, the client PC will be required to NEWREV to an available Z: drive.
2. Apply the most recent server kernel patch to any 5.50 and earlier servers. Any 5.50 or earlier server that is going to provide file services to a Banyan Client for Windows 95 must be patched with the most recent kernel patch. If 5.50 and earlier servers are not patched, they freeze the client whenever accessed by a Banyan Client for Windows 95. See "Applying the Kernel Patch" later in this section for instructions.
Before you install the Win32 client files, keep the following prerequisites in mind:
|
Access to a workstation with a CD-ROM drive to install the Win 32 client files. |
|
|
You must have administrative privileges to change access rights to the appropriate directories and subdirectories on the server where the client files are copied. |
|
|
You must have appropriate security rights to create additional disk space, if it is determined that sufficient space is not available for the client files. |
|
|
Servers must have approximately 2 MB of free disk space for each location (USA, France, Spain, and so on) that you install. |
|
|
Since the Windows 95 PC maps its Z: drive to the DOS directory for the same language location, DOS must be installed for the intended language. |
|
|
Before patching a server to Release 7.32(0), administrators must preserve any customized .AVD files that exist on WIN32 Z: drives, as well as any other files or applications that have been copied to the Z: drive area. The vconfig.dat file, if it exists, is preserved during the patch installation. |
There are two methods for installing the Win32 client files; use the one that is appropriate for your servers. The two methods are:
|
|
Use Banyan's PATCH program to install the Win32 client files on Native VINES servers. See "Installing the Win32 Z Drive on VINES Servers" below for instructions. |
|
|
Use the VFILES Setup Utility to install the Banyan Win32 client files on StreetTalk for Windows NT servers. See "Installing the Win32 Z Drive on StreetTalk for Windows NT Servers" for instructions. |
Installing the Win32 Z: Drive on VINES Servers
Use the Patch Utility to apply the Banyan Win32 Z: drive patch to your VINES servers. The patch should be applied before you install the client on your workstations. This patch causes services on the server to cycle; therefore, you should patch your servers when they are not in use.
You issue the PATCH command from a Banyan workstation. The Patch Utility allows you to select multiple servers on which to install support for the Banyan Client simultaneously. However, if you are patching multiple servers, the servers acting as your StreetTalk, drive Z, and routing server should be patched last. If the routing server is patched and then becomes unavailable, subsequent patch sessions will fail to identify the routing server and your drive Z server, until the routing server becomes available again.
To Apply the Win32 Z Drive Patch
1. Log in as a user on the AdminList@servername@Servers list, where servername is the name of the server to which you are installing patch.
2. Open a DOS session, and make the directory containing the language-specific version of the patch files your active directory.
For example:
- If the files are located on Banyan Client Components CD-ROM, insert the CD into the CD-ROM drive on the workstation and enter:
D:
CD \win95\<location>\patch<location> is the language-specific location (USA, France, Germany, and so on) you want to install.
- If you have copied the files to your local disk, enter:
cd C:\<location>\patch
<location> is the language-specific location (USA, France, Germany, and so on) you want to install.
3. Enter the PATCH command. If you are patching only one server, you can specify the server name:
Z:\PATCH
or
Z:\PATCH servername
The Patch Utility menu appears.
4. Choose Install Patches.
The Select Patch Names screen appears and displays the names of the patches on the patch diskette. In this case, only one name will appear as follows:
Win95 Z: drive Patch with Client Software
The name is already highlighted.
5. Press ENTER.
An asterisk appears beside the selected name, and the patch range information is displayed at the bottom of the screen.
6. Press F10. If you specified the server name at step 3, proceed directly to step 8. Otherwise, the Available Servers screen appears.
The Available Servers screen displays information specific to each selected server, including its patch range. If the patch range for the selected server is out of bounds for the range specified for this release, you cannot apply this release on that server.
7. Use the arrow keys to move to the servers on which you are installing this release. To select a server, press ENTER. You can select more than one server.
To select a server, press ENTER. Pressing ENTER a second time, deselects the server.
When you select a server, a line on the Available Server screen displays information about that server. The following character codes may appear:
$ -- Indicates that you selected the server
Z -- Indicates that the server provides your Z drive
R -- Indicates that the server is your routing server
AT, MC, or SMP -- Indicate the server platform8. After you finish selecting the servers to patch, press F10. The Display Install Time screen appears. This screen contains the following information:
- The name of each server being patched.
- The time that the patch is scheduled to run. By default all servers are scheduled to be patched ASAP.
9. Do one of the following:
- To schedule each server to be patched at a specific time, continue with step 10.
- To apply the patches as soon as possible to all servers, press F10. Skip to step 17.
10. Use the arrow keys to select a server. You change the schedule individually for each server.
11. Press F4 to specify a time to apply the patch. You are prompted to enter a time to apply the patch. Continue with step 12.
12. Enter the time when you want to patch the selected server.
Enter the new time in HH:MM format. For example, enter 16:00 to apply the patch at 4:00 p.m. If you make an error when entering the time, use the BACKSPACE key to delete what you have entered.
To apply the patch at a later time, take into account the length of time required to copy the patch files to the server, especially if you are applying a large patch to several servers. The Patch Utility needs several minutes to copy the patch source files to the server. The actual time depends on the size of the patch, the number of servers being patched, and whether the files are being copied from diskettes or a fixed disk.
Set the time far enough ahead to avoid conflict between the copy operations and applying the patch. If you set a time and the patch files are not yet copied to the server when that time arrives, the patch is applied as soon as possible after the files are copied.
For example, if you schedule the patch to be applied in 15 minutes, but it takes 20 minutes to copy one patch to one server, the installation takes place as soon as possible after all files have been copied to the server.
Caution: Avoid scheduling a patch so that it executes when the mail janitor runs or STDA is rebuilding.
13. The Display Install Time screen appears again. The time that you specified for each server appears beside the name of the server. The patch application will begin at the time shown.
14. Repeat steps 10 through 13 for each server that you want to schedule. Servers for which you do not specify a time are patched as soon as the patches are copied to the server.
15. After you have finished scheduling the patch session for each server press F10. A message appears, reminding you that the servers being patched will reboot after the patch has been applied.
16. Press F10 to continue.
17. The Patch Utility begins copying files from the server. It informs you of the total number of files being copied and incrementally displays the file numbers being copied.
For example:
Copying 19 files to server Admin1
Copying file #18After all files have been copied, the following message appears:
All files were copied successfully to server.
18. Press ESC. The Patch Utility main menu appears.
19. Press ESC to exit to a DOS prompt. The servers you selected in step 7 are patched in the order in which you selected them.
The patch is applied to the selected servers at the time you specified at the Current Time screen. After the patch is applied, the server reboots automatically.
When all services are running on the server, verify that the patch was properly applied. Refer to "Verifying That You Applied the Patch Successfully," which follows.
Verifying that the Patch Applied Successfully
To verify that the patch was applied to the servers selected, do one of the following:
|
|
From the Patch Menu, choose Display Patch
History for the servers where you applied patch components. Win95 Z: drive for Patch and Client Software |
|
|
Examine the PATCHLG file. By default, this file is created in the root directory of your workstation's drive C. For each patch that was successfully copied to the server, the log provides the name of the patch and server. |
|
|
Run SHOWREVS <servername>. If the server is running the Windows 95 Client software, SHOWREVS should show the updated revision information for the server's WIN32 location. |
Installing the Win32 Z Drive on StreetTalk for Windows NT Servers
Prerequisites
You must install the language specific DOS Z: drive files prior to installing the corresponding Win32 Z: Drive files. For example to install CLIUSA.EXE, you must have installed the DOS/USA VINESFiles from the Client Component CD using the setup program on your StreetTalk for Windows NT Server installation media.
To Upgrade Existing Win32 Z: Drive Files
1. Use StreetTalk Explorer to shut down VINESFiles@<servername>@servers by double-clicking VINESFiles and then clicking Stop.
2. Using NT File Manager or NT Explorer, go to the appropriate language directory and delete PCINIT and all directories beneath it.
3. Copy the downloaded CLIxxx.EXE file to the appropriate language directory.
4. Run the CLIxxx.EXE using the "-d" switch to maintain directory structure.
5. Use StreetTalk Explorer to restart VINESFiles@<servername>@servers.
To Install Win32 Z: Drive Files on a New Server
1. If your StreetTalk for Windows NT server does not have a previous version of the WIN32 Z: drive files, go to C:\Program Files\Banyan\Vfiles and create a \win32 directory. Then create the appropriate language directory within the \win32 directory.
For example, from a from DOS session:
md Program Files\Banyan\VFiles\win32
md Program Files\Banyan\VFiles\win32\usa2. Copy the downloaded CLIxxx.EXE file to the appropriate language directory.
3. Run the CLIxxx.EXE using the "-d" switch to maintain directory structure.
4. Use StreetTalk Explorer to restart VINESFiles@<servername>@servers.
Note: If you have installed new Win32 Z drive files over existing Win32 Z drive files, you may need to reset your VCONFIG.DAT. See "Resetting VCONFIG.DAT" below for instructions.
If you install new Win32 Z drive files over existing Win32 Z drive files, it resets VCONFIG.DAT to the default "None" from whatever it was set to. Use any ASCII text editor to change VCONFIG.DAT back to its previous setting, if any.
Note: When logging in, if a Banyan Client for Windows 95 is unable to find a server with a matching VCONFIG.DAT file, the client will automatically invoke NewRev.
You must apply the most recent server kernel patch to any 5.50 and earlier servers that will provide file services for Banyan Windows 95 Clients. If you do not, anytime you use the Network Neighborhood to enumerate files on a 5.50 or earlier server, the server will trap.
You can download kernel patches from www.banyan.com, BOA, or banyan's ftp site (ftp.banyan.com).
1. Log in as a user on the AdminList@servername@Servers list, where servername is the name of the server to which you are installing patch.
2. Make the directory containing the patch files your active directory.
For example, if you have copied the files to your local disk, enter:
cd C:\patch
3. Enter the PATCH command. If you are patching only one server, you can specify the server name:
PATCH
or
PATCH servername
The Patch Utility menu appears.
4. Select Install Patches.
The Select Patch Names screen appears and displays the names of the patches in the patch directory.
5. Press ENTER.
An asterisk appears beside the selected name, and the patch range information is displayed at the bottom of the screen.
6. Press F10. If you specified the server name at step 3, proceed directly to step 8. Otherwise, the Available Servers screen appears.
The Available Servers screen displays information specific to each selected server, including its patch range. If the patch range for the selected server is out of bounds for the range specified for this release, you cannot apply this release on that server.
7. Use the arrow keys to move to the servers on which you are installing this release. To select a server, press ENTER. You can select more than one server.
To select a server, press ENTER. Pressing ENTER a second time deselects the server.
When you select a server, a line on the Available Server screen displays information about that server. The following character codes may appear:
$ -- Indicates that you selected the server
Z -- Indicates that the server provides your Z drive
R -- Indicates that the server is your routing server
AT, MC, or SMP -- Indicate the server platformThe number that appears beside the server name indicates its position on the server list.
8. After you finish selecting the servers to patch, press F10. The Display Install Time screen appears. This screen contains the following information:
- The name of each server being patched.
- The time that the patch is scheduled to run. By default all servers are scheduled to be patched ASAP.
9. Do one of the following:
- To schedule each server to be patched at a specific time, continue with step 10.
- To apply the patches as soon as possible to all servers, press F10. Skip to step 17.
10. Use the arrow keys to select a server. You change the schedule individually for each server.
11. Press F4 to specify a time to apply the patch. You are prompted to enter a time to apply the patch. Continue with step 12.
12. Enter the time when you want to patch the selected server.
Enter the new time in HH:MM format. For example, enter 16:00 to apply the patch at 4:00 p.m. If you make an error when entering the time, use the BACKSPACE key to delete what you have entered.
To apply the patch at a later time, take into account the length of time required to copy the patch files to the server, especially if you are applying a large patch to several servers. The Patch Utility needs several minutes to copy the patch source files to the server. The actual time depends on the size of the patch, the number of servers being patched, and whether the files are being copied from diskettes or a fixed disk.
Set the time far enough ahead to avoid conflict between the copy operations and applying the patch. If you set a time and the patch files are not yet copied to the server when that time arrives, the patch is applied as soon as possible after the files are copied.
For example, if you schedule the patch to be applied in 15 minutes, but it takes 20 minutes to copy one patch to one server, the installation takes place as soon as possible after all files have been copied to the server.
Caution: Avoid scheduling a patch so that it executes when the mail janitor runs or STDA is rebuilding.
13. The Display Install Time screen appears again. The time that you specified for each server appears beside the name of the server. The patch application will begin at the time shown.
14. Repeat steps 10 through 13 for each server. Servers for which you do not specify a time are patched as soon as the patches are copied to the server.
15. After you have finished scheduling the patch session for each server press F10. A message appears, reminding you that the servers being patched will reboot after the patch has been applied.
16. Press F10 to continue.
17. The Patch Utility begins copying files from the server. It informs you of the total number of files being copied and incrementally displays the file numbers being copied.
For example:
Copying 19 files to server Admin1
Copying file #18After all files have been copied, the following message appears:
All files were copied successfully to server.
18. Press ESC. The Patch Utility main menu appears.
19. Press ESC to exit to a DOS prompt. The servers you selected in step 7 are patched in the order in which you selected them.
The patch is applied to the selected servers at the time you specified at the Current Time screen. After the patch is applied, the server reboots automatically.
