More About Automating the NetWare 5 Installation with a Response File
Articles and Tips: article
Software Engineering Manager
Novell, Inc.
01 Feb 1999
Learn how to create a response file that allows a fully automated, unattended installation of NetWare 5 as well as additional products and services.
- Introduction
- Performing a Fully Automated Installation
- Customizing the Installation Using Install Scripts
- Performing a Factory Install
Introduction
"Automating the NetWare 5 Installation with a Response File" (published in the December 1998 issue of Novell AppNotes) introduced the use of a Response File to make installing the NetWare 5 operating system software easier and more flexible. The process involved specifying various installation values and parameters in a Windows INI-like Response File, which can then be given as input when the installation program is started. As the installation progresses, the default installation values are replaced with the values specified in the Response File. Depending on how much information is included in the Response File, users can bypass entire sections of the program or automate the entire server installation process.
This follow-up AppNote presents additional information about automating the NetWare 5 installation by using a Response File. In particular, it covers:
How to perform a fully automated server installation. In addition to the Response File sections and keys listed in the previous AppNote, there are some other keys that are required to completely automate the installation of NetWare 5. You can also automate the installation of additional products and services such as LDAP Services, Novell DNS/DHCP Services, and so on.
How to customize the installation using Install Scripts. NetWare 4 supported the use of Install Scripts (formerly known as CDWare) to customize the installation process by running batch file-like scripts at certain points in the program. NetWare 5 supports a similar function through the NWConfig utility and the NetWare 5 installation system.
How to perform a partial "factory install" that can be completed later by the customer. This new installation feature was developed to enable an Original Equipment Manufacturer (OEM) to pre-load the NetWare"5 operating system prior to shipping the server hardware. It is also useful for resellers and enterprise customers who have a configuration center where the network operating system is installed on a server prior to moving the machine to its permanent location.
This information is intended as a supplement to "Automating the NetWare 5 Installation with a Response File." It is assumed that the reader has read and understood that AppNote prior to reading this one.
Performing a Fully Automated Installation
My December 1998 AppNote on the Response File explained the Windows INI-style headings, keys, and values that correspond to the NetWare 5 installation screens. This AppNote expands on that information by describing additional parameters that must be present to completely automate an installation or upgrade.
The syntax and values for the supplementary NetWare 5 installation sections and their associated keys are specified below. As in the previous AppNote, section names and key names are in bold, and listed for each key are the default value, possible values, and whether the key is required for the NetWare 5 installation to run without any user intervention. Also included with each key description are an example and a short description of the key's purpose.
Keep in mind that for a fully automated installation to work, these sections must appear somewhere in the Response File in addition to all of the other required keys listed in the previous AppNote.
[Initialization] Section
|
SummaryPrompt= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
Yes |
|
|
Example |
SummaryPrompt = True |
|
|
Purpose |
Controls whether the installation Summary screen is displayed. |
[Novell:NOVELL_ROOT:1.0.0] Section
|
closeScreen= <string< |
||
|
|
Default |
None |
|
|
Values |
SilentCloseScreen |
|
|
Required |
Yes |
|
|
Example |
closeScreen = SilentCloseScreen |
|
|
Purpose |
When this parameter is set, the final installation screen is not shown. |
|
Reboot = <string< |
||
|
|
Default |
None |
|
|
Values |
True or False |
|
|
Required |
Yes |
|
|
Example |
Reboot = False |
|
|
Purpose |
Controls whether the server is restarted after the final screen of the installation is closed. |
Automating the Installation of Additional Products and Services
As part of the overall NetWare 5 installation, additional products and services can also be auto- installed. This is done by including a [Selected Products] section in the Response File. Since this section of the Response File is not as easy to configure as the other sections are, it is recommended that you first do a manual installation, selecting the products you want to have installed on the server. Then you can modify the resulting Response File for use as input to future NetWare 5 installations. (For more information, see the section on "How to Create a Response File" in the previous AppNote.)
If the [Selected Products] section is added to the input Response File, the following lines must be present under the section heading:
Novell:NetWare5:1.0.0=Novell:NetWare5OS:5.0.0,Novell:Products:1.0.0,Novell\ :NWUpdateGroup:1.0.0 Novell:NetWare5OS:5.0.0=Novell:DiskCarver:1.0.0,Novell:Protocols:1.0.0,\ Novell:DS_Install:1.0.0, Novell:LicensePrompt:1.0.0,Novell:NW:1.0.0,Novell:NDPS Server Files:1.0.0 Novell:NW:1.0.0=Novell:Startup:1.0.0,Novell:SYS:1.0.0,Novell:DriverFiles:1.0.0 Novell:Startup:1.0.0=Novell:StartupDirectory:1.0.0 Novell:SYS:1.0.0=Novell:SYSDirectory:1.0.0,Novell:ETCDirectory:1.0.0,Novell:\ PROFINST_NODE:1.0.0 Novell:DriverFiles:1.0.0=Novell:LANFiles:1.0.0,Novell:SBDFiles:1.0.0 Novell:NDPS Server Files:1.0.0=Novell:NDPS System:1.0.0,Novell:NDPS Public:1.0.0 Novell:Products:1.0.0=Novell:NICIInstall:1.0.0 Novell:NICIInstall:1.0.0=Novell:NICIModule:1.0.0 Novell:NWUpdateGroup:1.0.0=Novell:NWUpdate:1.0.0
You can add more lines according to your individual needs, but these represent the minimum information that must be included in the [Selected Products] section.
|
[Selected Products] Section |
||
|
Prompt= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
Yes |
|
|
Example |
Prompt = True |
|
|
Purpose |
Controls whether the Additional Products and Services screen is displayed. |
|
Novell:Products:1.0.0= <string(s) separated by commas< |
||
|
|
Default |
Novell:NICIInstall:1.0.0 (Note: This NICI install string must be included.) |
|
|
Values |
Novell:NDPS:2.0.0 |
|
|
Novell:IpLdapService:3.0.0 |
|
|
|
Novell:IpCatalogService:1.0.0 |
|
|
|
Novell:IpWanmanService:1.0.0 |
|
|
|
Novell:SecuritySASInstall:1.0.0 |
|
|
|
Novell:PKIInstall:1.0.0 |
|
|
|
Novell:NICIInstall:1.0.0 |
|
|
|
Novell:RAS:4.1.0 |
|
|
|
Novell:SMS:1.0.0 |
|
|
|
Novell:DNS_DHCP:1.0.0 |
|
|
|
Required |
Yes |
|
|
Example |
Novell:Products:1.0.0 = Novell:NICIInstall:1.0.0,Novell:NDPS:2.0.0 |
|
|
Purpose |
Specifies the additional products and services to be installed on the server. |
To install multiple products on a server, ensure that the Novell:Products:1.0.0 key has multiple values, separated by commas as shown in the example above.
In addition to identifying the product in the Novell:Products:1.0.0 key, each product has its own keys and values for the [selected nodes] section. The keys and values for each product are listed below.
Novell Distributed Print Services (NDPS) Novell:NDPS:2.0.0=Novell:NDPS Server Files:1.0.0,Novell:NDPS Resource Files:1.0.0 Novell:NDPS Resource Files:1.0.0=Novell:NDPS Banner:1.0.0,Novell:NDPS Font:1.0.0, Novell:NDPS Prndef:1.0.0,Novell:NDPS Prndrv:1.0.0 Novell:NDPS Prndrv:1.0.0=Novell:NDPS Prndrv W31:1.0.0,Novell:NDPS Prndrv W95:1.0.0, Novell:NDPS Prndrv NT4:1.0.0 LDAP Services Novell:SecuritySASModule:1.0.0=Novell:SASFiles:1.0.0 Novell:PKIModule:1.0.0=Novell:PKIFiles:1.0.0 NDS Catalog Services Novell:IpCatalogService:1.0.0=Novell:DfgCatalogService:1.0.0 WAN Traffic Manager Services Novell:IpWanmanService:1.0.0=Novell:DfgWanmanService:1.0.0 Secure Authentication Services Novell:RAS:4.1.0=Novell:RAS Server Files:1.0.0,Novell:SVCDEF_NODE:1.0.0,Novell:SupportedOS:1.0.0,Novell:\ UpgradeFrom:1.0.0 Novell:RAS Server Files:1.0.0=Novell:RAS System Connect:1.0.0,Novell:RAS System Connect Scripts:1.0.0,Novell:RAS Public:1.0.0 Novell PKI Services Novell:PKIInstall:1.0.0=Novell:PKIModule:1.0.0,Novell:NICIModule:1.0.0 Novell:PKIModule:1.0.0=Novell:PKIFiles:1.0.0 Novell Internet Access Server Novell:RAS:4.1.0=Novell:RAS Server Files:1.0.0,Novell:SVCDEF_NODE:1.0.0,Novell:SupportedOS:1.0.0,Novell:\ UpgradeFrom:1.0.0 Novell:RAS Server Files:1.0.0=Novell:RAS System Connect:1.0.0,Novell:RAS System Connect Scripts:1.0.0,Novell:RAS Public:1.0.0 Storage Management Services Novell:SMS:1.0.0=Novell:SMSFiles:1.0.0 Novell:SMSFiles:1.0.0=Novell:SMSSystemFiles:1.0.0,Novell:SMSPublicFiles:1.0.0 Novell DNS/DHCP Services No additional keys and values are used for the installation of this service
Again, it is recommended that you reuse a Response File from a previous installation rather than attempting to manually type these keys and values into the file. If the values are not entered exactly as shown, the NetWare installation program will fail abruptly with no information to help you troubleshoot the problem.
Additional Products and Services Screens
Two of the additional services available with NetWare 5 have data input screens for their configuration. These products are LDAP Services and Novell DNS/DHCP Services. These services have Response File sections associated with them that must be included in addition to the keys and values listed above. Be sure to use the proper case (upper or lower) when entering these keys and values.
|
[LDAP] Section |
||
|
prompt= <string< |
||
|
|
Default |
(none) |
|
|
Values |
true or false |
|
|
Required |
Yes |
|
|
Example |
prompt = false |
|
|
Purpose |
Controls whether the LDAP configuration screen is displayed. |
|
adminID= <string< |
||
|
|
Default |
(none) |
|
|
Values |
(NDS distinguished name) |
|
|
Required |
Yes |
|
|
Example |
adminID = .CN=admin.O=install |
|
|
Purpose |
Identifies the Admin name and NDS context. This should correspond with the Admin Login Name and Admin Context identified in the NWI:NDS section of the Response File. Note the case of the characters in the string. |
|
installCatalog= <string< |
||
|
|
Default |
(none) |
|
|
Values |
true or false |
|
|
Required |
Yes |
|
|
Example |
installCatalog = false |
|
|
Purpose |
Controls whether an LDAP catalog is installed. Corresponds to the question: Enable use of LDAP catalog? |
|
useCatalogOnly= <string< |
||
|
|
Default |
(none) |
|
|
Values |
true or false |
|
|
Required |
Yes |
|
|
Example |
useCatalogOnly = false |
|
|
Purpose |
Controls whether the LDAP catalog is used exclusively for searching. Corresponds to the LDAP screen prompt: Catalog Usage for Searching. |
[Novell:DNS_DHCP:1.0.0] Section
|
Prompt= <string< |
||
|
|
Default |
(none) |
|
|
Values |
true or false |
|
|
Required |
Yes |
|
|
Example |
Prompt = false |
|
|
Purpose |
Controls whether the DNS/DHCP configuration screen is displayed. |
|
TreeName= <string< |
||
|
|
Default |
(none) |
|
|
Values |
(text) |
|
|
Required |
Yes |
|
|
Example |
TreeName = Novell |
|
|
Purpose |
Specifies the name of the NDS tree in which DNS/DHCP Services will be installed. |
|
UserName= <string< |
||
|
|
Default |
(none) |
|
|
Values |
(NDS distinguished name) |
|
|
Required |
Yes |
|
|
Example |
UserName = .CN=admin.O=install |
|
|
Purpose |
Identifies the Admin name and NDS context. This should correspond with the Admin Login Name and Admin Context identified in the NWI:NDS section of the Response File. Note the case of the characters in the string. |
|
ExtendDNIPSchema= <string< |
||
|
|
Default |
(none) |
|
|
Values |
true or false |
|
|
Required |
Yes |
|
|
Example |
ExtendDNIPSchema = true |
|
|
Purpose |
Controls whether the schema is extended for DNS/DHCP Services. Note that this should be set to true. |
|
LocatorNDSContext= <string< |
||
|
|
Default |
(none) |
|
|
Values |
(NDS distinguished name) |
|
|
Required |
Yes |
|
|
Example |
LocatorNDSContext = O=install |
|
|
Purpose |
Identifies the NDS context into which the Locator Object is to be installed. |
|
GroupNDSContext= <string< |
||
|
|
Default |
(none) |
|
|
Values |
(NDS distinguished name) |
|
|
Required |
Yes |
|
|
Example |
GroupNDSContext = O=install |
|
|
Purpose |
Identifies the NDS context into which the Group Object is to be installed. |
|
RootSrvrNDSContext= <string< |
||
|
|
Default |
(none) |
|
|
Values |
(NDS distinguished name) |
|
|
Required |
Yes |
|
|
Example |
RootSrvrNDSContext = O=install |
|
|
Purpose |
Identifies the NDS context into which the RootSrvr Zone is to be installed. |
In addition to the DNS/DHCP keys identified above, there must also be a line in the [Settings] section with the entry:
Novell:DNS_DHCP:1.0.0=
CD-ROM Boot and the Response File
In the previous AppNote, two options were given for passing a Response File into the NetWare 5 installation: (1) on the command line using the /RF switch, or (2) from the Install Options screen. If the install is begun by booting directly to the NetWare 5 CD-ROM, there is no opportunity to pass in the Response File automatically. However, there is a solution. When the NetWare 5 CD is booted, the startup utility checks for a RESPONSE.TXT file in the C:\NWUPDATE directory. If such a file exists, the installation program will bypass the DOS partitioning utility and use RESPONSE.TXT as the input Response File.
Customizing the Installation Using Install Scripts
As mentioned previously, some NetWare 4 customers found Install Scripts useful in customizing their installation process. In NetWare 5, install scripts are supported by the NWConfig utility and the NetWare 5 installation system.
There are two places in the NetWare 5 installation where install scripts can be executed. The first place is at the end of the preliminary file copy (just prior to the launching of the graphical portion of the install). An install script executed here can be used for copying files from the DOS partition to the SYS volume.
The second install script can be run at the end of the NetWare 5 installation. It is called right after the user answers "OK" or "No" on the closing screen and before the install cleanup process. This script is useful for customers who want to manage files and launch NLMs (for example, those that install other products) as part of the NetWare 5 installation. The script must be placed on volume SYS prior to its execution. You can do this either by having the script run at the end of the preliminary file copy or by placing the script in the appropriate directory of a CD-ROM image on a network drive.
The following Response File syntax is used to run install scripts during the NetWare 5 installation.
|
[NWI:Install Script] Section |
||
|
Script Location= <string< |
||
|
|
Default |
None |
|
|
Values |
(existing DOS path up to 255 characters) |
|
|
Required |
No |
|
|
Example |
Script Location = C:\NWUPDATE\PRECOPY.IC? |
|
|
Purpose |
Identifies the filename and path of an Install Script that will be executed at the end of the preliminary file copy (prior to the launching of the graphical portion of the installation program). Usage of the ? wildcard in the extension of the filename will suppress an error if the specified file does not exist. |
|
Close Script= <string< |
||
|
|
Default |
None |
|
|
Values |
(existing DOS path up to 255 characters) |
|
|
Required |
No |
|
|
Example |
Close Script = SYS:\OTHER.ICS |
|
|
Purpose |
Identifies the filename and path of an Install Script that will be executed when the final screen of the NetWare 5 server installation is closed. This script is executed just prior to some housekeeping that is done by the Close Screen routine. |
Performing a Factory Install
The so-called "Factory Install" reduces for the customer the complexity and time spent on the installation. Much of the hardware configuration and file copying is done at the "factory" so that the customer need only use the graphical portion of the NetWare 5 installation to complete their configuration on-site. Since the network operating system files were pre-copied to the server, installation time for the customer is reduced to a few minutes.
The Factory Install splits the installation of NetWare into two phases. Phase 1 performs the disk detection, disk partitioning, SYS volume creation, and file copy portions of the install. This phase is meant to be performed in a factory or configuration center.
Phase 2 is focused on user configuration. It includes the setting of the server name, protocol binding, creation of volumes other than SYS, and configuration of time zone, NDS, licensing, and other products. This phase is meant to be performed by the customer at the server's permanent location.
Once Phase 1 is completed, the machine should be rebooted or powered off. When the machine is powered on and the server is started, the AUTOEXEC.NCF will launch Java for Phase 2 of the installation.
A Factory Install is implemented with the Response File sections below. The Preinstall key of the [NWI:Factory] section is the primary key that directs the NetWare 5 Installation to perform a factory install. The Precopy key of the other sections specifies whether the file group should be recopied during the final file copy routine of the NetWare 5 Installation. If Precopy=True, the files will be verified, but not copied; however, the Installation will appear as if it is copying the files because you will see each file name displayed in the copy status box.
Note: The NetWare 5 CD-ROM must be inserted in Phase 2 of the Factory Install in order to perform this file verification.
This Factory Install discussion assumes that all other required keys for an automated install are also included in the Response File.
|
[NWI:Factory] Section |
||
|
Preinstall= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
Yes |
|
|
Example |
Preinstall = True |
|
|
Purpose |
Controls whether the Factory Install option of the NetWare 5 installation is invoked. If Presinstall = True, the files are not copied again the the final file copy routine. |
[Novell:SYSDirectory:1.0.0] Section
|
Precopy= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
No |
|
|
Example |
Precopy = True |
|
|
Purpose |
Controls whether the files destined for volume SYS are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. |
[Novell:ETCDirectory:1.0.0] Section
|
Precopy= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
No |
|
|
Example |
Precopy = True |
|
|
Purpose |
Controls whether the files destined for the SYS:\ETC directory are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. |
[Novell:LANFiles:1.0.0] Section
|
Precopy= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
No |
|
|
Example |
Precopy = True |
|
|
Purpose |
Controls whether the LAN files destined for the C:\<Startup Directory<\DRIVERS directory are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. |
[Novell:StorageFiles:1.0.0] Section
|
Precopy= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
No |
|
|
Example |
Precopy = True |
|
|
Purpose |
Controls whether the HAM and CDM files destined for the C:\<Startup Directory<\DRIVERS directory are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. |
[Novell:PSMFiles:1.0.0] Section
|
Precopy= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
No |
|
|
Example |
Precopy = True |
|
|
Purpose |
Controls whether the PSM files destined for the C:\<Startup Directory<\DRIVERS directory are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. |
[Novell:StartupDirectory:1.0.0] Section
|
Precopy= <string< |
||
|
|
Default |
True |
|
|
Values |
True or False |
|
|
Required |
No |
|
|
Example |
Precopy = True |
|
|
Purpose |
Controls whether the files destined for the C:\<Startup Directory< directory are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. |
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.