Removing Files from Startup
Directory and SYS:SYSTEM ...11
Removing Unsupported DOS
Utilities ...................................12
Copying Files ...........................13
Copying Startup Files and
Drivers....................................13
Copying Files to SYSTEM,
PUBLIC, and LOGIN
Directories..............................14
Copying Necessary Script
Files....................................... 16
Copying and Uncompressing
Java Files...............................16
Copying and Uncompressing
Novell ConsoleOne Files......... 17
Copying New Install Files........ 17
Copying NetWare NDPS
Utilities ...................................18
Putting the Finishing
Touches....................................18
Appendix – Example Script...... 20
Scripts to Upgrade from
NetWare 4 to NetWare 5 on
Compaq Servers
Abstract: The migration of a multi-server network from
NetWare 4.x to NetWare 5 can be a time consuming task. By taking
advantage of the Novell installation scripting language CDWare,
introduced with NetWare 4, you can eliminate the time spent in
repeating the upgrade at multiple consoles. Since no two server
environments are identical, it would be impossible to develop a script
that properly addresses the specific needs of every migration. This
paper, however, outlines the steps necessary in a migration script so
that you may develop your own script, customized to your server
environment. The included sample script reaches beyond basic
scripting and provides enhancements like Compaq hardware driver
updating.
Help us improve our technical communication. Let us know what you think
about the technical information in this document. Your feedback is valuable
and will help us structure future communications. Please send your
comments to: Novell.Feedback@Compaq.com
Page 2
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers2
Notice
The information in this publication is subject to change without notice and is provided “AS IS” WITHOUT
WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS
INFORMATION REMAINS WITH RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE FOR
ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE OR OTHER DAMAGES
WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS
PROFITS, BUSINESS INTERRUPTION OR LOSS OF BUSINESS INFORMATION), EVEN IF
COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The limited warranties for Compaq products are exclusively set forth in the documentation accompanying
such products. Nothing herein should be construed as constituting a further or additional warranty.
This publication does not constitute an endorsement of the product or products that were tested. The
configuration or configurations tested or described may or may not be the only available solution. This test
is not a determination or product quality or correctness, nor does it ensure compliance with any federal,,
state, or local requirements.
Product names mentioned herein may be trademarks and/or registered trademarks of their respective
companies.
Compaq, Contura, Deskpro, Fastart, Compaq Insight Manager, LTE, PageMarq, Systempro, Systempro/LT,
ProLiant, TwinTray, ROMPaq, LicensePaq, QVision, SLT, ProLinea, SmartStart, NetFlex, DirectPlus,
QuickFind, RemotePaq, BackPaq, TechPaq, SpeedPaq, QuickBack, PaqFax, Presario, SilentCool,
CompaqCare (design), Aero, SmartStation, MiniStation, and PaqRap are registered with the United States
Patent and Trademark Office.
Netelligent, Armada, Cruiser, Concerto, QuickChoice, ProSignia, Systempro/XL, Net1, LTE Elite,
Vocalyst, PageMate, SoftPaq, FirstPaq, SolutionPaq, EasyPoint, EZ Help, MaxLight, MultiLock,
QuickBlank, QuickLock, UltraView, Innovate logo, Wonder Tools logo in black/white and color, and
Compaq PC Card Solution logo are trademarks and/or service marks of Compaq Computer Corporation.
Microsoft, Windows, Windows NT, Windows NT Server and Workstation, and Microsoft SQL Server for
Windows NT are trademarks and/or registered trademarks of Microsoft Corporation.
NetWare and Novell are registered trademarks and intraNetWare, NDS, and Novell Directory Services are
trademarks of Novell, Inc.
Integration Note prepared by Novell Integration
First Edition (November 1998)
Document Number ECG0351198
ECG0351198
Page 3
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers3
CDROM.NLM
uncompress
uncompress
NDPS
Reboot the server
Remove obsolete
Install
Run
Run
Script-Based Migration
When managing a large, multi-server network, migrating to a new OS version is quite a task.
Days of complete or partial downtime are often needed to complete the migration. Developing
and using your own migration script can upgrade your entire network as fast as migrating a single
server.
Successful script migration begins with an understanding of the scripting language and ends with
extensive testing before deployment. In this document, we provide insight into the actions that
must be called by a script to migrate from NetWare 4.x to NetWare 5. In addition, the name and
location of all files that must be copied or deleted for a baseline NetWare 5 server are provided,
along with destinations and modifications for the files that are being copied. Finally, a complete
example script is provided in the Appendix.
IMPORTANT: The filenames, examples, and procedures given do not include references to any
third party or after-market products that you may need to update or upgrade for NetWare 5.
Please contact your software vendor for any relevant changes that you should add to your custom
script.
The flowchart below details the steps in preparing, launching, and completing a script-based
migration.
Backup all
servers that will
be upgraded
Upgrade NDS
Master replica
server using
Novell
installation utility
Mount the
Gather user
licenses
Steps you should perform to prepare servers for migration
NetWare 5 CD
as a NetWare
volume on the
master server
Insert the NetWare 5 CD in the CD-ROM drive on
drives: IDEATA.HAM and IDECD.CDM. For SCSI
Load
the upgrade master server
Load the appropriate CD-ROM driver. For IDE
drives: CPQSCSI.HAM SCSICD.CDM
and the CD will automatically be
mounted as volume NETWARE5:
Place the script
and any .NLMs
called by the
script in a
directory on the
master server
Define installation
variables
uncompress Java
installation files
Copy Compaq
NWPA drivers
Load INSTALL at
the server to be
upgraded via the
script
C:\NWSERVER
SYS:SYSTEM
Copy and
files from
and
Select
Product Options/
Install Product Not
Listed
Remove obsolete
user files from
Copy and
NetWare 5 GUI
components
SETUPNLS.NLM
Steps necessary to initiate migration at the console
SYS:PUBLIC
Copy and
ConsoleOne files
Autodetect
hardware
Steps that should be performed by the script
Steps that you should perform after the script has run
Figure 1. Script-based migration overview
Press F3 to specify the path
to the MASTER server that
points to the migration script.
For example MASTER\
SYS:SCRIPT
Copy necessary
script files to
C:\NWSERVER
Delete
uncompressed
Novell
Licenses
archives for Java,
ConsoleOne, and
NetWare 5 GUI
Perform NDS
update
Configure
cryptography, if
applicable
Enter valid
username and
password at the
remote login
screen
Backup user
configuration files
Copy NetWare
administration
utilities
Edit AUTOEXEC.NCF and
STARTUP.NCF to reflect changes in
LOAD and SET statements necessary
for NetWare 5 compatibility
INETCFG.NLM
Once logged in, the
remote server will
begin running the first
.IPS script found in
the remote directory
Copy files to
SYS:SYSTEM,
SYS:PUBLIC,
and SYS:LOGIN
Convert SMP
support to
NetWare 5
Restore user
configuration files
ECG0351198
Page 4
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers4
Developing Your Own Script
IMPORTANT: Developing a migration script is a complex task and is recommended only for
experienced system administrators. Improper implementation can cause loss of data and
prolonged server downtime. Backup any data before attempting an automated migration. Please
be sure that you are confident in your scripting before attempting to migrate your network using
your script.
What is a Script?
In order to facilitate custom NetWare installations, Novell created CDWare installation scripting.
Although CDWare was originally developed to allow OEMs to create hardware-specific
installations of the NetWare installation procedure, you can use CDWare to create a noninteractive batch installation of your NetWare configuration. This document illustrates, through a
complete example, specifically how you can use CDWare to migrate from NetWare 4.x to
NetWare 5.
An installation script is simply a text file. When interpreted by the NetWare installation
application, however, the script provides customized instructions for the installation. By placing
any user-options in the script file, the process can be automated, requiring little user intervention.
In large, multi-server networks this automation can considerably accelerate your migration. The
added ability to remotely launch the script can also speed the process by allowing simultaneous
migration of multiple servers on your network. In addition, your script provides you with a tool
for swiftly adding new or restored servers to your network.
Developing a script to shorten the migration process, however, is neither a fast nor simple
process. The scripting language has numerous commands, each with its own syntax and
parameters. Even a basic installation script requires a solid understanding of CDWare scripting.
Furthermore, an intensive script, such as, a multiple-server migration script, should undergo
extensive testing before it is implemented on the entire network. If you are proficient in, or even
familiar with, scripting, the time you invest in developing a script is minimal compared to the
time that would have to be spent at each server console doing local migrations.
Before You Begin
In order to get started on developing your custom migration script, you should become familiar
with the sample scripts available from Novell and the sample script in the Appendix. For our
purposes, the scripts that Novell has released (one with the intraNetWare service pack called
411SPACK.IPS and the other UPGRADE.IPS from the Novell Accelerated Upgrade utility) will
provide the most applicable examples of using CDWare scripting for upgrading NetWare
components. This document includes a sample script that was developed by Compaq to illustrate
the power and flexibility of the scripting language and, at the same time, provide a solid example
of a thorough script with good scripting style. In addition, the Compaq script addresses some
issues specific to Compaq hardware, such as, automatic DDFS to NWPA storage driver
replacement. Before developing your own script, you should use these examples to become
familiar with the purpose and format of the commands in the sample script. For additional
information and the example scripts mentioned above, search the Novell website for CDWarescripts or Accelerated Upgrade Utility.
ECG0351198
Page 5
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers5
Migration Tasks
After becoming familiar with the commands in the sample scripts, you will need to outline the
tasks necessary to complete the NetWare migration. Although there is no one script that will
cover every server configuration, internal Compaq migration scripts complete the following tasks:
Creating the script environment
• Transferring any files necessary for the script to complete to the master server
• Defining any internal variables used within the script
Removing old files, patches, and utilities
• Removing outdated system patches and products that may be incompatible
• Removing old NetWare 4 files from the startup directory and SYS:SYSTEM
• Removing any DOS utilities that are unsupported in NetWare 5
Copying files
• Copying necessary script files to the boot directory
• Copying server startup files and drivers
• Copying NetWare SYSTEM, PUBLIC, and LOGIN directories and files
• Copying and uncompressing Java files
• Copying and uncompressing Novell ConsoleOne files
• Copying NetWare 5 GUI components
• Copying NetWare NDPS administration utilities
Putting the finishing touches
• Converting storage driver LOAD statements from DDFS drivers to NWPA drivers
• Rebooting the server after copying files
• Auto-detecting hardware after reboot
Not all of these tasks can or should be used in every script, nor is this a complete list of actions
that can be performed. Your script, for example, may convert the statements that load the storage
drivers to reflect the newer NWPA drivers. In this case, the automatic hardware detection is not
necessary.
For all of these steps, however, there may be many files that are deleted, copied, or renamed.
Perhaps the most difficult task in developing your own script is identifying which files are
incompatible with and which are essential to NetWare 5. This document handles that confusion
for you with detailed lists of files complete with sources and destinations. Another aspect of wellwritten scripts is portability.
ECG0351198
A more portable script can be modified more easily to accommodate minor differences between
server environments. You may want to begin your script by gathering variables that may change
for different installations. By doing so, you can eliminate editing your script should you need to
perform a modified installation, such as a different destination directory or different language
installation
Page 6
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers6
Creating a fully functioning NetWare 5 server without any user input is impossible. While the
example script provided in the Appendix completes all necessary file manipulation, there are a
few key elements that require specific input to make your NetWare 5 server fully operational.
Specifically, after migrating your server with your script, you will need to run SETUPNLS.NLM
to convert NetWare 4.11 licensing schemas to the newer NetWare 5 format. Also, you should run
INETCFG.NLM to setup the network components, including IP.
The Sample Script
The script in the Appendix was developed internally at Compaq for the purposes of illustrating
proper scripting style and necessary actions for migrating your server. Every effort has been made
to produce a script that represents portability and stability. Features such as log files, path
variables, and migration conflict detection may not be necessary for successful scripting but in a
critical environment may be well worth the time to implement. Where noticeable, extra features
or aspects of the script will be highlighted.
Before running the sample script or a script of your own, you should copy the following files and
the script itself to the master server: ICMD.NLM, CPQICMD.NLM, and NDSDIBUP.NLM. Both
ICMD.NLM and NDSDIBUP.NLM are included with the Accelerated Upgrade Utility from
Novell and CPQICMD.NLM is available as part of the Compaq Support Software for Novell
Products (Novell SSD). Once initiated, the sample script takes roughly 35 minutes to complete on
a ProLiant 5000 over a dedicated 100BASE-T Ethernet connection. Upon rebooting, the ProLiant
is a fully functional NetWare 5 server, requiring only the minimal manual configuration
mentioned. The sample script, as it appears in the Appendix, requires at least 9 MB of free space
on the DOS partition and 165 MB of free space on the SYS: partition. Compaq recommends that
you issue the PURGE command both before and after the script is run to make sure that deleted
files waste no disk space.
Note: After migrating with the sample script, you may have trouble logging into the server as
ADMIN. This is not an error. With the NetWare 5, you must specify the context of the admin
login. To find the context for a given server, issue the CONFIG command at the server console.
The context should be appended to the admin login, for example ADMIN.CPQ, where .CPQ is
the context.
The rest of this document provides a walkthrough of the script in the Appendix, including the
files that should be affected by your script and extra steps taken to ensure success when using the
script. By developing your own script that accomplishes these tasks, you can automate the vast
majority of the migration and save your organization many hours of downtime.
Creating the Script Environment
In order to facilitate the steps called by the script, steps should be taken to prepare the script
environment with variable and menu item declarations and name space modules.
Defining Variables and Menu Items
While this is not necessary in your migration script, using variables and menus will make your
script more portable with a minimum of effort. In addition, by defining the variables within the
script, you reduce the amount of console intervention. Your script may contain as many or as few
variables as you feel necessary. In the sample script several variables are defined and used
throughout.
ECG0351198
Page 7
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers7
Table 1. Defined variables
Variable nameValueDescription
TRUE1
FALSE0
SRCSRVRName of the master server that has
the NetWare 5 CD mounted.
SRCNW5%{SRCSRVR}\\NETWARE5:Location and path to the NetWare 5 CD
SRCSYS%{SRCSRVR}\\SYS:
SRCSCRIPT%{SRCSYS}SCRIPT
SRCPOET%{SRCSRVR}\\SYS:\\NI\\POET\\NLMLocation of POET files needed for migration
NWBOOTC:\\NWSERVER
NWSYSSYS:Volume name of the SYS: volume
NWSYSTEMSYS:SYSTEM
NWPUBLICSYS:PUBLIC
NWLOGINSYS:LOGINLocation of the LOGIN directory on the SYS:
General definition for clarity when used in script
By defining the name of the master server within
the script itself, the script can be run from different
master servers by redefining the variable.
Location of the SYS: directory on the master
server
Location of the script file and necessary support
.NLMs
Path of the boot directory containing
SERVER.EXE
Location of the SYSTEM directory on the SYS:
volume
Location of the PUBLIC directory on the SYS:
volume
volume
When commands within your script use variables as pathnames, it is not sufficient to simply have
defined the variable. In order for the script to correctly interpret your string variable as a path, the
variable must be associated with a path using the GetPath command. The following path variables
are defined in the sample script with the GetPath command.
In the example script in the Appendix, the different actions to be performed have been separated
into independent sub-modules. Each of these sub-modules has an associated variable which
allows the installation of that component to be enabled or disabled. Once again, this was done to
make the script as portable as possible by allowing certain elements of the migration which are
not necessary to be skipped. In the script, these variables can be identified by the word Flag at the
beginning. The use of Flag is not specific to the scripting language. This is simply a matter of
scripting style; any non-reserved variable names can be used to label elements in your script.
ECG0351198
Page 8
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers8
Table 3. Flag variables to denote key actions of the script
By setting any of the above variables to %{false} in the example script, you can prevent the
respective section from executing. The example script in the Appendix extends the function of the
Flag variables by performing a check to make sure that the components selected to install do not
cause any known conflicts.
Additionally, the example script creates a log file of all actions performed by the script. Should
you perform the migration and afterwards wish to review which elements of your script had been
selected, you may find adding the extra lines of code necessary very useful. The code that
appends the text for each action to the log file can be found near the beginning of each separate
section. For example,
In order to view the log generated by the sample script, load NWCONFIG.NLM and select
View/Change/Remove installed options from the Product Options menu.
Preparing the Server Environment for Migration
At this point in the sample script, there are a few actions that prepare the server environment to be
updated. Not all of these actions should be performed in any single migration. That is, some
actions will undo the effects of another, or one action could lead to a conflict with another.
However, some of these actions must be complete to successfully copy the full NetWare 5 file
system onto your server.
Add long name space
Adding long name space is necessary for correct uncompressing of files. Therefore, this
step is necessary if Java, ConsoleOne, and the NetWare 5 GUI are to be installed. To add
long name space, your script needs load OS2.NAM and LONG.NAM.
Update the STARTUP.NCF
In the example script, any SET parameters found in the STARTUP.NCF are commented
out. While this step is not absolutely necessary, it makes sure that there are no conflicts
between NetWare 5 and older NetWare 4.11 parameters. This step may not be necessary
if automatic hardware detection is used or if you are using a master copy STARTUP.NCF.
ECG0351198
Page 9
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers9
Convert SMP support
Unlike NetWare 4.11, NetWare 5 does not require separate kernels for single- and
multiprocessor platforms. As a result, the sample script comments out all LOAD
statements in both the AUTOEXEC.NCF and STARTUP.NCF files that refer to
NetWare 4.x multiprocessor specific modules. In addition, lines are added that will load
the NetWare 5 platform support modules upon rebooting. This step is not necessary if
automatic hardware detection is used.
Convert storage drivers from DDFS to NWPA
Specific to Compaq systems, this portion of the sample script will comment out any
LOAD statements that refer to any DDFS Compaq storage drivers. At the same time, the
example script will add the appropriate NWPA storage driver load statements to the
AUTOEXEC.NCF and STARTUP.NCF files. Once again, this is for Compaq hardware
only. This step may not be necessary if automatic hardware detection is used. But, since
NetWare 5 no longer supports DDFS, either automatic detection or this section of the
sample script should be used to convert to NWPA drivers.
Prepare for hardware autodetect on reboot
If automatic hardware detection is selected, the sample script removes the current
STARTUP.NCF, copies necessary files for the detection, and generates a new
STARTUP.NCF file that will initiate the automatic hardware detection on reboot. While
automatic hardware detection can eliminate some of the steps above, the detection will
most likely require user interaction to locate Compaq and third-party drivers.
The list of files necessary for hardware detection follows.
Table 4. Files to be copied for hardware detection
If you already have a version of a STARTUP.NCF for NetWare 5 with support for your
hardware, you may wish to place that file in the same directory as the script file on the
master server and have your script copy that file to the server being migrated. The sample
script will not execute if you are using a master STARTUP.NCF and performing hardware
Page 10
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers10
detection or DDFS to NWPA conversion, since performing hardware detection or the
DDFS to NWPA conversion will modify the STARTUP.NCF.
Each of these steps is labeled in the example script. When the sample script is run, there is a
check to ensure that any incompatibilities between these actions will terminate the script; for
example, converting to NWPA and autodetect hardware or installing Java without long name
space installed.
Removing Old Files, Patches, and Utilities
Obviously, some components of NetWare 4 are incompatible with the newer NetWare 5
architecture. Patches for NetWare 4 that have been integrated into NetWare 5, unsupported
utilities, and outdated files should be removed.
Removing Outdated Patches and Products
To eliminate any potential incompatibilities between NetWare 4.11 patches and NetWare 5, your
script should remove all traces of any patches. Luckily, CDWare scripting provides an integrated
function for removing patches. The syntax is somewhat cryptic and documentation on this
command is sparse. The section of the example script was generated by Novell to remove any
publicly available patches. The list of patches that are removed follows.
Table 5. Outdated patches to be removed before migration
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers11
Due to the number of entries and the undefined syntax of the PI_EditNCF_KEYSTRINGS
command, Compaq recommends that you use this section of the script exactly as it appears in the
example rather than coding your own.
Likewise, there are several large updates and patches for NetWare 4.11 that should be uninstalled
before the migration. Unlike the previous list of patches, these products should be uninstalled by
calling UINSTALL.NLM within your script.
Table 6. Products to be uninstalled using UInstall.NLM
Removing Files from Startup Directory and
SYS:SYSTEM
There are many files that have been replaced, modified, or eliminated for NetWare 5. Before you
begin the migration, your script should remove these files to ensure that any possible conflicts are
eliminated. The sample script shows how to remove all of the following files.
Table 7 lists files to be deleted in the NetWare boot directory, which is by default
C:\NWSERVER.
There are some utilities scattered about a NetWare 4.11 server that are no longer supported or
have been replaced in NetWare 5. Your script should remove each of these.
The following table lists files that reside on the SYS volume in the PUBLIC directory and that
should be erased by your script.
Table 9. The following utilities should be removed from the SYS:PUBLIC directory.
Similarly, your script should remove the following files from the SYS:LOGIN directory.
Table 10. Files to be removed from SYS:LOGIN
ATTACH.BATMENU_X.BATNLIST.EXETYPEMSG.EXE
NetWare 4.11 .PSMs are not compatible with the architecture of NetWare 5. For that reason, your
script should remove any .PSM and .MDI files remaining on the server.
Table 11. .PSM and .MDI files to be removed
Files in NWBOOT Files in NWSYSTEM
*.PSM*.MDI*.PSM*.MDI
Copying Files
The heart of the NetWare migration is copying the new NetWare 5 files to the server but the
script must also copy many other files for a successful migration. Drivers, additional script files,
support files, and utilities should also be copied as detailed below.
Copying Startup Files and Drivers
To make all drivers and necessary boot files available to the OS, your script should copy several
files to the NWBOOT directory.
Table 12. Drivers and startup files that should be copied to NWBOOT
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers14
Directory contentsDRIVERS\STORAGE\C:\NWSERVER\DRIVERS
Directory contentsDRIVERS\STORAGE\NLS\C:\NWSERVER\NLS
Directory contentsDRIVERS\STORAGE\NLS\%{LANG}\C:\NWSERVER\NLS\%{LANG}
Directory contents and subdirectoriesDRIVERS\SBD\C:\NWSERVER\DRIVERS
Copying Files to SYSTEM, PUBLIC, and LOGIN
Directories
There are several user configuration files from NetWare 4.x that can be used for your NetWare 5
server. Preserving these files can save time in configuring NetWare 5. Unfortunately, the files
reside on the NetWare CD among many necessary files; copying the entire source directory from
the CD would overwrite your configuration files. It is possible to specify every other file, besides
the default configuration files on the CD, to be copied, but it is easier for your script to make a
temporary backup of the following files and replace them after the NetWare 5 default versions are
copied to your server.
The configuration files that should be backed up follow.
Table 13. Configuration files that should be backed up
At this point, your script should restore the configuration files which it had previously backed-up
to their original locations
Copying Necessary Script Files
Several script files must be copied from the NetWare 5 CD to the C:\NWSERVER DOS partition.
When copying these files, your script should also set the attributes for the file to disable the
read-only parameter.
When your script has copied the files to SYS:, you should call the NLMexec function to launch
TAR to extract the files. When calling TAR, your script should specify the xvfD parameters so
that the files are extracted to the correct subdirectory. An example is shown below.
NLMexec 1, SYS:SYSTEM\\TAR xvfD BEANS.TAR
After extracting the files, have your script delete the four compressed archives.
ECG0351198
Source
Directory
Destination
Directory
Page 17
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers17
Copying and Uncompressing Novell ConsoleOne Files
Similar to the Java installation, the ConsoleOne files reside on the NetWare 5 CD as compressed
archives. In order to install ConsoleOne, your script should copy the archives, extract the files
with directory structure intact, then delete the original compressed files copied from the CD. The
archives that contain ConsoleOne are listed below.
Table 17. Files to be copied and extracted for ConsoleOne installation
When your script has copied the files to SYS:, you should call the NLMexec function to launch
TAR to extract the files. When calling TAR, your script should specify the xvfD parameters so
that the files are extracted to the correct subdirectory. An example is shown below.
NLMexec 1, SYS:SYSTEM\\TAR xvfD CONSOLE1.TAR
After extracting the files, have your script delete the four compressed archives.
Copying New Install Files
Once again, your script must copy and uncompress the archives, just as with the Java and
ConsoleOne components, to perform the installation.
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers18
CPDATA.NLMINSTALL\C:\NWSERVER
Directory contents and subdirectoriesINSTALL\JAVABIN\SYS:JAVA\BIN
Directory contents and subdirectoriesINSTALL\CFGS\SYS:SYSTEM
Perhaps the most troubling component of the script was the handling of the NetWare 5
encryption engines. The copying of the encryption engines as seen in the Appendix
provides only minimal encryption support through a NULL engine. If greater
cryptography is needed, you will need to configure the encryption according to the
Novell documentation.
Destination
Directory
SYS:PUBLIS\NLS\%{NWLANGNAME}
SYS:PUBLIC\WIN32\NLS\%{NWLANGNAME}
ECG0351198
Copying Updated Compaq Drivers
To make the migration script even more complete, the sample script copies all Compaq
drivers from the NetWare 5 CD to the server being migrated. If you have obtained newer
drivers than appear on the NetWare 5 CD, the script could easily copy them from the
Page 19
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers19
master server so that the machine you are upgrading would boot with the latest Compaq
drivers.
Performing Directory Services Update
Before the migration is complete, you must update the Novell Directory Services using
the NDSDIBUP.NLM available from Novell with the Accelerated Upgrade Utility. Since
this utility needs be run only once after the first reboot, the sample script adds the
necessary lines to the AUTOEXEC.NCF and then actually creates another script that will
remove these statements when the server reboots.
Modifying Startup Files
The sample script adds a few additional lines to the AUTOEXEC.NCF that will enable the
IPX networking for the server. Since NetWare 5 is native IP, these components are
loaded to ensure IPX compatibility.
Removing Third-Party Applications from AUTOEXEC.NCF
To eliminate any potential conflict between NetWare 5 and any third-party applications
on your server, the sample script searches the AUTOEXEC.NCF file and comments out
the load statement for SAMPLE.NLM. In developing your own script, you could replace
SAMPLE.NLM with any after-market application running on your server. By duplicating
the code and replacing the name for each custom .NLM loaded, you can prevent any
potential conflicts from interfering with your migration. After the script has completed,
you will need to uncomment the lines for the applications that are compatible with
NetWare 5.
Configuring the mouse port
With a new graphical interface, mouse support is a must for NetWare 5. The sample
script enables mouse support for either a serial or PS/2 mouse by modifying, or creating
if necessary, the files MOUSE.CFG and PRE_SRV.NCF.
Rebooting the Server
Finally, if you would like, you may have the script automatically reboot the server. This
step is not necessary in your script and, in some cases, not practical due to the number of
users currently accessing the server. If your script does not reboot the server, you can
perform the migration during regular operation, then reboot the server when server
activity is reduced to avoid the impact of momentarily downing the server. However, a
reboot, at some point, is necessary to have your server functioning as a NetWare 5 server.
ECG0351198
Page 20
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers20
Appendix – Example Script
@Version 5.00
@SyntaxVersion 1.03
; UPGRADE.IPS ** x86 Version **
;----------------------------------------------------------------------------; Sample NetWare 5 Migration Script
; Updates a NetWare 4.11 server to NetWare 5 with minimal user intervention
; User accepts responsibility and consequences of use!
;
; Requirements:
; 1) Master NDS replica updated to NW5 using NetWare 5 CD (Normal upgrade)
; 2) NetWare 5 CD available on a network server
; 3) On the same server as the NetWare 5 CD, this script is available
; 4) In the same directory as this script, the following helper NLMS:
; CPQICMD.NLM version 1.13 or later (from Compaq NSSD 5.01)
; ICMD.NLM version 3.07 or later from the NetWare 5 CD STARTUP directory
; NDSDIBUP.NLM version 1.00 or later from Novell
; 5) Update the following variables in the Global Variables section
; to match the configuration you with to use:
; SRCSRVR should be the name of the source system
; SRCNW5 should be the path to the NetWare 5 CD contents
; SRCSCRIPT should be the path to the script and associated utilities
; NWBOOT should be the directory that the target server boots from
;
; Instructions
; 1) Mount the NetWare 5 CD on the master replica server (not the target server)
; 2) Create a directory on the server for the migration kit
; 3) Copy this script and associated utilities to the script directory
; 4) Edit the appropriate global variables (below)
; 5) On the target system,
; a. Load INSTALL
; b. Select Product Options
; c. Select Install a product not listed
; d. Press F3 and enter the path to the script. eg, NW5:SYS\SCRIPT
; e. Supply a username and password for the source server
; f. Let the script run (requires about 35m across a 100Tx link)
; g. Proceed when the migration process is complete (1 reboot)
; 6) On the target system, LOAD SETUPNLS.NLM
; a. Update the licensing service
; 7) On the target system, LOAD NWCONFIG.NLM
; a. Install the NetWare 5 server license(s)
; 8) On the target system, LOAD INETCFG.NLM
; a. Update the networking
; 9) Install/configure any additional features/applications
;10) Reboot the server for all the changes to take place.
;-----------------------------------------------------------------------------
ECG0351198
;----------------------------------------------------------------------------; Transfer needed utilities to the local (target) server from the same
; location as the script.
; ICMD.NLM must be copied from the STARTUP directory on the NETWARE5 CD
; to the same directory as this script on the master server!
CopyToServer SYSTEM\NWUPDATE, ICMD.NLM, '', ''
CopyToServer SYSTEM\NWUPDATE, CPQICMD.NLM, '', ''
;-----------------------------------------------------------------------------
;----------------------------------------------------------------------------; Load the script command language extender.
Command NWUPDATE\ICMD
;-----------------------------------------------------------------------------
; Establish installation selection items below
; These items could be enabled through a menu (optional filesets), but this
; allows them to execute without user intervention. The only flag likely to be
; modified is FlagRebootServer (if you want to migrate but wait to down the
; server).
;
; Note: To prevent an installation action, set the flag to false (do not
; delete the flag). Otherwise a syntax error may occur.
;--------------------------------------------------------------------------; Last warning and splash screen
;--------------------------------------------------------------------------Display 0,
"яяяяяяяяяяяяяяяяNetWare 5 Migration Scriptяяяяяяяяяяяяяяяя\n
This script will attempt to migrate a server from NetWare 4 to NetWare 5. If
you continue, the migration will proceed.\n\n
яяяяяяяяя*** This is not a reversible process ***\n
(once begun, the only restoration method may be from tape)\n\n
This script should not be used on an SFT-III server. This
script should not be used if HCSS data migration is in process.\n\n
ECG0351198
Page 22
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers22
The following steps will need to be performed after running this script:\n
- Update NetWare licensing service\n
- Apply the NetWare 5 server license(s)\n
- Configure TCP/IP\n
- Configure the mouse for Console1\n\n
Press <ESC> to abort or"
;---------------------------------------------------------------------------
;--------------------------------------------------------------------------; Dump global variables in debug mode
;--------------------------------------------------------------------------Label ProcDumpGlobals
GotoIfNEqual %{true}, %{FlagDebug}, EndProcDumpGlobals
;--------------------------------------------------------------------------; Sanity check - make sure that conflicting Flags are not selected
;--------------------------------------------------------------------------Label ProcSanityCheckFlags
Label Test1Begin
GotoIfEqual %{false}, %{FlagAutoDetectHW}, Test1End
GotoIfEqual %{false}, %{FlagMigrateSMP}, Test1End
Display 1, "Error1: conflicting options AutoDetect hardware and Migrate SMP are both enabled."
Goto EndScript
Label Test1End
Label Test2Begin
GotoIfEqual %{false}, %{FlagAutoDetectHW}, Test2End
GotoIfEqual %{false}, %{FlagConvertCPQStorageDrivers}, Test2End
Display 1, "Error2: conflicting options AutoDetect hardware and Convert storage drivers are both enabled."
Goto EndScript
Label Test2End
Label Test3Begin
GotoIfEqual %{false}, %{FlagAutoDetectHW}, Test3End
GotoIfEqual %{false}, %{FlagTransferMasterStartup}, Test3End
Display 1, "Error3: conflicting options AutoDetect hardware and Transfer Master STARTUP.NCF are both enabled."
Goto EndScript
Label Test3End
Label Test4Begin
GotoIfEqual %{false}, %{FlagTransferMasterStartup}, Test4End
GotoIfEqual %{false}, %{FlagMigrateSMP}, Test4End
Display 1, "Error4: conflicting options Transfer Master STARTUP.NCF and Migrate SMP are both enabled."
Goto EndScript
Label Test4End
Label Test5Begin
GotoIfEqual %{false}, %{FlagTransferMasterStartup}, Test5End
GotoIfEqual %{false}, %{FlagConvertCPQStorageDrivers}, Test5End
Display 1, "Error5: conflicting options Transfer Master STARTUP.NCF and Convert storage drivers are both enabled."
Goto EndScript
Label Test5End
Label Test6Begin
GotoIfEqual %{false}, %{FlagTransferNewJavaFiles}, Test6End
GotoIfEqual %{true}, %{FlagAddLongNameSpace}, Test6End
Display 1, "Error6: dependent options Transfer new Java files and Add long name space are not both enabled."
ECG0351198
Page 23
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers23
Goto EndScript
Label Test6End
Label Test7Begin
GotoIfEqual %{false}, %{FlagTransferNewConsole1Files}, Test7End
GotoIfEqual %{true}, %{FlagAddLongNameSpace}, Test7End
Display 1, "Error7: dependent options Transfer new ConsoleOne files and Add long name space are not both enabled."
Goto EndScript
Label Test7End
Label Test8Begin
GotoIfEqual %{false}, %{FlagTransferNewInstallFiles}, Test8End
GotoIfEqual %{true}, %{FlagAddLongNameSpace}, Test8End
Display 1, "Error8: dependent options Transfer new Install files and Add long name space are not both enabled."
Goto EndScript
Label Test8End
Label Test9Begin
GotoIfEqual %{false}, %{FlagTransferNewJavaFiles}, Test9End
GotoIfEqual %{true}, %{FlagTransferNewSystemFiles}, Test9End
Display 1, "Error9: dependent options Transfer new Java files and Transfer new System files are not both enabled."
Goto EndScript
Label Test9End
Label Test10Begin
GotoIfEqual %{false}, %{FlagTransferNewConsole1Files}, Test10End
GotoIfEqual %{true}, %{FlagTransferNewSystemFiles}, Test10End
Display 1, "Error10: dependent options Transfer new ConsoleOne files and Transfer new System files are not both enabled."
Goto EndScript
Label Test10End
Label Test11Begin
GotoIfEqual %{false}, %{FlagTransferNewInstallFiles}, Test11End
GotoIfEqual %{true}, %{FlagTransferNewSystemFiles}, Test11End
Display 1, "Error11: dependent options Transfer new Install files and Transfer new System files are not both enabled."
Goto EndScript
Label Test11End
Label Test12Begin
GotoIfEqual %{false}, %{FlagEnableMousePS2}, Test12End
GotoIfEqual %{false}, %{FlagEnableMouseCOM1}, Test12End
Display 1, "Error12: conflicting options Enable PS/2 Mouse and Enable COM1 Mouse are both enabled."
Goto EndScript
Label Test12End
;--------------------------------------------------------------------------; Internationalization - determine the name of the language directory
;---------------------------------------------------------------------------
Page 24
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers24
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers25
; Remove outdated patches
; NetWare 4 patches do not belong on a NetWare 5 system
;--------------------------------------------------------------------------Label ProcRemoveOldPatches
GotoIfNEqual %{true}, %{FlagRemoveOldPatches}, EndProcRemoveOldPatches
SetVar FlagRemoveOldProducts, %{true}
;--------------------------------------------------------------------------; Add name spaces
; Long filename space is required for successful unTARring of archives
;--------------------------------------------------------------------------Label ProcAddLongNameSpace
GotoIfNEqual %{true}, %{FlagAddLongNameSpace}, EndProcAddLongNameSpace
SetVar CPQICMDFile, "%{LOGFILE}"
SetVar CPQICMDCommand, "AppendText"
SetVar CPQICMDAddText, "Add LONG name space to volume SYS:"
nlmexec 1, NWUPDATE\CPQICMD
Display 2, "Adding long name space to SYS:."
GotoIfEqual %{PI_OSMajorVersion}, 5, EndProcAddLongNameSpace
GotoIfEqual %{PI_OSMinorVersion}, 11, NameSpace_411
Console 'Load OS2.Nam', 2
Console 'Add Name Space OS2 to SYS', 20
Goto EndProcAddLongNameSpace
Label NameSpace_411
Console 'Load Long.Nam', 2
Console 'Add Name Space LONG to SYS', 20
Display 2, "Adding long name space to SYS: - complete."
Label EndProcAddLongNameSpace
; Update STARTUP.NCF
; This probably doesn't help if hardware detect option is selected.
; Comments out STARTUP statements that are not needed for NetWare 5.
;--------------------------------------------------------------------------Label ProcUpdateSTARTUP
GotoIfNEqual %{true}, %{FlagUpdateSTARTUP}, EndProcUpdateSTARTUP
;--------------------------------------------------------------------------; Convert SMP support (if present) to NetWare 5 flavor
; This probably doesn't help if hardware detect option is selected.
; Disables NetWare 4 SMP support (if present). Adds NetWare 5 support
; for Compaq systems.
;--------------------------------------------------------------------------Label ProcMigrateSMP
GotoIfNEqual %{true}, %{FlagMigrateSMP}, EndProcMigrateSMP
Page 27
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers27
; The PSM should generally be loaded on all systems (even single processor)
; for NetWare 5. There are some exceptions, but adding this load statement
; will not hurt. Novell also supplies a PSM (MPS14.PSM) that can be used
; on most systems.
SetVar CPQICMDFile, "%{NWBOOT}\\STARTUP.NCF"
SetVar CPQICMDCommand, "PrependText"
SetVar CPQICMDAddText, "LOAD CPQMPK.PSM"
nlmexec 1, NWUPDATE\CPQICMD
Display 2, "Converting platform support to NetWare 5 (SMP) - complete."
Label EndProcMigrateSMP
;--------------------------------------------------------------------------; Convert DDFS to NWPA.
; Legacy Compaq storage driver LOAD statements will use current equivalents.
; This probably doesn't help if hardware detect option is selected.
; This probably doesn't help for non-Compaq storage adapters.
;--------------------------------------------------------------------------Label ProcConvertCPQStorageDrivers
GotoIfNEqual %{true}, %{FlagConvertCPQStorageDrivers}, EndProcConvertCPQStorageDrivers
;--------------------------------------------------------------------------; Configure the server to run hardware detection algorithm after reboot
; May require user intervention to complete.
;--------------------------------------------------------------------------Label ProcAutoDetectHardware
GotoIfNEqual %{true}, %{FlagAutoDetectHW}, EndProcAutoDetectHardware
GotoIfEqual %{PI_OSMajorVersion}, 5, EndProcAutoDetectHardware
;--------------------------------------------------------------------------; Transfer a master STARTUP.NCF to the target server
; This probably doesn't help if hardware detect option is selected.
; For standard configurations, a master NetWare 5 STARTUP.NCF file can be
; copied from the script directory to the target server.
;--------------------------------------------------------------------------Label ProcXferMasterStartup
GotoIfNEqual %{true}, %{FlagTransferMasterStartup}, EndProcXferMasterStartup
; An alternative would to be to generate one "on the fly" using Append...
; File is transferred from the same directory as the script
CopyFile 0,0,1,1,0,SRCSCRIPT,STARTUP.NCF,'','',NWBOOT,'','',''
;--------------------------------------------------------------------------; Clean up obsoleted files in OS SYS:SYSTEM directory
;--------------------------------------------------------------------------Label ProcEraseOldSystemFiles
GotoIfNEqual %{true}, %{FlagEraseOldSystemFiles}, EndProcEraseOldSystemFiles
SetVar CPQICMDFile, "%{LOGFILE}"
SetVar CPQICMDCommand, "AppendText"
SetVar CPQICMDAddText, "Erase old OS system files"
nlmexec 1, NWUPDATE\CPQICMD
Display 2, "Removing old system files."
; Remove old 4.x and 5.x files
;--------------------------------------------------------------------------; Transfer new boot files to the boot (C:\NWSERVER) directory
;--------------------------------------------------------------------------Label ProcTransferNewBootFiles
GotoIfNEqual %{true}, %{FlagTransferNewBootFiles}, EndProcTransferNewBootFiles
SetVar CPQICMDFile, "%{LOGFILE}"
SetVar CPQICMDCommand, "AppendText"
SetVar CPQICMDAddText, "New OS boot files" nlmexec 1, NWUPDATE\CPQICMD
Display 2, "Transferring new OS boot files."
CopyFile 0,1,1,2,0,SRCNW5, startup,'','',NWBOOT,'','',''
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers34
Copying Files to SYSTEM, PUBLIC, and LOGIN Directories
;--------------------------------------------------------------------------; Transfer new system files to the SYS:SYSTEM directory
;--------------------------------------------------------------------------Label ProcTransferNewSystemFiles
GotoIfNEqual %{true}, %{FlagTransferNewSystemFiles}, EndProcTransferNewSystemFiles
SetVar CPQICMDFile, "%{LOGFILE}"
SetVar CPQICMDCommand, "AppendText"
SetVar CPQICMDAddText, "New OS system files" nlmexec 1, NWUPDATE\CPQICMD
; DOS utility language support
CopyFile 0,1,0,2,0,SRCNW5, sys\public\nls,'','',NWSYS,public\nls,'',''
CopyFile 0,1,1,2,0,SRCNW5, 'sys\\public\\nls\\%{NWLANGNAME}','','',NWSYS,'public\\nls\\%{NWLANGNAME}','',''
Display 2, "Updating Windows client utilities."
; Windows utilities and language support
; Windows 95 utilities and language support
CopyFile 0,1,1,2,0,SRCNW5, sys\public\win95,'','',NWSYS,public\win95,'',''
CopyFile 0,1,0,2,0,SRCNW5, sys\public\win95\nls,'','',NWSYS,public\win95\nls,'',''
CopyFile 0,1,1,2,0,SRCNW5, 'sys\\public\\win95\\nls\\%{NWLANGNAME}','','',NWSYS,'public\\win95\\nls\\%{NWLANGNAME}','',''
; Windows NT utilities and language support
CopyFile 0,1,1,2,0,SRCNW5, sys\public\winnt,'','',NWSYS,public\winnt,'',''
CopyFile 0,1,0,2,0,SRCNW5, sys\public\winnt\nls,'','',NWSYS,public\winnt\nls,'',''
CopyFile 0,1,1,2,0,SRCNW5, 'sys\\public\\winnt\\nls\\%{NWLANGNAME}','','',NWSYS,'public\\winnt\\nls\\%{NWLANGNAME}','',''
;--------------------------------------------------------------------------; Transfer new script files to the boot (C:\NWSERVER) directory
;--------------------------------------------------------------------------Label ProcTransferNewScriptFiles
GotoIfNEqual %{true}, %{FlagTransferNewScriptFiles}, EndProcTransferNewScriptFiles
;--------------------------------------------------------------------------; Transfer and expand new Java files
;--------------------------------------------------------------------------Label ProcTransferNewJavaFiles
GotoIfNEqual %{true}, %{FlagTransferNewJavaFiles}, EndProcTransferNewJavaFiles
Display 2, "Java for NetWare directories and files are being extracted."
NLMexec 1, 'SYS:SYSTEM\\TAR xvfD java.tar'
EraseFile 0,NWSYS, java.tar,'',''
CopyFile 0,0,0,1,0,NWSYS,temp\sys\etc\java.cfg,'','',NWSYS,'etc','',''
CopyFile 0,0,1,0,0,SRCNW5,sys\java_ins\njcl.tar,'','',NWSYS,'','',''
Display 2, "Java Class Libraries for NetWare directories and files are being extracted."
NLMexec 1, 'SYS:SYSTEM\\TAR xvfD njcl.tar'
EraseFile 0,NWSYS, njcl.tar,'',''
CopyFile 0,0,1,0,0,SRCNW5,sys\java_ins\beans.tar,'','',NWSYS,'','',''
Display 2, "Java Beans for NetWare directories and files are being extracted."
NLMexec 1, 'SYS:SYSTEM\\TAR xvfD beans.tar'
EraseFile 0,NWSYS, beans.tar,'',''
CopyFile 0,0,1,0,0,SRCNW5,sys\java_ins\perl.tar,'','',NWSYS,'','',''
Display 2, "Perl 5 for NetWare directories and files are being extracted."
NLMexec 1, 'SYS:SYSTEM\\TAR xvfD perl.tar'
EraseFile 0,NWSYS, perl.tar,'',''
;--------------------------------------------------------------------------; Transfer and expand new Console1 files
;--------------------------------------------------------------------------Label ProcTransferNewConsole1Files
GotoIfNEqual %{true}, %{FlagTransferNewConsole1Files}, EndProcTransferNewConsole1Files
Display 2, "Console One Directories and Files are being extracted."
NLMexec 1, 'SYS:SYSTEM\\TAR xvfD console1.tar'
EraseFile 0, NWSYS, console1.tar,'',''
CopyFile 0,0,1,0, 0,SRCNW5,sys\java_ins\mach1.tar,'','',NWSYS,'','',''
Display 2, "Mach One Directories and Files are being extracted."
NLMexec 1, 'SYS:SYSTEM\\TAR xvfD mach1.tar'
Page 37
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers37
Display 2, "Server Top Directories and Files are being extracted."
NLMexec 1, 'SYS:SYSTEM\\TAR xvfD servtop.tar'
EraseFile 0, NWSYS, servtop.tar,'',''
; backup the current NCF
CopyFile 0,2,0,0,0,NWSYS,system\ldragcon.ncf,'','',NWSYS,system\ldragcon.sav,'',''
CopyFile 0,0,1,0, 0,SRCNW5,sys\java_ins\rconj.tar,'','',NWSYS,'','',''
Display 2, "Java Rconsole directories and files are being extracted."
NLMexec 1,'SYS:SYSTEM\\TAR xvfD rconj.tar'
EraseFile 0, NWSYS, rconj.tar,'',''
; restore the current NCF
CopyFile 0,2,0,0,0,NWSYS,system\ldragcon.sav,'','',NWSYS,system\ldragcon.ncf,'',''
;--------------------------------------------------------------------------; Transfer and expand new Install files
;--------------------------------------------------------------------------Label ProcTransferNewInstallFiles
GotoIfNEqual %{true}, %{FlagTransferNewInstallFiles}, EndProcTransferNewInstallFiles
Display 2, "NetWare Server Install directories and files are being extracted."
NLMexec 1,'SYS:SYSTEM\\TAR xvfD ni.tar'
EraseFile 0, NWSYS, ni.tar,'',''
CopyFile 0,0,1,0, 0,SRCNW5,install\tars\products.tar,'','',NWSYS,'','',''
Display 2, "Other Products directories and files are being extracted."
NLMexec 1,'SYS:SYSTEM\\TAR xvfD products.tar'
EraseFile 0, NWSYS, products.tar,'',''
; Transfer and expand NICI Signed Loader cryptography files
ECG0351198
Page 38
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers38
; Cryptography needs to be set up (key and license) to take effect
;--------------------------------------------------------------------------Label ProcTransferCryptographyFiles
GotoIfNEqual %{true}, %{FlagTransferCryptographyFiles}, EndProcTransferCryptographyFiles
;--------------------------------------------------------------------------; Transfer Compaq storage drivers (required storage adapter drivers) to the
; server boot directory.
; This is kind of a hack, but allows the OS to boot on Compaq hardware
; without requiring hardware detection, seamlessly. On systems or options not
; supported by the NetWare 5 CD drivers, new drivers could be copied here.
; Regular hardware detection will copy necessary files from the DRIVERS
; directory to the NWSERVER directory.
;--------------------------------------------------------------------------Label ProcMoveCompaqStorageDrivers
ECG0351198
Page 39
Using NetWare Installation Scripts to Upgrade from NetWare 4 to NetWare 5 on Compaq Servers39
Display 2, "Preparing for NDS update at next boot."
; The NDS update program, NDSDIBUP.NLM must be co-located
; with the script on the master server
CopyToServer SYSTEM, NDSDIBUP.NLM, '', ''
Display 2, "Modifying AUTOEXEC.NCF for NDS update."
PI_EditNCF_ADDLINE '; The following lines were added by the migration script'
PI_EditNCF_ADDLINE '; and can be removed after rebooting the server.'
PI_EditNCF_ADDLINE '; NDSDIBUP is used to update the NDS schema.'
PI_EditNCF_ADDLINE 'LOAD NDSDIBUP.NLM'
PI_EditNCF_ADDLINE 'LOAD NWCONFIG.NLM b=%{NWBOOT}\\MIGDONE.ICS e=%{NWBOOT}\\err.log d=%{NWBOOT}'
PI_EditNCF_ADDLINE '; End of modifications made by the migration script.'
PI_EditNCF_ADDLINE ' ' ;Add blank Line
PI_EditNCF NWSYSTEM, 'autoexec.ncf', '.BAK', ccode
SetVar CPQICMDFile, "%{LOGFILE}"
SetVar CPQICMDCommand, "AppendText"
SetVar CPQICMDAddText, "IPX will load when OS is booted"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDAddText, "IPX router network management will load when OS is booted"
nlmexec 1, NWUPDATE\CPQICMD
; ConsoleOne support pulled because mouse requires configuration.
; SetVar CPQICMDAddText, "Console 1 will load when OS is booted"
; nlmexec 1, NWUPDATE\CPQICMD
; Perform updates on actual AUTOEXEC
SetVar CPQICMDFile, "%{NWSYSTEM}\\AUTOEXEC.NCF"
SetVar CPQICMDCommand, "AppendText"
SetVar CPQICMDAddText, "\n"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDAddText, "\; The following lines were added by the migration script:"
nlmexec 1, NWUPDATE\CPQICMD
Display 2, "Preparing for IPX load at next boot."
SetVar CPQICMDAddText, "LOAD IPXRTR"
nlmexec 1, NWUPDATE\CPQICMD
Display 2, "Preparing for IPX router network management load at next boot."
SetVar CPQICMDAddText, "LOAD IPXRTRNM"
nlmexec 1, NWUPDATE\CPQICMD
; now add statements that normally are present on NW5 installations
Display 2, "Accommodating new search paths."
SetVar CPQICMDAddText, "SYS\:\\SYSTEM\\NMA\\NMA5.NCF"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDAddText, "\#RCONAG6.NLM is required by Console Manager in ConsoleOne and by RConsoleJ"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDAddText, "\#LOAD SPXS"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDAddText, "\#LOAD RCONAG6.NLM"
nlmexec 1, NWUPDATE\CPQICMD
; ConsoleOne support pulled because mouse requires configuration.
; Display 2, "Preparing for ConsoleOne load at next boot."
; SetVar CPQICMDAddText, "C1START"
; nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDAddText, "\; End of modifications made by the migration script."
nlmexec 1, NWUPDATE\CPQICMD
;--------------------------------------------------------------------------; Disable Third Party Applications
; They will be manually enabled after migration is complete
; * Sample
;--------------------------------------------------------------------------Label ProcDisableThirdPartyApps
GotoIfNEqual %{true}, %{FlagDisableThirdPartyApps}, EndProcDisableThirdPartyApps
Display 2, "Disabling any Third Party Applications."
; Note updates in migration log file
; Perform updates on AUTOEXEC
; The file being processed
SetVar CPQICMDFile, "%{NWSYSTEM}\\AUTOEXEC.NCF"
; The command being processed
SetVar CPQICMDCommand, "PrependLineWithText"
; The text to insert in the process
SetVar CPQICMDAddText, "\; REM-Enable Later: "
; The text to insert before in the process (whitespace ignored)
SetVar CPQICMDSearchText, "LOAD SAMPLE.NLM "
; Launch the process
nlmexec 1, NWUPDATE\CPQICMD
Display 2, "Disabling any Third Party Applications - complete."
Label EndProcDisableThirdPartyApps
SetVar FlagEnableMouseCOM1, %{false}
;--------------------------------------------------------------------------; Enable Mouse support through the PS/2 mouse port
;--------------------------------------------------------------------------Label ProcEnableMousePS2
GotoIfNEqual %{true}, %{FlagEnableMousePS2}, EndProcEnableMousePS2
;--------------------------------------------------------------------------; Enable Mouse support through the COM1 port
;--------------------------------------------------------------------------Label ProcEnableMouseCOM1
GotoIfNEqual %{true}, %{FlagEnableMouseCOM1}, EndProcEnableMouseCOM1
; MOUSE.CFG
; Assures that "-mp Microsoft -md COM1" is in SYS:JAVA\NWGFX\MOUSE.CFG
SetVar CPQICMDFile, "%{NWSYS}\\JAVA\\NWGFX\\MOUSE.CFG"
SetVar CPQICMDCommand, "PrependLineWithText"
SetVar CPQICMDAddText, "\# "
SetVar CPQICMDSearchText, "-mp "
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDCommand, "AppendText"
SetVar CPQICMDAddText, "-mp Microsoft -md COM1"
nlmexec 1, NWUPDATE\CPQICMD
; PRE_SRV.NCF
; Assures that "LOAD AIO" is in SYS:JAVA\NWGFX\PRE_SRV.NCF
; Assures that "AIOCOMX port=3F8 int=4 name=COM1" is in SYS:JAVA\NWGFX\PRE_SRV.NCF
SetVar CPQICMDFile, "%{NWSYS}\\JAVA\\NWGFX\\PRE_SRV.NCF"
SetVar CPQICMDCommand, "PrependLineWithText"
SetVar CPQICMDAddText, "\# "
SetVar CPQICMDSearchText, "AIOCOMX"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDSearchText, "LOAD AIOCOMX"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDSearchText, "AIOPS2"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDSearchText, "LOAD AIOPS2"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDSearchText, "AIO"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDSearchText, "LOAD AIO"
nlmexec 1, NWUPDATE\CPQICMD
SetVar CPQICMDCommand, "AppendText"
SetVar CPQICMDAddText, "AIO"
nlmexec 1, NWUPDATE\CPQICMD
; The following command contains COM port parameters which can be changed
; a similar procedure would be used if a serial mouse were on COM2
SetVar CPQICMDAddText, "AIOCOMX port=3F8 int=4 name=COM1"
nlmexec 1, NWUPDATE\CPQICMD
Display 2, "Enabling COM1 Mouse support - complete."
Label EndProcEnableMouseCOM1