Remote Installation of OS/2 Warp Connect: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 1: Line 1:
{{IBM-Reprint}}
{{IBM-Reprint}}


[[Erik Mintz]]  
''[[Erik Mintz]]''


'''''This Little Solution discusses the remote installation utility included with OS/2 Warp  
''This Little Solution discusses the remote installation utility included with OS/2 Warp Connect. It covers the products included with OS/2 Warp Connect, installation methods, remote installation server setup, the client boot diskettes, and remote client installation.''
Connect. It covers the products included with OS/2 Warp Connect, installation  
methods, remote installation server setup, the client boot diskettes, and remote client  
installation.'''''  


IBM's most recent release of its award-winning 32-bit operating system is OS/2 Warp  
IBM's most recent release of its award-winning 32-bit operating system is OS/2 Warp Connect. Like OS/2 Warp, this package comes in two versions: one without WIN-OS2 support (the red-spine product box) and one with WIN-OS2 support (the blue-spine box).
Connect. Like OS/2 Warp, this package comes in two versions: one without WIN-OS2  
support (the red-spine product box) and one with WIN-OS2 support (the blue-spine box).


OS/2 Warp Connect installs on top of DOS and Windows systems meeting the minimum  
OS/2 Warp Connect installs on top of DOS and Windows systems meeting the minimum requirements (see "Server and Client Requirements" below), as well as on top of OS/2 2.1 or 2.11. If you currently use OS/2 for Windows 2.1, we recommend that you use the OS/2 Warp Connect product with the red spine, which uses your existing DOS and Windows.
requirements (see "Server and Client Requirements" below), as well as on top of OS/2  
2.1 or 2.11. If you currently use OS/2 for Windows 2.1, we recommend that you use the  
OS/2 Warp Connect product with the red spine, which uses your existing DOS and  
Windows.


== Products Included in OS/2 Warp Connect ==
== Products Included in OS/2 Warp Connect ==
Delivered on CD-ROM only, OS/2 Warp Connect includes the following products:
Delivered on CD-ROM only, OS/2 Warp Connect includes the following products:
* Base product:
*Base product:
** OS/2 Warp 3.0 (with WIN-OS2 support)
** OS/2 Warp 3.0 (with WIN-OS2 support)
** IBM Peer for OS/2
** IBM Peer for OS/2
Line 28: Line 19:
** Network SignON Coordinator
** Network SignON Coordinator
** TCP/IP for OS/2 3.0 (including the Internet Access Kit)
** TCP/IP for OS/2 3.0 (including the Internet Access Kit)
* Utilities:
*Utilities:
** AskPSP
** AskPSP
** Diskette images for OS/2 Warp and Networking Products Single-Component           Installations for Connectivity Products
** Diskette images for OS/2 Warp and Networking Products Single-Component Installations for Connectivity Products
** View/print publications
** View/print publications
* BonusPak for OS/2 Warp (on a separate CD-ROM):
* BonusPak for OS/2 Warp (on a separate CD-ROM):
Line 45: Line 36:
   
   
== Two Installation Methods ==
== Two Installation Methods ==
OS/2 Warp Connect includes two installation methods: (1) local, where you install  
OS/2 Warp Connect includes two installation methods: (1) local, where you install directly from the CD-ROM, or (2) remote, where you install across a local area network (LAN) from a workstation set up as a remote installation server.
directly from the CD-ROM, or (2) remote, where you install across a local area network  
(LAN) from a workstation set up as a remote installation server.


== Remote Installation Server ==
== Remote Installation Server ==
One of the best features of OS/2 Warp Connect is its ability to set up a workstation  
One of the best features of OS/2 Warp Connect is its ability to set up a workstation equipped with a CD-ROM as a remote installation server. This remote installation capability allows a client machine to attach across a LAN to an OS/2 Warp Connect server workstation and then install all of the products contained in OS/2 Warp Connect.
equipped with a CD-ROM as a remote installation server. This remote installation  
capability allows a client machine to attach across a LAN to an OS/2 Warp Connect  
server workstation and then install all of the products contained in OS/2 Warp Connect.


=== Server and Client Requirements ===
=== Server and Client Requirements ===
Below are the hardware and software requirements for both the server and client  
Below are the hardware and software requirements for both the server and client machines.
machines.
* Server:
* Server:
** 16 MB of RAM
** 16 MB of RAM
Line 72: Line 57:
   
   
=== Remote Installation Server Setup ===
=== Remote Installation Server Setup ===
Your remote installation server must meet the hardware requirements listed previously  
Your remote installation server must meet the hardware requirements listed previously under "Server and Client Requirements." Its software requirements are OS/2 Warp and native NetBIOS.
under "Server and Client Requirements." Its software requirements are OS/2 Warp and  
native NetBIOS.


Begin the OS/2 Warp Connect installation by booting the installation diskettes provided  
Begin the OS/2 Warp Connect installation by booting the installation diskettes provided with the package. Install only OS/2 Warp, without any networking options (unless required). It does not matter which drive you use to install OS/2 Warp.
with the package. Install only OS/2 Warp, without any networking options (unless  
required). It does not matter which drive you use to install OS/2 Warp.


