4.2.4 Migrating the Primary Domain Controller

4.3 Performing the Migration

This section shows how to perform the migration using OS/2 Warp Server for e-business. You may have noticed that no boot diskettes are shipped with the server. This is because CD-ROM #1 is a bootable CD-ROM. If the new machine where OS/2 Warp Server for e-business is being installed does not support booting from a CD-ROM, you can create the set of three boot diskettes with the CDINST command.

4.3.1 Installing the OS/2 Base Operating System

The first migration task deals with migrating the previous base operating system to the level of OS/2 Warp Server for e-business. Perform the following steps:

1. Insert the OS/2 Warp Server for e-business CD-ROM in the machine's CD-ROM drive and insert the first boot diskette (Installation Diskette) in drive A:

   Note: Machines that support booting from CD-ROM don't need to boot from boot diskettes since the OS/2 Warp Server CD-ROM is bootable. Insert the first CD-ROM instead and skip the diskette-changing step.

2. Shut down the system and reboot.

3. Insert Diskettes 1 and 2 as prompted. If the CD-ROM was not inserted in the step before, you'll be prompted to do so.

   When .ADD filters are loaded from Diskette 2, some warning messages might be displayed informing you that some Adaptec drivers cannot be loaded (AIC7870.ADD and AIC78U2.ADD), which can be ignored if your hardware does not have these adapters.

   When Diskette 2 has finished loading, the installation program will inspect your system for availability of logical volumes.

   Since it is the first time you are installing OS/2 Warp Server for e-business, you will receive a message stating that some compatibility volumes have been created, and that you need to reboot your system.

   OS/2 Warp Server for e-business uses a new disk managing technique based on logical volumes. As long as you do not use the new Journal File System (and up to now, you don't), the main difference you'll notice is that the disks are now managed by the Logical Volume Manager, LVM, not FDISK anymore. FDISK, as a command and utility, is no longer available.
   
   

   Note

   Since FDISK is no longer shipped with OS/2 Warp Server for e-business, you might need to modify your self-written utility programs that rely on FDISK. For example, if you used the FDISK /QUERY command to determine the CD-ROM drive letter, you would need to rework this procedure using the LVM /QUERY command. Note that the output text has changed. Also worth mentioning is that logical volumes can be assigned any drive letter, and the CD-ROM drive letter can have a fixed one. If you need to rely on the output of FDISK, to avoid overriding, you can rename FDISK.COM (located in the \OS2 directory of your current installation) to another name, such as OFDISK.COM. However, only use the /QUERY parameter since the old FDISK cannot cope with logical volumes. Not doing so might result in very serious problems. If you rename the old FDISK.COM file to be able to use its output, modify your self-written programs to accommodate the new name and double check that only the /QUERY parameter is used.

   
   
   

   The installation program continues by displaying a Welcome screen that lists the components and services offered by the product and introduces the panel-driven installation. The following describes the various steps of the process:

   1. Preparing the system
      • Select the install volume

      • Format the volume if necessary. (In our case of a migration, we will obviously not format the volume.)

      • Copy the system files

   2. Configuring hardware and software options

   3. Installing and configuring the server components

   The Installation Volume Selection is displayed.

4. Choose the option that says Specify another volume, even if the Accept the selected volume option is highlighted. Hit Enter to continue.

   The LVM text mode screen is presented to you. Only your previously bootable partitions are displayed. Don't panic, the other partitions are still there, but the LVM started in the Logical View mode and only the bootable partitions have been associated automatically with volumes. These volumes have not, however, an assigned drive letter. You will need to provide one.

5. Using the arrow keys, highlight the volume you want and press Enter.

   Like in the old FDISK screen, a menu is displayed to you where you can select Change the Volume Drive Letter.

   You are prompted with a list to indicate the drive letter you want to assign to this volume. Repeat that step for all the bootable partitions you have. At this time, don't forget to indicate on which partition you want OS/2 Warp Server for e-business to be installed.

6. Assign drive letters to the remaining partitions of your disks using LVM. To locate them, use the Physical view by pressing the F5 key.

   Their previous labels are not displayed anymore. Instead, remaining partitions are given some names, such as [A 1], [A 2]... . Switch back to the logical view by pressing F5 to create logical volumes.

   Since those partitions are likely to be data partitions, in the following window, you may choose Create a volume that does not need to be bootable. This creates a Compatibility Volume (a volume that is associated with only one partition) or a Logical Volume (they can be associated with more that one partition, assuming they are JFS-formatted).

   When defining a volume, you need to assign a drive letter to it (using the same process as described before). The system asks you about the associated partition (you can create a new one or use an already existing one).

7. Since the drive letters have been modified, the system needs to be restarted. Re-insert the installation diskette and press Ctrl-Alt-Del.

   After the reboot, the newly-defined volume will match your specifications, and you will be able to continue the migration process.
   
   

   Another Method
   You can also (if needed) directly call the VCU.EXE program that is located in the \OS2IMAGE\DISK_6 subdirectory of the CD-ROM. You will then receive a message informing you that the compatibility volumes have been created, and that the system needs to be rebooted.

   
   
   

   When you accept the installation volume (you may need to double-check the LVM screen to be sure), the next step consists of specifying what to do with the selected installation volume. The associated screen displays three choices:

   1. Not formatting the volume (needed for a migration and the one you should choose).

   2. Performing a long format of the volume (the best choice for a new installation).

   3. Performing a quick format of the volume (very fast but may leave some unmarked bad blocks on your disk and possibly cause problems later). This option was the default choice for the previous OS/2 Warp Server version. The more experienced user exited to a command line to execute the FORMAT /L long format command instead.

8. If your machine uses the HPFS386 file system, an information window is displayed providing you the last chance to remove the ACLs. You can use the F3 key here to get a command prompt or press Enter to continue with the installation.

   This installs the OS/2 base operating system to your machine.

9. After all files have been copied to the machine, you will be prompted to reboot the machine. Perform as prompted.

10. Define your system configuration as shown in Figure 22 and Figure 23. Note that these windows have not changed from the OS/2 Warp 4 install.
    
    
    
    Figure 22: System Configuration Panel (1 of 2)
    
    

Pay attention to the video display that has been detected by the installation program. Previously installed video drivers are not detected and will not be used. If the one presented doesn't exactly match your display adapter, select Video Graphics Array (VGA) from the list. This will guarantee the system starts properly. After the migration has completed, you may install your display driver in a separate step using, for example, the DSPINSTL utility or the display installation program that came with the display adapter.



Figure 23: System Configuration Panel (2 of 2)

1. Even if the country was selected in the first configuration panel, you will be presented with the following window where you can select the default and secondary code pages that will be used by your system (850,437 which covers the broadest set of national characters available for Western Europe and English speaking countries is certainly the best choice for these areas).

   If you select an European country, you'll even be able to select the use of the European locale. This ensures the Year 2000 compliance of your server in these locations.
   
   
   Figure 24: Country Information Panel
   
   

2. The usual printer selection panel is then displayed, and you can, if needed, indicate the primary printer associated with the server. If you don't have any preferences, you may install the IBMNULL printer driver. This ensures ASCII text printing from a printer that can be attached to the server.

   When all these elements (more or less relative to the hardware) have been collected, the installation program enters its last phase.

   You have to specify the elements you want to have added to the base operating system. Unless you have good reasons, we advise you to install as few elements as possible: An OS/2-based server generally runs unattended and is mostly controlled by remote REXX programs and is definitely not a development platform.

   Also, note that this phase, just as the preceding one, can be easily restarted after the migration by executing INSTALL from the command line or by clicking on the Selective Installation icon.
   
   
   
   Figure 25: Selecting the Optional System Components
   
   

3. As shown in Figure 25, we have only selected Fonts (to have a system that will be able to take advantage of the Unicode support), System Utilities, and System Components.

   We have suppressed any DOS Support, Multimedia, Development, and the Tools and Games. (On the CD-ROM that will come with this book, you'll find plenty of OS/2 and Server-oriented tools.) However, if you plan to run OS/2 Warp Server for e-business as a Java Server, we recommend selecting Java Development.

   The following three figures show the windows selected in the previous step when pressing the corresponding More... button. Figure 26 shows that only Unicode Fonts, which is the default, is selected.
   
   
   
   Figure 26: Fonts Selection Window
   
   

Figure 27 displays the System Utilities selection window. All system components but Sort Filter (which, for European countries, doesn't sort at all) are selected.



Figure 27: System Utilities Selection Window

Figure 28 displays the System Components selection window. The JFS file system will be installed.



Figure 28: Systems Components Selection Window

1. As shown in Figure 29, the last OS/2-related pop-up window appears prompting you how to cope with your previous configuration. Both check boxes are already selected for you. Since it is desirable to migrate previous configuration files and to have the opportunity to make changes to the new CONFIG.SYS file (some previous settings, such as SET PROMPT, are not transferred), press OK to continue.
   
   
   
   Figure 29: Previous Configuration Handling through Advanced Options Window
   
   

4.3.2 Installing the LAN Server Components

The second migration task deals with migrating the previous LAN Server component to the level of OS/2 Warp Server for e-business. After the OS/2 base operating system migration has completed, the installation of the server component will be started, as shown in Figure 30. Perform the following steps:



Figure 30: Server Component Installation

As shown in Figure 31, you are prompted to select the services you want to install. For each component you select, the installation program will prompt you to provide configuration information. In case the selected component was previously installed, configuration information will be migrated. However, you still will have a chance to make changes to it.

Note that some components are checked by default, for example, TCP/IP Services, and others are mandatory to install, such as Netscape Communicator. The Current Status list informs you whether or not available components were installed before and what level they are, for example, current version or downlevel version.



Figure 31: Server Components Selection

1. Click Next to continue the installation process. As shown in Figure 32, the OS/2 Warp Server for e-business Configuration panel will be presented to you.

   Because all configuration information has been retrieved from a previous installation, most items are marked with a blue dash, which means that acceptable default settings can be used.

Note
When migrating a Primary Domain Controller, an additional and to-be-configured item is added to the list. You will be required to provide an administrator ID along with a password.

Figure 32: OS/2 Warp Server for e-business Configuration Window

Go from item to item to check or change configuration information. Especially pay attention to the items that are preceded by a red-colored arrow.

As shown in Figure 33, the previously defined server and domain names were retrieved.



Figure 33: Previous Configuration Values are Preserved

1. When you click on the Install button, you will be prompted to confirm your selection by clicking on OK to complete the installation (see Figure 34).
   
   
   
   Figure 34: Starting the Installation
   
   

   In general, the NetBIOS parameters that were set previously are not considered as appropriate by the Tuning Assistant, which will tune them again. An information window will be presented to you, as shown in Figure 35.
   
   
   
   Figure 35: Information from the Warp Server Tuning Assistant
   
   

   You may, however, have good reasons to use the previous NetBIOS parameters. As indicated in the shown message, the previous PROTOCOL.INI file is copied in the \OS2\INSTALL\ directory with the file name of WARPSRV.BAK.

2. Click OK to continue.

   All selected components will be installed now, and many files are copied. A progress indicator informs you about the installation progress.

3. You are now presented with the Migrate CONFIG.SYS/AUTOEXEC.BAT window, as shown in Figure 36, showing you the modifications that will be performed to the two configuration files.
   
   
   
   Figure 36: CONFIG.SYS before and after Migration
   
   

Figure 36 shows you that our server was previously using HPFS386 (first line in the left list) and that the new CONFIG.SYS (the right part) does not reflect the HPFS386 installable file system anymore. This is normal: It will take a further reboot to install it. So, please resist the temptation to modify the IFS part of the new CONFIG.SYS and rely on the install program do it in a timely manner.

You can also notice that, on the right part, we have manually removed the BASEDEV=AIC78U2.ADD line (it usually appears on the second line below the CLASSPATH definition). Our machine does not have Adaptec adapters. Don't forget then to press the Save button before pressing the Quit button in order to save your modifications. The modifications you perform are not checked before you save them. Make modifications only if you're absolutely sure they will not induce an error during the next reboot. Good candidates for modifications are listed below:

SET PROMPT=($r)[$p]

Modify the prompt in order to display the return code of the previous command between parenthesis before the current path.

SET TZ=CST6CDT

Set the time zone to reflect Central USA. (If you need some more elements to set the time zone of your machine correctly, you can get an excellent freeware, TIME868, which offers a very nice time zone calculator.)

SET AUTOSTART=TASKLIST,FOLDERS,WARPCENTER

Remove Programs and Connections from the AUTOSTART line. That prevents the automatic restart of any unwanted program, such as the Reconnect window at start-up of your server.

SET RESTARTOBJECTS=STARTUPFOLDERSONLY

Restrict the automated restart to the objects that will be put in any folder having the startup attribute set (there is one by default in OS/2 Warp, but you may define others).

SET SCUSEPRETTYCLOCK=YES

Modify the aspect of the OS/2 Warp Center (formerly called Smart Center, hence, the SC prefix) to have it display a nicer clock than the default one.

SET SCKILLFEATUREENABLED=YES

Enables killing a running process by obtaining the list of the running process using a Ctrl-Click on the Windows list button.

SET SCFINDUTILITY=D:\OS2\APPS\PMSEEK.EXE

Replaces the object find program by the more usable PMSeek application.

Depending on your machine type, you may want to remove unnecessary device drivers, such as either IBM1FLPY.ADD or IBM2FLPY.ADD.

4.4 Behind the Scenes