WiseManager Documentation

From OS2World.Com Wiki
Jump to navigation Jump to search

By Serenity Systems International

Planning

The Serenity System Managed Client package consists of three basic software components: WiseManager, WiseServer and WiseClient. A key feature of the Managed Client environment as implemented by WiseManager is the fact that this application executes from the system administrator's workstation, which can be any workstation on the network, including a remote workstation using a dial up connection. This means that WiseManager can even be implemented and executed from the same system being used as the server. The WiseServer application resides and executes on the server. The WiseClient application resides and executes on each of the remote boot clients.

Software

Server Prerequisites

The server must be running either the Warp Server Entry, Warp Server Advanced, Warp Server SMP, or the newly released OS/2 Warp Server for e-business (a.k.a Aurora) with "Remote IPL", "File and Print Service", and "TCP/IP" installed. A fresh installation with NO fixpaks applied is highly recommended.

Limitations of Remote Boot Clients

WiseManager supports OS/2 Warp 4 as a remote boot client. Users should be aware that it is not possible to invoke Netbios/Netbeui peer resource sharing from a remote boot client. For example, a printer attached to a remote boot client cannot be shared as a peer resource. Sharing a printer is accomplished by attaching the printer to a server, a non-remote boot Warp 4 client, or using a printer which has a built in adaptor to make it a network resource. However, printers CAN be accessed and shared through TCP/IP printing.

The fact that a client has or does not have local drives is not the issue. A remote boot client does not have to be diskless. Once the machine is booted from the network, the local hard drives can be used in exactly the same way as a non-remote boot Warp 4 client system. However, even then, if the client is utilizing local drives, the restriction regarding peer resource sharing remains in effect. Peer resource sharing is not available.

Hardware

Server=

System

Any system capable of running Warp Server should be acceptable for the evaluationprograms which limits the number of clients to five Managed Clients. However larger installations should utilize an SMP version of Warp Server, either Warp Server Advanced SMP, or Warp Server for e-business with the extra SMP option.

Processor

Pentium class processor(s) or equivalent. Because all of the client stations perform their own processing, they create little additional demand on the server processor.

Memory

Sufficient memory should be available to achieve a cache hit ratio of more than 95%. 64M is acceptable for small installations (a few client stations). 128M should be considered the minimum for medium size installations (10 to 30 client stations), and 256M (or more) is recommended for larger installations (more than 30 client stations per boot server).

Hard Disk

For small installations, the minimum requirement is a large capacity IDE drive with at least a RAID 1 hardware mirroring controller. For larger installations, fast ultrawide-SCSI drives with hardware RAID support is highly recommended.

Network Interface Card (NIC)

A bus-mastering NIC is recommended. Users can also use multiple NICs to benefit from Warp Server's automatic load balancing capability.

Client

System

Generally, systems capable of running Warp 4 will provide acceptable performance. The IBM Network Station 2800, or other NLX form factor small foot-print PCs are highly recommended.

Processor

Pentium class processor or equivalent.

Memory

Same requirement as Warp 4.

Video

For best results, use video cards that are supported by the IBM GenGradd or Scitech display doctor drivers see http://service.boulder.ibm.com/os2ddpak/html/gradd/ and http://www.scitech.com). =====Hard Disk The use of a local hard disk for client systems is discouraged. This is an issue of design and implementation. Diskless clients provide more benefits from a standpoint of reliability, manageability, and problem resolution. However, some users may opt to utilize a small local harddrive to host the machine's swapper file. This will help reduce network bandwidth demand by the client system. For small installations, the benefit provided by use of local hard drives is negligible and use of local drives should be avoided.

Network Interface Card (NIC)
               The Managed Client environment is specialized and while many NICs support this environment, it is not always an easy task to determine which NICs fall into this category. Even different model NICs from the same manufacturer have provided mixed results. It is recommended that NICs tested and supported by Serenity Systems be utilized.

Network=

A 16 MB/s token ring or 100BaseT ethernet network is highly recommended. A 10BaseT nework will work fine for small installations.

Server Network Resource Requirements

IBMLAN.INI
               [server] section
NUMREQBUF

This is the number of request buffers. Four (4) should be defined for each requester.

Maximum value is 408.

MAXOPENS

Number of files, pipes, and devices which can be open simultaneously on the server. This value is ignored by the server under the HPFS386 file system.