Once OS/2 Warp is configured, installed, and running on your server, you must install  
Once OS/2 Warp is configured, installed, and running on your server, you must install LAN adapter and protocol support. Multi-Protocol Transport Support (MPTS), included with OS/2 Warp Connect, provides these LAN adapter device drivers and protocols.
LAN adapter and protocol support. Multi-Protocol Transport Support (MPTS), included  
with OS/2 Warp Connect, provides these LAN adapter device drivers and protocols.


To install MPTS, type x:\cid\img\laps\mpts where x: is the drive letter of the  
To install MPTS, type x:\cid\img\laps\mpts where x: is the drive letter of the CD-ROM drive on your remote installation server.
CD-ROM drive on your remote installation server.


Choose the appropriate device driver for your LAN adapter card, and choose the  
Choose the appropriate device driver for your LAN adapter card, and choose the NetBIOS protocol (see Figure 1). When MPTS has been successfully installed and configured, shut down and reboot your machine.
NetBIOS protocol (see Figure 1). When MPTS has been successfully installed and  
[[Image:mintz24.gif|thumb|Figure 1. LAN Adapter and Protocol Support Installation]]
configured, shut down and reboot your machine.
 
[[Image:mintz24.gif]]
 
'''Figure 1. LAN Adapter and Protocol Support Installation'''


''Note:'' If you are installing OS/2 Peer or LAN Requester, remember two things:
''Note:'' If you are installing OS/2 Peer or LAN Requester, remember two things:
# Native NetBIOS is required for remote installations.
# Native NetBIOS is required for remote installations.
# Skip installing MPTS for LAN Adapter and Protocol Support.
# Skip installing MPTS for LAN Adapter and Protocol Support.


== Client Boot Diskettes ==
== Client Boot Diskettes ==
Open the OS/2 System object, then the OS/2 Warp Connect Install/Remove object, then  
Open the OS/2 System object, then the OS/2 Warp Connect Install/Remove object, then the OS/2 Warp Connect Remote Install object (see Figure 2). This last object guides you through building a set of client boot diskettes based on the client workstation's LAN adapter card (see Figures 3 and 4).
the OS/2 Warp Connect Remote Install object (see Figure 2). This last object guides you  
through building a set of client boot diskettes based on the client workstation's LAN  
adapter card (see Figures 3 and 4).


[[Image:mintz25.gif]]
[[Image:mintz25.gif|thumb|Figure 2. OS/2 Warp Connect Remote Install Object]]
 
