OSINREDR - REDIRECTED INSTALLATION OF OS/2 2.1 01/22/96 ======================================================================= Redirected Installation of OS/2 2.1 ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION The following steps describe how to build an OS/2 redirected installation server, including Dialog- or Response-file-driven methods of installation. In Dialog-driven installation, the client drives the installation by answering the dialog boxes similar to a diskette-driven installation. In Response-file installation, the installation process is driven by the contents of a Response file. RESOLUTION Note: Make sure you have a backup of any file you intend to change. IBM owns all rights to this document. It may not be used for reprint or publication in any form. This document is "AS IS"; IBM makes no warranties to this document. This article was compiled using ITSC's Redbook, OS/2 V2.0 and V2.1 Remote Installation and Maintenance (GG24-3780-02); NTS/2 Redirected Installation and Configuration Guide (S96F-8488-00); and NTS/2 LAN Adapter and Protocol Support Configuration Guide (S96F-8489-00). The NTS/2 documents are provided with IBM OS/2 LAN Server 3.0 (P/N 96f8400 or 96F8414). Code Server and Client Hardware/Software Requirements ----------------------------------------------------- Server Hardware/Software Requirements ------------------------------------- * 386 or greater * 8 MB RAM (16 MB suggested) * 1.44 MB Drive A * Token-Ring Network * 16/4 Token-Ring Adapter (ISA or Micro Channel) * DASD requirements: 120 MB (recommended) * OS/2 2.1 (recommended) * NTS/2 LAN Adapter and Protocol Support (LAPS) with NTS2FIX (NTS2FIX contains a fix for LAPSCID.DLL and LAPSPM.DLL. You need to obtain NTS2FIX or Service Level wr07020 of LAPS (recommended), which includes NTS2FIX.) * NTS/2 Utilities Diskette Client Hardware/Software Requirements ------------------------------------- * 386 or greater * 6 MB RAM (minimum) * 1.44 MB Drive A * 16/4 Token-Ring Adapter (ISA or Micro Channel) * Minimum OS/2 DASD requirements 1. Create a 60 MB primary partition (drive C) for OS/2 2.1 (recommended) and LAPS, and a 60 MB extended logical partition (drive D) for your code server. 2. Install OS/2 2.1 in your primary partition. 3. Install LAPS in your primary partition. When you set up LAPS, select the 16/4 Token-Ring device drivers and OS/2 NETBIOS. 4. On drive D, create the following directory structure: D:\SERVER D:\CID D:\CID\EXE D:\CID\EXE\OS2V21 D:\CID\IMG D:\CID\IMG\LAPS D:\CID\IMG\OS2V21 D:\CID\IMG\SRVIFS D:\CID\RSP D:\CID\RSO\OS2V21 5. Insert the NTS/2 Utilities Diskette in drive A and type the following, pressing Enter after each: XCOPY A:\SRVIFS D:\CID\IMG\SRVIFS COPY A:\SAMPLE\SERVICE.* D:\SERVER COPY D:\CID\IMG\SRVIFS\XI*.* D:\SERVER COPY D:\CID\IMG\SRVIFS\SERVICE.EXE D:\SERVER 6. Copy the LAPS Disk to your code server; then insert the NTS/2 LAPS Diskette in drive A and type A:\LAPSDISK A: D:\CID\IMG\LAPS and press Enter. 7. Perform the following steps to unpack the files for setting up the code server: a. Insert Diskette 7 in drive A. b. Type the following, pressing Enter after each: UNPACK A:\CID D:\CID\EXE\OS2V21 UNPACK A:\REQUIRED D:\CID\EXE\OS2V21 /N:RSPINST.EXE OS/2 diskettes have labels of different colors. The diskette you need for the next step, depends on the color of your diskette label: * Blue: Diskette 13 * Salmon: Diskette 11 c. Insert the correct diskette in drive A. d. Type the following, pressing Enter after each: UNPACK A:\REQUIRED D:\CID\RSP\OS2V21 /N:SAMPLE.RSP COPY D:\CID\RSP\OS2V21\SAMPLE.RSP D:\CID\RSP\OS2V21\DEFAULT.RSP Note: In a Response file installation, you can customize DEFAULT.RSP and rename it based on a particular "client's" name. 8. To install your OS/2 images on your code server, type the following, pressing Enter after each: CD\CID\EXE\OS2V21 SEIMAGE /S:A: /T:D:\CID\IMG\OS2V21 9. Build your SRVIFS configuration file. The following parameters are described in the NTS/2 Redirected Installation and Configuration Guide, Chapter 6. Refer to this document to customize the SRVIFS configuration file for your environment. Edit D:\SERVER\SERVICE.INI and add the following statements: # SRVIFS Configuration file Adapter = 0 /* Assumes one Token-Ring Adapter in server */ MaxClients = 5 MaxFiles = 102 Name = IMGSRV01 /* Code Server Name */ GroupName = No ClientWorkers = 6 Path = D:\CID PerClient = No PermitWrite = No alias=READONLY,SINGLE,EXE,D:\CID\EXE alias=READONLY,SINGLE,IMG,D:\CID\IMG alias=READONLY,SINGLE,RES,D:\CID\RSP 10. The THINSRV.EXE: * Creates or modifies the STARTUP.CMD with statements necessary to start your code server. * Appends path information in the CONFIG.SYS file. * Adds ISSDEL.EXE to D:\SERVER. IFSDEL.EXE is not needed for redirected installation. a. Type the following, pressing Enter after each: CD\CID\IMG\SRVIFS THINSRV /R:D:\SERVER\SERVICE.INI /S:D:\CID\IMG\SRVIFS /T:D:\SERVER /TU:C: 11. Shut down and then restart the system. You see the following message when the code server is started: IMGSRV01 Server is Active, Version 1.32 Creating LAN Transport Client Boot Diskettes -------------------------------------------- The following steps create Dialog-driven and Response-file driven LAN Transport (LT) client startup diskettes. Dialog-Driven ------------- 1. Type the following , pressing Enter after each: CD\CID\EXE\OS2V21 SEDISK /S:D:\CID\IMG\OS2V21 /T:A: Note: SEDISK prompts you for 2 formatted diskettes; the first is the Installation Diskette, and the second is Diskette 1 of the LT startup diskettes. CD\CID\IMG\LAPS THINLAPS D:\CID\IMG\LAPS A: IBMTOK.NIF Note: If you are using a Token-Ring Bus Master adapter, use IBMTRBM.NIF instead of IBMTOK.NIF. 2. Insert Diskette 1 in drive A. 3. Type the following, pressing Enter after each: CD\CID\IMG\SRVIFS THINIFS /T:A: /S:D:\CID\IMG\SRVIFS /TU:A: /REQ:* /D:X: /SRV:\\IMGSRV01\IMG /W 4. Edit the CONFIG.SYS file on Diskette 1: a. Set OS2_SHELL=X:\OS2V21\DISK_1\SYSINST2.EXE b. Add SET SOURCEPATH=X:\OS2V21 at the end of the CONFIG.SYS file. 5. Save and exit the file; then shut down and restart the system to activate the changes. Response-File Driven -------------------- 1. Type the following , pressing Enter after each: CD\CID\EXE\OS2V21 SEDISK /S:D:\CID\IMG\OS2V21 /T:A: Note: SEDISK prompts you for 2 formatted diskettes; the first is the Installation Diskette, and the second is Diskette 1 of the LT startup diskettes. CD\CID\IMG\LAPS THINLAPS D:\CID\IMG\LAPS A: IBMTOK.NIF Note: If you are using a Token-Ring Bus Master adapter, use IBMTRBM.NIF instead of IBMTOK.NIF. 2. Insert Diskette 1 in drive A. 3. Type the following, pressing Enter after each: CD\CID\IMG\SRVIFS THINIFS /T:A: /S:D:\CID\IMG\SRVIFS /TU:A: /REQ:* /D:X: /SRV:\\IMGSRV01\IMG /W THINIFS /T:A: /S:D:\CID\IMG\SRVIFS /TU:A: /REQ:* /D:Y: /SRV:\\IMGSRV01\EXE /W THINIFS /T:A: /S:D:\CID\IMG\SRVIFS /TU:A: /REQ:* /D:Z: /SRV:\\IMGSRV01\RSP /W 4. Edit the CONFIG.SYS file on Diskette 1: a. Set OS2_SHELL=Y:\OS2V21\RSPINST.EXE Z:\OS2V21\client.RSP (client is the client's name, or use DEFAULT.RSP. b. Add SET SOURCEPATH=X:\OS2V21 at the end of the CONFIG.SYS file. Note: If you use the client's name instead of DEFAULT.RSP, include the following statement: COPY D:\CID\RSP\OS2V21\DEFAULT.RSP D:\CID\RSP\OS2V21\CLIENT'S NAME.RSP 5. Save and exit the file; then shut down and restart the system to activate the changes. ______________________________________________________________________ IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright (c) 1994, 1995 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.