Microsoft KB Archive/91022

= Installing LAN Man 2.1 RPL for OS/2 Clients =

Article ID: 91022

Article Last Modified on 9/30/2003

-

APPLIES TO


 * Microsoft LAN Manager 2.1 Standard Edition

-



This article was previously published under Q91022



SUMMARY
This information supplements Chapter 13 of the &quot;LAN Manager Administrator's Guide,&quot; version 2.1, and the Release Notes for Remoteboot Users (in the README.RPL file on the OS/2 Server disk of the installation set).



Preinstallation Setup Planning

 * 1) Before installing Remote Boot, check the amount of free space on the partition where LAN Manager is installed. The basic installation of RPL for OS/2 clients takes 16 MB, with significant additional space needed for profile information and client data storage. If there isn't enough free space, you can install the RPL files to a different partition, but if you are doing this and using LAN Manager version 2.1, first get new versions of the installation programs from Microsoft. The required update is called csd00.9
 * 2) If the server was configured for LAN Manager 2.0 Remote Boot, the configuration information is preserved in \RPLOLD by LAN Manager 2.1 SETUP.EXE during the upgrade. No special action is required to avoid losing information when installing 2.1 RPL.
 * 3) The RPL server must be running with user security enabled.

Select Remote Boot Protocol Driver

 * 1) If the server ran Remote Boot under LAN Manager 2.0, remove the Remote Boot protocol from the network driver configuration and reboot.
 * 2) Add the Remote Boot driver to the token ring or Ethernet adapter configuration. This adapter must also run the NetBEUI protocol to successfully boot workstations. The base RPL installation (approx. 0.5 MB and 180 files) will be copied to \RPL as part of the procedure for loading the driver from the floppy to the hard disk.

Use RPLSETUP to Install LAN Manager Files
  If you want the RPL installation on another partition, copy the \RPL tree to the desired location and add the line &quot;rpldir = &quot; to the [remoteboot] section of LANMAN.INI file for the server. The original files may be deleted. Throughout this document, paths relative to the specified RPLDIR parameter will be given. For example,      RPLFILES\BINFILES\LANMAN refers to      C:\LANMAN\RPL\RPLFILES\BINFILES\LANMAN on a default installation.  Run RPLSETUP and select installation of files for OS/2 clients. This will install the files to RPLFILES\BINFILES\LANMAN.

Install OS/2 Kernel Files
Copy the two files OS2LDR and OS2KRNL to the BBLOCK\OS2121 or \OS213 directory as appropriate. These files must have the hidden and system attributes removed for the boot to proceed properly.

Install OS/2 Device Drivers and Utilities
  Copy the OS/2 tree from an existing computer's C:\OS2 directory to RPLFILES\BINFILES\OS2121 or \OS213. All the subdirectories should be copied to the server.

There are a number of device drivers in the C:\ directory of the donor OS/2 installation that are needed for OS/2 operation. The exact files vary with the OS/2 version. The list given below applies for the Microsoft OS/2 1.30.1 version shipped with LAN Manager 2.1. The files are copied to the same RPLFILES\BINFILES\OS2121 or \OS213 directory.      *.TSD          Generic disk drivers *.VSD         Vendor enhancement drivers *.BID         Disk controller drivers IOCFGO.SYS IORUN.SYS IOS1Z.SYS BASEDDO.SYS   Keyboard and misc. drivers FLOPPYO?.SYS In general, you should copy to the OS/2 directory on the server every file required by the operating system and located in the root directory (except CONFIG.SYS and STARTUP.CMD). 

Configuring the Service and Creating Profiles

 * 1) Set permissions.

Use RPLINST to create the rplusers and rpladmins groups, set permissions on the installed directories, and modify RPL.MAP and RPLMGR.INI to reflect the operating systems that are present.
 * 1) Create profiles for each hardware configuration.

Using the Remote Boot Manager program (RPLMGR.EXE), create base profiles for each combination of OS/2 version, video type, and network configuration to be supported.
 * 1) Create workstations and assign to profiles.

Create a workstation record for each remote boot client workstation, either by resetting the workstation and allowing it to default boot MS-DOS or by entering the adapter address in the &quot;New Workstation ...&quot; dialog box. Assign the workstation to the correct OS/2 remote boot profile.

The workstation is now configured to boot using the default adapter parameters and system configuration files. If the PROTOCOL.INI file parameters for the workstation need to be modified (for example, to change the interrupt setting), see below.

Maintaining the Service and Modifying the Profiles
Shared and personal profiles

You can configure workstations with either a shared or personal profile. Shared profile clients have read-only access to their configuration files, and all shared profile workstations assigned the same profile share the same copy of the file. This makes for stability and saves disk space. Personal profile clients have read/write access to their configuration files; they start with copies of the shared files but are free to modify them without affecting any other workstation.

Profile-specific information is kept under the RPLFILES\PROFILES\(PROFILE) directory for shared profile clients and RPLFILES\MACHINES\(computer)\(profile)\PRO for personal profile clients, where (profile) and (computer) are replaced with the profile and workstation names.

The binp, binb, and binr directories under rplfiles are shared by all RPL clients, and appear in the client's C:\ directory. The binp, binb, and binr directories under each profile directory are &quot;stubs&quot; and all file access is redirected to the shared bin directories through the FIT file translation mechanism.

Modifying the System Files
<pre class="fixed_text">CONFIG.SYS:  Located in the appropriate profile directory mentioned earlier.

STARTUP.CMD: Located in the appropriate profile directory mentioned earlier.

AUTOEXEC.BAT: Located in the appropriate profile directory mentioned earlier. Executed when the MS-DOS 3.x compatibility box initializes.

LANMAN.INI:  In the &quot;lanman&quot; directory under the appropriate profile directory.

PROTOCOL.INI: For OS/2 RPL clients, there are two PROTOCOL.INI files that may need to be modified. The first is in             RPL\BBLOCK\NETBNETBEUI\(adapter name)\OS2 and is used by              the real mode network drivers that are downloaded in the original boot block. Change the interrupt and I/O address parameters as needed, but do not alter the other parameters in this PROTOCOL.INI file. (This file is             shared by all OS/2 RPL clients that use the same              adapter.) The second PROTOCOL.INI file is used by the usual OS/2 protected mode drivers and is located in the &quot;lanman&quot; directory under the profile directory. This is             the place to make changes to allocate additional NetBIOS sessions and NCBs.

Additional query words: RIPL RPL OS/2 REMOTEBOOT

Keywords: KB91022

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.