[[Image:mintz26.gif|thumb|Figure 3. Building Client's Remote Installation Diskettes, Diskette Creation]]
'''Figure 2. OS/2 Warp Connect Remote Install Object'''
[[Image:mintz27.gif|thumb|Figure 4. Building Client's Remote Installation Diskettes, Network Adapter Selection]]
 
[[Image:mintz26.gif]]<br>
 
'''Figure 3. Building Client's Remote Installation Diskettes, Diskette Creation'''
 
[[Image:mintz27.gif]]
 
'''Figure 4. Building Client's Remote Installation Diskettes, Network Adapter Selection'''


== Remote Installation Server Startup ==
== Remote Installation Server Startup ==
After you build your client boot diskettes, you can start your remote installation server  
After you build your client boot diskettes, you can start your remote installation server  
(see Figure 5).
(see Figure 5).
 
[[Image:mintz28.gif|thumb|Figure 5. Remote Installation Server Startup]]
[[Image:mintz28.gif]]
 
===== Figure 5. Remote Installation Server Startup =====


== Client Installation ==
== Client Installation ==
When a client connects to the remote installation server via the LAN installation  
When a client connects to the remote installation server via the LAN installation diskettes, the status bar at the server shows "Installation in progress" (see Figure 6).
diskettes, the status bar at the server shows "Installation in progress" (see Figure 6).
[[Image:mintz29.gif|thumb|Figure 6. Remote Installation Server Status]]
 
[[Image:mintz29.gif]]
 
'''Figure 6. Remote Installation Server Status'''


If the client machine does not have OS/2 Warp already installed, the client's user can  
If the client machine does not have OS/2 Warp already installed, the client's user can choose between the Easy or Advanced installation option. But if OS/2 Warp is already installed and running on the client machine, the installation is flexible enough to give the client's user two other choices: install networking only or reinstall OS/2 Warp with networking.
choose between the Easy or Advanced installation option. But if OS/2 Warp is already  
installed and running on the client machine, the installation is flexible enough to give the  
client's user two other choices: install networking only or reinstall OS/2 Warp with  
networking.


When the client completes the installation, the status bar at the server shows "Installation  
When the client completes the installation, the status bar at the server shows "Installation  

Revision as of 18:14, 22 October 2017

Reprint Courtesy of International Business Machines Corporation, © International Business Machines Corporation

Erik Mintz

This Little Solution discusses the remote installation utility included with OS/2 Warp Connect. It covers the products included with OS/2 Warp Connect, installation methods, remote installation server setup, the client boot diskettes, and remote client installation.

IBM's most recent release of its award-winning 32-bit operating system is OS/2 Warp Connect. Like OS/2 Warp, this package comes in two versions: one without WIN-OS2 support (the red-spine product box) and one with WIN-OS2 support (the blue-spine box).

OS/2 Warp Connect installs on top of DOS and Windows systems meeting the minimum requirements (see "Server and Client Requirements" below), as well as on top of OS/2 2.1 or 2.11. If you currently use OS/2 for Windows 2.1, we recommend that you use the OS/2 Warp Connect product with the red spine, which uses your existing DOS and Windows.

Products Included in OS/2 Warp Connect

Delivered on CD-ROM only, OS/2 Warp Connect includes the following products:

  • Base product:
    • OS/2 Warp 3.0 (with WIN-OS2 support)
    • IBM Peer for OS/2
    • IBM LAN Requester 4.0
    • NetWare Client for OS/2
    • LAN Distance Remote 1.1
    • Network SignON Coordinator
    • TCP/IP for OS/2 3.0 (including the Internet Access Kit)
  • Utilities:
    • AskPSP
    • Diskette images for OS/2 Warp and Networking Products Single-Component Installations for Connectivity Products
    • View/print publications
  • BonusPak for OS/2 Warp (on a separate CD-ROM):
    • Internet Connection
    • CompuServe Information Manager for OS/2
    • HyperACCESS Lite for OS/2
    • Person to Person for OS/2
    • Multimedia Viewer
    • Video IN for OS/2
    • IBM Works
    • FaxWorks for OS/2
    • System Information Tool
  • Lotus Notes Express (on a separate CD-ROM)

Two Installation Methods

OS/2 Warp Connect includes two installation methods: (1) local, where you install directly from the CD-ROM, or (2) remote, where you install across a local area network (LAN) from a workstation set up as a remote installation server.

Remote Installation Server

One of the best features of OS/2 Warp Connect is its ability to set up a workstation equipped with a CD-ROM as a remote installation server. This remote installation capability allows a client machine to attach across a LAN to an OS/2 Warp Connect server workstation and then install all of the products contained in OS/2 Warp Connect.

Server and Client Requirements

Below are the hardware and software requirements for both the server and client machines.

  • Server:
    • 16 MB of RAM
    • OS/2-compatible CD-ROM drive
    • LAN adapter card supported by OS/2 LAN Server
    • OS/2 Warp Version 3 or later
  • Client:
    • Intel 80386SX processor or greater
    • 8 MB to 12 MB of RAM
    • 1.44 MB, 3.5-inch diskette drive configured as drive A:
    • VGA video support
    • IBM-compatible mouse
    • LAN adapter card supported by OS/2 LAN Server

Remote Installation Server Setup

Your remote installation server must meet the hardware requirements listed previously under "Server and Client Requirements." Its software requirements are OS/2 Warp and native NetBIOS.

Begin the OS/2 Warp Connect installation by booting the installation diskettes provided with the package. Install only OS/2 Warp, without any networking options (unless required). It does not matter which drive you use to install OS/2 Warp.

Once OS/2 Warp is configured, installed, and running on your server, you must install LAN adapter and protocol support. Multi-Protocol Transport Support (MPTS), included with OS/2 Warp Connect, provides these LAN adapter device drivers and protocols.

To install MPTS, type x:\cid\img\laps\mpts where x: is the drive letter of the CD-ROM drive on your remote installation server.

Choose the appropriate device driver for your LAN adapter card, and choose the NetBIOS protocol (see Figure 1). When MPTS has been successfully installed and configured, shut down and reboot your machine.

Figure 1. LAN Adapter and Protocol Support Installation

Note: If you are installing OS/2 Peer or LAN Requester, remember two things:

  1. Native NetBIOS is required for remote installations.
  2. Skip installing MPTS for LAN Adapter and Protocol Support.

Client Boot Diskettes

Open the OS/2 System object, then the OS/2 Warp Connect Install/Remove object, then the OS/2 Warp Connect Remote Install object (see Figure 2). This last object guides you through building a set of client boot diskettes based on the client workstation's LAN adapter card (see Figures 3 and 4).

Figure 2. OS/2 Warp Connect Remote Install Object
Figure 3. Building Client's Remote Installation Diskettes, Diskette Creation
Figure 4. Building Client's Remote Installation Diskettes, Network Adapter Selection

Remote Installation Server Startup

After you build your client boot diskettes, you can start your remote installation server (see Figure 5).

Figure 5. Remote Installation Server Startup

Client Installation

When a client connects to the remote installation server via the LAN installation diskettes, the status bar at the server shows "Installation in progress" (see Figure 6).

Figure 6. Remote Installation Server Status

If the client machine does not have OS/2 Warp already installed, the client's user can choose between the Easy or Advanced installation option. But if OS/2 Warp is already installed and running on the client machine, the installation is flexible enough to give the client's user two other choices: install networking only or reinstall OS/2 Warp with networking.

When the client completes the installation, the status bar at the server shows "Installation complete."

References

The following documents were used to create this article:

  • Up and Running, included with OS/2 Warp Connect, page 24
  • User's Guide to OS/2 Warp, included with OS/2 Warp Connect