Maximum value is 8000.

MAXSESSOPENS

Number of files, pipes, and devices simultaneously open for a requester. This value is ignored by the server under the HPFS386 file system.

Maximum value is 8000.

[remoteboot] section

MAXTHREADS

Number of threads that the Remote IPL service starts in order to perform asynchronous reading of the configuration files.

Maximum value = MAXTHREADS in the server's config.sys.

This value should be no greater than 6.

Increasing this parameter can decrease performance in larger installations.

PROTOCOL.INI
[protocol] section
NCBS

Should be set to 4 x n where n is the number of remote boot clients supported by this server.

SESSIONS

Total number of DOS and OS/2 remote boot clients supported by this server.

Installation

Install Warp Server

It is highly recommended that a fresh install be used with WiseManager. However, if you must use an existing system, please backup your system. The WiseManager installation process will cause changes to be made to the system in such a way that THERE WILL BE NO WAY TO RETURN THE SERVER TO THE STATE IT WAS IN BEFORE THE INSTALLATION BEGAN. The only way to restore the system will be from a backup!

Disk Partitions

The following represent a typical and recommended disk partitioning pattern. Your actual needs may be different.

Install the basic components of OS/2, MPTS, File & Print Service, Spooler Queues, and TCP/IP in the System Partition. Depending on the video driver needed for the server, you might need to include DOS. Installation of WinOS2 on the server is not recommended. The remote boot client stations WILL be able to run WinOS2.

Drive Letter Type Minimum Size (MB) Format Comment
C: Primary 30 HPFS Maintainance (BootOS2 - at the present, BootOS2 does not work with Warp Server for e.business. Recently, fixes which may allow bootos2 to work with Warp Server for e.business so this condition should be corrected in coming releases of WiseManager.)
D: Logical 512 HPFS System partition
E: Logical 1,024 HPFS/JFS For the IBMLAN\RPL and IBMLAN\RPLUSER directory
F: Logical large HPFS/JFS For WiseManager and ALL remote boot client work areas
G: Logical <100 HPFS Garbage dump
H: Logical (2nd drive) large (100 per client) HPFS Swap area for server and remote boot clients

File and Print Services

When you install the network portion of Warp Server, be sure to check the "More..." button to the right of the "File and Print Sharing Services" and check "Remote Boot Service for OS/2 Workstations (Remote IPL)" and "Remote Boot Service for DOS Workstations (Remote IPL)" (optional). Click "Okay" and then "Next". You should see the following screens:

MPTS

