home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 36 Tips
/
36-Tips.zip
/
INRDIR.FAX
< prev
next >
Wrap
Text File
|
1994-12-11
|
9KB
|
255 lines
Remote installation via LAN 8/12/94
File:OSINRDIR.fax 4/20/94
TITLE: Remote Install
The following process should not be used as a replacement for
the various REDBOOKS available on Remote Installation. If you
have any further questions that are not covered in the fax please
call 1-800-IBM-7282 to order the appropriate REDBOOK.
Remote Installation and Maintenance GG24-3780-02
Automated Installation for CID Enabled GG24-3783-01
Automated Installation for CID
Enabled Extended Services OS/2 2.X GG24-3781-00
The Installation and Update of Remote OS/2 Systems
Using Netview Distribution Manager. ZZ81-0263-00
DISCLAIMER OF WARRANTIES AND LIABILITY:
---------------------------------------
This sample list is not part of any standard IBM product and is
provided to you solely for the purpose of assisting you in the
development of your application. The list is provided "AS IS",
without warranty of any kind. IBM shall not be liable for any
damages arising out of your use of this list, even if they have
been advised of the possibility of such damages. The following is
provided without guarantees and IBM assumes no liability
or responsibility for the accuracy of this information. IBM
assumes no liabilities arising from the distribution or use
of this information.
Redirected Installation Procedure
The following procedure can be found in the NTS/2 reference,
"Redirected Installation and Configuration Guide", s96f-8848-00.
The procedure below is one of a few ways to setup
a Remote Installation Server. Please note that the procedure below
is not a CID installation, rather a redirected installation of
OS/2. In order to build a Remote Install Server for redirected
installs, the following software is required:
OS/2 2.1 (recommended)
NTS/2 LAPS. LAN Server 3.0
NTS/2 LAPS Utilities. LAN Server 3.0
There are two methods of remote installation described in this
document:
1. Dialog Driven - client drives the installation by answering
the dialog boxes similar to a diskette
driven installation
2. Response File - installation is driven by a response file.
Pg 2
Here is a step by step procedure to build your code server and
client diskettes:
1. Install OS/2 2.1 on your machine
2. Install LAPS on your machine. Please note that LAPS must be
installed on your OS/2 bootable partition.
3. Create the following directory structure (note that any
partition can be used):
d:\cid
d:\server
d:\cid\img
d:\cid\img\srvifs
d:\cid\img\laps
d:\cid\exe
d:\cid\rsp
If you have different versions of OS/2 that you want to
store on your server (e.g. OS/2 2.0 and OS/2 2.1), I suggest
the following structure:
d:\cid\img\os2v20
d:\cid\img\os2v21
d:\cid\exe\os2v20
d:\cid\exe\os2v21
d:\cid\rsp\os2v20
d:\cid\rsp\os2v21
img - disk images
EXE - *.exe's for separate different versions of OS/2.
These files are unpacked from disk_7.
rsp - response files for various client's.
4. Insert the NTS/2 Utilities diskette into drive_a and
type the following command:
xcopy a:\srvifs d:\cid\img\srvifs
5. Insert the NTS/2 LAPS diskette into drive_a and type the
following command:
xcopy a:\*.* /s /h d:\cid\img\laps
6. Insert disk_7 from OS/2 2.1 into drive_a and type the
following command:
Blue colored diskettes: unpack a:\cid c:\cid\exe\os2v21
salmon colored diskettes: UNPACK2 a:\cid c:\cid\exe\os2v21
OS/2 2.0: unpack a:\cid c:\cid\exe\os2v20
Pg 3
This process will unpack four *.exe's shown below. Each *.exe
is specific to the version of OS/2 you are using. This is why
you want to separate each set of modules by version.
Here is a list of the modules that get unpacked:
semaint.exe
seinst.exe
sedisk.exe
seimage.exe
7. We are ready to install the images of OS/2 on your code
server:
For OS/2 2.1:cd\cid\exe\os2v21 seimage /s:a: /t:d:\cid\img\os2v21
For OS/2 2.0:cd\cid\exe\os2v20 seimage /s:a:/t:d:\cid\img\os2v20
8. Now create the SRVIFS configuration file using any editor.
Name the file SERVICE.INI, copy it to the server directory,
place the following statements in this file:
Adapter = 0
MaxClients = 10
MaxFiles = 100
Name = IMGSRV *** Any name can be used ***
GroupName = No
ClientWorkers = 12
Path = d:\
PerClient = No
PermitWrite = No
alias=readonly,single,os2_20,d:\CID\IMG\OS2V20
alias=readonly,single,os2_21,d:\CID\IMG\OS2V21
alias=readonly,single,rsp_inst,c:\os2\install
A description of the parameters above can be found in NTS/2's
"Redirected Installation and Configuration Guide". You need to
look at this manual in order to tune your SRVIFS configuration
file for your environment.
9. copy d:\cid\img\srvifs\xi*.* d:\server
10. copy d:\cid\img\srvifs\service.exe d:\server
11. cd c:\cid\img\srvifs
thinsrv /r:d:\server\service.ini /s:d:\cid\img\srvifs
/t:d:\server /tu:c:
(Note /tu:c: assumes that your bootable partition is
c_drive).
12. We now are going to build your boot diskettes. I am
only going to demo how to build the diskettes for OS/2 2.1,
The same method can be applied for OS/2 2.0, just changing
some of the parameters that may be apparent:
Pg 4
The method described below is a dialog driven method for
remote installation:
a. cd\cid\exe\os2v21
b. sedisk /s:d:\cid\img\os2v21 /t:a:
(This is creating the boot diskettes, e.g. install and
disk_1).
c. cd\cid\img\laps
d. thinlaps c:\cid\img\laps a: IBMTOK.INF
e. cd\cid\img\srvifs
f. thinifs /t:a: /s:c:\cid\img\srvifs /tu:a: /req:*
/d:x: /srv:\\testsrv\os2_21 /w
g: edit the config.sys on disk_1 with this change:
1. replace protshell=sysinst1.exe to
protshell=sysinst2.exe
2. add set sourcepath=x:\ (place it somewhere with the
other set statements).
h. copy d:\cid\img\os2v21\disk_1\sysinst2.exe a:
The method described below is a response file method for
remote installation:
a. cd\cid\exe\os2v21
b. sedisk /s:d:\cid\img\os2v21 /t:a:
(This is creating the boot diskettes, e.g. install and
disk_1).
c. cd\cid\img\laps
d. thinlaps c:\cid\img\laps a: IBMTOK.INF
e. cd\cid\img\srvifs
f. thinifs /t:a: /s:c:\cid\img\srvifs /tu:a: /req:*
/d:x: /srv:\\imgsrv\os2_21 /w
g. thinifs /t:a: /s:c:\cid\img\srvifs /tu:a: /req:*
/d:y: /srv:\\imgsrv\rsp_inst /w
h. edit the config.sys on disk_1 with the this change:
1. replace set os2_shell=cmd.exe to
set os2_shell=y:\rspinst.exe a:\default.rsp
2. add set sourcepath=x:\ (place it somewhere with the
other set statements)
The above statement means that the client is getting
rspinst.exe from the code server. This is defined by the
alias rsp_inst in SERVICE.INI which points to the
\os2\install directory on the code server where
RSPINST.EXE is installed. The y_drive is the redirected
drive letter defined in a srvattach statement in the
config.sys of disk_1. RSPINST.EXE calls default.rsp (which
is the customized response file called default.rsp on
disk_1.
Pg 5
13. OS/2 2.1 creates a sample.rsp in \os2\install. You can modify
this file per client and copy it to disk_1 with the name
default.rsp.
You now have completed the redirected installation process for
both dialog driven and response file methods. Before you
distribute the boot diskettes to your client's, I suggest that
you test each method locally using both methods.
12/31/99