An evaluator offered this comment, which is being evaluated: I found this bit of the install a bit "shakey" under Warp Server for e.business. After GETRPL is executed and I reboot, I have to go back into install (icon on desktop) and perform page 3 - First apply FP9 (don't re--boot), then go into install again and click "I did it". I think some people could miss this step.

After following the prompts of this stage, a message is displayed which says the server is not started when, in fact, it is. There's a message in the VX-Rexx console to ignore this, so I guess it's OK, but someone could easily click the "try to start server" button. Now this is finished, the install program requests you select the re-boot option - unfortunately it doesn't do anything and a manual shutdown and re-boot is needed.

A "cold" boot (power off/on) is probably best at this point in my opinion. The installation program adds a NET Start RIPL line to the STARTUP.CMD file, unfortunately (as in my case) if you already use Remoteboot (OS/2 DOS or WSOD), this causes an error as the server is already started when the server starts.

Perhaps the install program could be changed to look at IBMLAN.INI to see if REMOTEBOOT is listed as a required service and only if not there, either add it into the IBMLAN.INI file or add the NET START RIPL (or REMOTEBOOT) command to the STARTUP.CMD file ??

Tip: Experience has shown that the netwok installation portion of Warp Server to be problematic - often causing traps during MPTS install. The base OS installation has improved to the point where problems are few and far in-between. Therefore, it is recommended to perform the installation in two phases: First, with the base OS and NO NETWOK - uncheck all of the options from the network installation screen (including TCP/IP) with the exception of MPTS. Then, specify that there is NO network adapter in the system. The installation will proceed to install a NULL network driver in the system. Once you're done with the base OS installation, you can go back and do a selective install for networking.

Install WiseManager

When you have finished with the basic Warp Server install, you are ready to install WiseManager. If you are installing or re-installing WiseManager on an existing system, be sure to stop all other on-going tasks which need the server. The WiseManager installation program may automatically reboot the server at various stages of the installation process without giving any prior warning message.

Place the WiseManager CD into your CD-ROM and from an OS/2 command line, issue the command:

 x:\install.exe   (for Warp Server

or

 x:\install.exe AURORA  (For Warp Server for e-business)

where x is the drive letter of your CD-ROM

You will see one of the two following screens (if the "I did that" button is grayed out, stop the installation program and double click the "WiseServer Installer" program icon on your desktop to restart the installation program):

Warp Server for e-Business (AURORA)

File:WiseInst005.jpg Warp Server

The first time you invoke the WiseManager installation program, you will be prompted for the various locations in use. Generally, the default values will work fine. However, in the example above, you will need to change the location of the WiseManager directory (TVoice) to a different drive. The default setting points to the same drive as IBMLAN\RPLUSER. You can always invoke the "Drive Letters" option under the "Configuration" dropdown menu in the install program to change drive letters. From this point and on, simple follow the on-screen instruction to finish the installation.

This cannot be emphasized strongly enough. It is important to follow the instructions EXACTLY as stated and in the SPECIFIED SEQUENCE provided. At any time during the installation process, if you are not sure about a certain step, or if you have a question, STOP! If you skip one of the steps, it is very likely that you will have to do a complete Warp Server reinstall before you can use WiseManager. --- Tip: Make sure that the TCP/IP services DDNS, DHCP, and BINL are NOT running during WiseManager installation. At a certain point during the installation, you will see a dialog box warning you about this. When you see that message, bring up the window list to determine if these tasks are running. If so, while you are in the window list, close the tasks DDNSAPS.CMD, DBCPSCPS.CMD, and BINLSCPS.CMD.

In addition, if you're doing a re-installation, it's important that the RIPL service and WiseServer service NOT be running. The RIPL service can be stopped by issuing the command NET STOP RIPL from an OS/2 command line. The WiseServer service can only be stopped by executing the "Stop WiseServer" function inside the WiseServer application folder.

Finally, it has also been reported that GETRPL, RIPLINST, and XCOPY may have problems with some brands of CD-ROM drives. If you get any error messages from GETRPL, RIPLINST, XCOPY, or if the CD-ROM seems to take a long time before recognizing the WiseManager installation CD, do not skip past them. STOP. This task may have to be completed using a different CD-ROM drive. ---

An evaluator offered this comment, which is being evaluated: I found this bit of the install a bit "shakey" under Warp Server for e.business. After GETRPL is executed and I reboot, I have to go back into install (icon on desktop) and perform page 3 - First apply FP9 (don't re--boot), then go into install again and click "I did it". I think some people could miss this step.

After following the prompts of this stage, a message is displayed which says the server is not started when, in fact, it is. There's a message in the VX-Rexx console to ignore this, so I guess it's OK, but someone could easily click the "try to start server" button. Now this is finished, the install program requests you select the re-boot option - unfortunately it doesn't do anything and a manual shutdown and re-boot is needed.

A "cold" boot (power off/on) is probably best at this point in my opinion. The installation program adds a NET Start RIPL line to the STARTUP.CMD file, unfortunately (as in my case) if you already use Remoteboot (OS/2 DOS or WSOD), this causes an error as the server is already started when the server starts.

Perhaps the install program could be changed to look at IBMLAN.INI to see if REMOTEBOOT is listed as a required service and only if not there, either add it into the IBMLAN.INI file or add the NET START RIPL (or REMOTEBOOT) command to the STARTUP.CMD file ??

After you have performed all of the steps, reboot the server before using any of WiseManager's services.


Configuration

WiseManager Configuration

The first time you boot up the server after the WiseManager installation process, you should see the WiseServer icon on the lower left section the server's screen. If you have selected the Server and RIPL Services Auto-start options, those services will have been started. Underneath the WiseServer icon, you should see the name of your domain and the name of the RIPL server. If you don't see these things, and/or you see "RIPL Not Started" under the icon, something is wrong with the RIPL setup.

You should also have a folder on your desktop for WiseServer. Double click on that folder and you should see the following:

  • Double click on "WiseManager" to start the WiseManager program - a button with your domain name should be visible.
  • Click on your domain and you will be prompted for a logon userid and password. If the logon is successful, you will see a screen with the RIPL servers.
  • Clicking the server button will bring you to the work group screen, which has two groups: Main and Template.
  • Click on the Template group. The specific content of the next screen will depend on the NIC templates supplied. In our example, we'll use the Kingston KNE30 PCI 10BaseT network card at the client side. If the message "Workgroup TEMPLATES does not exist" appears, press the create button to create it. NOTE: If you are using a different card make sure you use the correct template. If you have the Kingston V4 card for instance, select the Kin_etherx_PCI template. If your card is not listed but is supported under OS/2 Ripl install it (see IBM Warp Server Documentation) and create a template for it, by right klicking anywhere in the Templates window and select "add new user".
  • Click the "KNE30RX PCI (pending)" button to bring up the "build" screen for a machine with the name of KNE30RXPCI.

File:Wiseconfig006.jpg

Parameters for Remote Boot Client

User Identifier by which this client is known to WiseManager. Must be unique within each work group. Can be the same as Machine ID below. Note that this name has nothing to do with any LOGON user id.
Machine ID Machine ID as known to Warp Server. Must be unique per domain.
Phone Extension Reserved for future use.
NIC Address 12 digit hex address for the client station's NIC. See notation below.
Adapter identifier Coded NIC identifier as defined in \IBMLAN\RPL\RPL.MAP.
Adapter description NIC description as defined in \IBMLAN\RPL\RPL.MAP. Read only field.
Bus type ISA or MicroChannel. (Default to ISA - which means Non-MicroChannel)
Display type Do not change here - you will be able to select display types later.
Keyboard type Keyboard type. (Default to Regular).
Swapper location Client swapper location: Server or Local. (Default to Server).
Boot drive letter Client boot drive letter. (Default to Z:)
System drive letter Reserved for future use.

NIC Address

NIC address is a unique burned-in 12 digit hex number identifying the primary network adapter in the client workstation. If you are building a client from the server side, you will need to know exactly what this address is. You can get this information by activating the RIPL function of the client workstation NIC and noting the value when the machine is powered on. Some NICs require a plug-in "boot prom" which needs to be activated while others have this function built in. Some machines may require a change in the BIOS settings in order to recognize this function. Others may need to run a DOS set up program.

Automatic Detection of NIC Address

An important feature of WiseManager is the ability to set up the system so the client systems will report the NIC address automatically to the server when the machine is powered on. This means that users don't have to build client machines from the manager's station or even track of the NIC addresses. This feature makes it much easier to set up networks.

Unfortunately, there is no definitive method available to associate a certain NIC address with a particular manufacturer and model number. So, it is not possible to know with certainty which device driver to load based solely on a given NIC address. In a group of similar network cards, you may only have ONE of them reporting the NIC address to the server at any given time. To utilize this "Self-definition" function, you must follow the instructions outlined below.

Wildcard Character Usage in NIC Address

Let's assume you have a number of new computers and they all have Kingston KNE30 PCI NICs. From what we know today, Kingston KNE30 PCI NICs use addresses that begin with 00C0F0. From the server side, in the template group for Kingston KNE30 PCI, specify a NIC address of 00C0F0?????? and click "Execute".

Building Remote Boot Client Machine

Depending of the system you have for the server, it takes approximately 30 seconds to "build" a remote boot client machine. If the build is successful, you should see the screen to the right. After that, you will see the Management Console for the template machine you just built (see the screen below). For now, just close the console.

Client Machine Power On

If the BOOT PROM is working, you should see some on-screen display indicating that it's searching for the server. The exact format of the indicator is NIC dependent. If you are offered a list of RIPL choices, select boot from network, and Non-Netware RIPL.

On most NICs, if it found the server with a matching NIC address or NIC address pattern, it will indicate a "FFC" count followed by a DOS section and then an OS/2 boot that is identical to what you would have see from a normal OS/2 Warp 4 boot.

If the boot is successful, you will see the screen below:

NOTE: This screen shot will be revised so Application Group shows Basic, not General, and the second button will be Create not Execute.

For a quick check, just fill in a "User" name and hit enter. The "User" name is NOT a logon user name but a name given to the remote boot client station, as it will be known to WiseManager. This name CAN be the same as the "Machine ID" which is a name given to the station as it will be known to Warp Server. The "User" name must be unique within a work-group. The "Machine ID", likewise, must be unique per domain. By default, "Machine ID" is set to "M" followed by the "User" name you enter and end with the last 4 digits of the station's NIC address.

Notice that the NIC address has been reported automatically to the server. It is VERY IMPORTANT that you don't shut off the machine at this point. If you do, you will have to do some manual cleanup of the \IBMLAN\RPL\RPL.MAP at the server.

For now, ignore all other fields and simply click "Create". After the machine has been "built" for you, the machine will reboot automatically. If everything works properly, you would have "built" a fully functional Warp 4 machine. There are several error messages displayed during the workstations boot, some of these are related to no DOS support being installed by default some are network related (such as IFNDIS) don't worry about these for the time being.

Destroy Template Machine

When you have finished building all of your machines, be sure to destroy the template machine from that machine's management console by invoking the "Destroy" function under the "Utility" system menu item. When you do this, the template machine no longer "exists" and the Automatic Detection of NIC Address function as described above for that NIC will be turned off and will not cause any "false boots".

Wildcard Character Usage For Mixtures Of NICs

For reasons already explained, if you have a mixture of NICs and you wish to use the Auto-configuration feature of WiseManager, you must take steps to ensure that WiseManager loads the proper network driver for each card. For instance, both the Kingston KNE40 and KNE30 use NIC addresses that begin with 00C0F0 but require different drivers. Therefore, if you activated the KNE30 template machine and power on a machine with the KNE40 NIC, it will be unable to boot - because it would attempted to boot with the KNE30 network driver!

Once the machines are built, there is no problem using mixtures of NICs.

Wildcard Character Usage For Certain IBM NICs

Certain NICs, including IBM NICs, present a different challenge: they don't seem to have a consistent NIC address pattern. Unlike the Kingston cards whose NIC address always begin with 00C0F0, the IBM Etherjet NIC seems to come with various starting NIC address patterns. You will have to either create multiple template machines for these cards, or make other adjustments as your installation progresses.

WiseClient Configuration

After you had built a client machine, everything about that machine can be managed from WiseManager. Using the previous example, if you click on the Main work-group you would have seen a button registered for the machine you just built. Note: The first time you do this you may get a message "error group does not exist" if so, press the create button. If, however, you had that window open while the machine is being built, you will need to right click anywhere on that screen and select "Refresh". The management console for that machine will appear. See Managing A Remote Boot Client for a full discussion on how to manage a remote boot client.

Quick Start

A newly installed machine is usually set to VGA and one of the first things users or support people do is reset the configuration to SVGA. This is a process well known to both users and support people, so let's take a look at how WiseManager can improve this process. And by doing that, provide you with a clear example at how effective WiseManager can be at supporting the operational nature of the network, including supporting users.

For this example, we will assume that the IBM GenGradd driver supports the video card on the client system. The WiseManager user goes to the the Application Launching window, to the left of the Management Console. Expanding the "Hardware" tree, the user will see "IBMGenGradd". Note: IBMGenGradd may not appear under the hardware tree for some users. They may see SDDOS2. If so, these users may install the SDD drivers (if the video in the client is supported by SDD). To make this change on the workstation, the WiseManager user executes a simple drag and drop of this item on the Management Console, anywhere within that window on the right. After a few seconds, you will see the client machine goes into an auto-reboot and you can check that the machine is indeed working in SVGA mode after that.

This example illustrates two important features of WiseManager. First, this illustrates the power which can be implemented in a Managed Client environment using WiseManager to manage workstations. Second, it demonstrates how this power can be implemented utlizing the simple drag and drop functionality made possible with the WorkPlace Shell. This powerful implementation often overlooked and under appreciated. However, WiseManager makes excellent use of this technology to support the administration of operations in the computing environment.

Drag and Drop Application Deployment

This same drag-and-drop action is all that is required to install or deploy either an application or hardware item onto a client machine. In addition, users can set up application groups and perform drag-and-drop deployment of a number of applications to a client machine. The WiseManager - Enterprise Edition also support drag-and-drop application deployment on a work-group, server, and domain basis. Deploying an application to hundreds of machines requires only one drag-and-drop mouse action!

The standard WiseManager installation CD comes with a set of configurations for a number of common OS/2 applications. Other than "free-ware", "trial-ware", or standard applications (such as Netscape), the "gut" of the individual program packages are not included. In order to set up an existing licensed or in-house package to be "deployable", you must follow the instructions in the Application section of this manual.