Automating the NetWare 5 Installation with a Response File

Articles and Tips: article

CURT KANAHELE
Software Engineering Manager
Novell, Inc.

01 Dec 1998

Installers and resellers are always looking for ways to streamline the server installation process. Here's a little-known feature to automate the whole thing.

Introduction
How to Create a Response File
How to Select a Response File
Response File Syntax
NetWare 5 Response File Sections and Keys

Introduction

Installing the NetWare 5 operating system software can be easier and more flexible when you use a Response File. In conjunction with the new graphical server installation program, the Response File allows you to set and display specific defaults, bypass entire sections, or automate the entire server installation process.

If a Response File is given as input, the NetWare 5 server installation reads the installation parameters directly from the Response File. During the server installation, the default installation values are replaced with the values specified in the Response File. The installation program simply accepts the values as they appear and continues to the next installation screen. If desired, the entire sequence of installation screens may be skipped because the installation program gets all the required information from the Response File.

This AppNote tells how to create, modify, and select a Response File when installing a NetWare 5 server. It describes the syntax for the various section and key names, and lists all of the possible keys that can be included in the Response File.

The Response File feature is useful to a variety of customers and vendors. Novell customers who have established server hardware standards in their enterprise can use the Response File to rapidly deploy multiple NetWare 5 servers. Customers may also have need to preconfigure some of the NetWare 5 installation, but leave other parameters to the local administrator. Resellers and OEMs will find the Response File useful for pre-installing NetWare 5 prior to shipping a server to their customers. A follow-up AppNote will cover these specific uses of the Response File.

How to Create a Response File

A Response File can be created from scratch or edited from a previous server installation. Care must be taken when using a Response File from a previous installation because it may contain advanced configuration options that are not wanted for a new installation.

Creating a New Response File

Use an ASCII text editor such as EDIT to input parameters as described in the Syntax section of this document.

Using a Response File from a Previous Server Installation

A Response File can be generated from a server installation or upgrade and used as input for additional server installations or upgrades. Using the Response File from another server installation works best when both servers have the same hardware configuration.

To use the Response File generated in a server installation, do the following:

Perform the first server installation. Reboot the server by answering "Yes" on the closing screen of the installation.
Log in to the new server after it has been rebooted.
Copy the RESPONSE.NI file from the SYS:NI\DATA directory to a diskette and/or to the new server.
Modify the file by adjusting the parameters as needed and removing unwanted sections.

How to Select a Response File

A Response File can be given as input in one of two ways: (1) identified during the server installation, or (2) via the command line.

To identify a Response File during the server installation, do the following:

Copy the Response File to a diskette, hard disk, or network directory accessible by the PC on which you are installing NetWare 5.
Start the server installation by typing INSTALL <Enter<.
On the Install Options screen (the first screen after language selection), press <F3< for the Response File window. (Note that this use of the <F3< key can be disabled by using a special setting in the Response File.)
Type in the full DOS path and filename for the Response File.

An example of specifying a Response File on diskette is shown in Figure 1.

Figure 1: You can input the name of the Response File at this point in the server installation program.

To input a Response File via the command line, do the following:

Copy the Response File to a diskette, hard disk, or network directory accessible by the PC on which you are installing NetWare 5.
Start the server installation from CD-ROM, hard disk, or network directory by typing:

INSTALL /RF=<Response File DOS path\filename<

For example, if you are installing NetWare 5 from the CD-ROM and the Response File is on a diskette, you would type:

D:\INSTALL /RF=A:\RESPONSE.TXT

Response File Syntax

The Response File is a Windows INI-type file. Data items are identified as keys. Keys have associated values that you would specify for data fields (for example, key = value). These keys are grouped in sections. For the NetWare 5 installation program, each data input screen has one or more sections associated with it. Section names of the NetWare 5 installation generally correspond to the function of the screens.

Section and key names are case sensitive. Values associated with keys are not case sensitive. A semicolon ( ; ) placed at the beginning of a line specifies that the line is a comment.

Sections may be placed in any order within the Response File. However, if there is more than one section with the same section name, the first section encountered in the Response File will be the one used; any others will be ignored.

Section Headings

The following table lists the sections that apply to the NetWare 5 server installation. For the most part, they are listed in the order they appear during the installation.

Section Heading	Purpose
[NWI:Product Information]	Identifies the specific product version that this Response File is associated with.
[NWI:Language]	Specifies the languages to be installed on the server.
[NWI:Install Options]	Corresponds to the first data input screen.
[NWI:Locale]	Corresponds to the regional settings screen.
[NWI:Mouse and Video]	Corresponds to the mouse and video settings screen.
[NWI:Hardware]	Corresponds to the hardware detection and driver matching function of the installation program. Note: If drivers are found in the Update directories, they will be used instead of the drivers found on the NetWare 5 CD-ROM.
[NWI:Multi-Processor System]	Identifies the driver associated with the processor system in the server.
[NWI:Storage Adapter n]	Identifies the driver and its associated parameters for a specific storage adapter. This section may be duplicated for as many adapters as are in the server. The variable n uniquely identifies the sequence of the section (for example, 1, 2, and so on).
[NWI:Storage Device n]	Specifies storage devices. This section may be duplicated for as many devices as are in the server. The variable n uniquely identifies the sequence of the section (for example, 1, 2, and so on).
[NWI:Network Adapter n]	Identifies the driver and its associated parameters for a specific network adapter. This section may be duplicated for as many adapters as are in the server. The variable n uniquely identifies the sequence of the section (for example, 1, 2, and so on).
[NWI:HotPlug System]	Identifies the driver associated with the processor system in the server.
[NWI:NetWare Loadable Module]	Identifies NLMs that are to be loaded with the hardware drivers.
[NWI:Misc]	For parameters that do not correspond to a data input screen.
[NWI:NW Volume]	Specifies the parameters for the SYS volume and its NetWare partition.
[NWI:File Server]	Specifies the parameters that uniquely identify the server.
[NWI:Protocols]	Controls whether the protocol screen is displayed.
[NWI:TCPIP]	Specifies TCP/IP parameters.
[NWI:IPX]	Specifies IPX parameters.
[NWI:Time Zone]	Corresponds to the time zone screen.
[NWI:NDS]	Corresponds to the NDS screen.
[NWI:License]	Identifies the location of the license file.
[NWI:Time Synchronization]	Identifies time synchronization configuration.
[NWI:DNS]	Specifies Domain Name Service parameters.
[NWI:SNMP]	Specifies Simple Network Management Protocol parameters.
[NWI:Add To Startup]	Specifies lines to be added to the STARTUP.NCF file
[NWI:Append To Autoexec.ncf]	Specifies lines to be added to the AUTOEXEC.NCF file.

The Prompt Key

A Prompt key is listed with each section that corresponds to a data input screen. This key controls whether the screen will be displayed, giving you the ability to pass in the keys and values of the section via the Response File and bypass the screen. If the value of Prompt is True, the screen will be displayed and the data that is specified in the Response File will be presented as default values. If the value of Prompt is False, the screen will not be displayed. However, if any of the required data is missing in the Response File, the screen will be displayed regardless of the Prompt value.

In the following example, the NDS section includes Prompt=True. Therefore the NDS data input screen will be displayed with the specified information already filled in.

[NWI:NDS]
Prompt = True
Tree Name = Novell
New Tree = True
Server Context = O=Utah
Admin Context = O=Utah
Admin Login Name = Admin
Admin Password = install
Display Summary = True
Schema Extensions = sys:/system/schema/NLS.SCH,sys:/system/
   schema/AUDITING.SCH,sys:/system/schema/NWADMIN.SCH,sys:/
   system/schema/NRD.SCH,sys:system/schema/SAS.SCH,sys:/system/
   schema/NDSPKI.SCH,sys:/system/schema/MASV.SCH,sys:system/
   schema/SLP.SCH
Schema Extensions Pre DS = sys:/system/schema/NDS500.SCH,
   sys:/system/schema/NLS.SCH

With this entry in the Response File, the NDS information screen will be displayed with the specified defaults as shown in Figure 2.

Figure 2: Example of the NDS information screen with defaults from the Response File filled in.

If the entry in the Response File were as follows, the NDS input screen and the Summary screens would not be displayed and the NetWare 5 installation program would bypass them.

[NWI:NDS]
Prompt=False
Tree Name = Novell
New Tree = True
Server Context = O=Utah
Admin Context = O=Utah
Admin Login Name = Admin
Admin Password = install
Display Summary = False
. . .

NetWare 5 Response File Sections and Keys

The NetWare 5 installation sections and their associated keys are specified below. Section names and key names are in bold. Included for each key are the default value, possible values, and whether the key is required for the NetWare 5 installation to run silently (for example, to create a new NDS tree without any user input, New Tree=True must appear in the Response File). Also included for each key are an example and a short description of the key's purpose.

[NWI:Product Information] Section

Major Version	= <string<
Default	NetWare 5
Values	(product name)
Required	Yes
Example	Major Version = NetWare 5
Purpose	Specifies the name of the product that this Response File is associated with. If this value does not match that of the NetWare default Response File (normally found in the INSTALL directory on the CD image), the installation will not continue.

Minor Version	= <integer<
Default	00
Values	0-99
Required	Yes
Example	Minor Version = 00
Purpose	Specifies the revision level of the product. If this value does not match that of the NetWare default Response File (normally found in the INSTALL directory on the CD image), the installation will not continue.

[NWI:Language] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the screen is displayed.

Server Language	= <integer<
Default	4 (English)
Values	1-100 (values are specified in INSTALL\PROFILE.TXT on the CD image)
Required	Yes
Example	Server Language = 4
Purpose	Specifies the language that the screens of the installation program will be displayed in. This will also be the default language of the server.

Additional Languages	= <integer(s) separated by commas<
Default	(none)
Values	1-100 (values are specified in INSTALL\PROFILE.TXT on the CD image)
Required	No
Example	Additional Languages = 5,6
Purpose	Specifies additional languages that will be installed on the server.

[NWI:Install Options] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the screen is displayed.

Upgrade	= <string<
Default	False
Values	True or False
Required	Yes
Example	Upgrade = False
Purpose	Specifies whether the installation will be an upgrade or a new installation. False specifies a new installation rather than an upgrade.

Startup Directory	= <string<
Default	C:\NWSERVER
Values	(existing DOS path up to 255 characters)
Required	Yes
Example	Startup Directory = C:\NWSERVER
Purpose	Identifies the directory where the server's initialization files will reside on the Boot Partition.

[NWI:Locale] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the screen is displayed.

Country Code	= <integer<
Default	001
Values	(values are specified in INSTALL\NLS\<language number<\LOCALE.TXT on the CD image)
Required	Yes
Example	Country Code = 001
Purpose	Specifies the country-oriented settings for display.

Code Page	= <integer<
Default	437
Values	(values are specified in INSTALL\NLS\<language number<\LOCALE.TXT on the CD image)
Required	Yes
Example	Code Page = 437
	Purpose Sets the character set for the server.

Keyboard	= <string<
Default	United States
Values	(values are specified in INSTALL\NLS\<language number<\LOCALE.TXT on the CD image)
Required	Yes
Example	Keyboard = United States
Purpose	Sets the keyboard type.

Replace DOS Config Files	= <string<
Default	True
Values	True or False
Required	No
Example	Replace DOS Config Files = True
Purpose	Adds new AUTOEXEC.BAT and CONFIG.SYS files that set a minimal DOS environment and automatically load the server. Pre-existing AUTOEXEC.BAT and CONFIG.SYS files on the server will be renamed to *.000. If this value is set to True and AUTOEXEC.000 already exists, then AUTOEXEC.BAT will be renamed to AUTOEXEC.001 and so on.

Allow User Response File	= <string<
Default	True
Values	True or False
Required	No
Example	Allow User Response File = True
Purpose	Makes the F3 key available on the opening screen. It allows a user to input a path to an additional Response File. Note: Values in a user Response File will override the values of other Response Files passed in previously to the installation program.

[NWI:Mouse and Video] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the screen is displayed.

Mouse	= <string<
Default	PS/2
Values	PS/2, Serial COM1, Serial COM2, No Mouse (values are specified in INSTALL\NLS\<language number<\LOCALE.TXT on the CD image)
Required	Yes
Example	Mouse = PS/2
Purpose	Specifies the mouse type that will be used for the graphical portion of the installation.

Use Super VGA	= <string<
Default	True
Values	True or False
Required	No
Example	Use Super VGA = True
Purpose	Indicates whether 256-color Super VGA is set for the graphical portion of the installation. If set to False, 16-color Standard VGA is set.

[NWI:Hardware] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the screen is displayed.

Update Storage Driver Directory	= <DOS path<
Default	(none)
	The Install always looks in C:\NWUPDATE as well
Values	(existing DOS path up to 255 characters)
Required	No
Example	Update Storage Driver Directory = F:\DRV\UPDATE
Purpose	Specifies the directory path where updated storage (HAM and CDM) drivers will be found. The directory should already exist and be a local DOS path. Note: Associated DDI files must accompany the storage drivers in this directory.

Update Network Driver Directory	= <DOS path<
Default	(none)
	The Install always looks in C:\NWUPDATE as well
Values	(existing DOS path up to 255 characters)
Required	No
Example	Update Network Driver Directory = F:\DRV\UPDATE
Purpose	Specifies the directory path where updated network (LAN) drivers will be found. The directory should already exist and be a local DOS path. Note: Associated LDI files must accompany the storage drivers in this directory.

Update PSM Driver Directory	= <DOS path<
Default	(none)
	The Install always looks in C:\NWUPDATE as well
Values	(existing DOS path up to 255 characters)
Required	No
Example	Update PSM Driver Directory = F:\DRV\UPDATE
Purpose	Specifies the directory path where updated processor (PSM) drivers will be found. The directory should already exist and be a local DOS path. Note: Associated PDI files must accompany the storage drivers in this directory.

Update Source Drive Type	= <string<
Default	(the type of the install source)
Values	Floppy or CD or Network or Other
Required	No, unless one or more of the Update keys above are set
Example	Update Source Drive Type = Network
Purpose	Specifies the type of the source directories identified in the keys above; all directories must be of the same type.

CD-ROM Driver	= <string<
Default	NetWare
Values	NetWare or DOS
Required	No
Example	Source Media Access = NetWare
Purpose	Determines the driver type (DOS or server) used to access the CD-ROM during installation.

PSM Detection	= <string<
Default	True
Values	True or False
Required	No
Example	PSM Detection = True
Purpose	Controls whether driver matching is performed for the processor system. If driver information is identified in the Response File (see Multi-Processor System section), detection may be set to False.

Storage Detection	= <string<
Default	True
Values	True or False
Required	No
Example	Storage Detection = True
Purpose	Controls whether detection of storage adapters and driver matching is performed. If storage adapter and driver information is identified in the Response File (see Storage Adapter section), detection may be set to False.

Network Detection	= <string<
Default	True
Values	True or False
Required	No
Example	Network Detection = True
Purpose	Controls whether detection of network adapters and driver matching is performed. If network adapter and driver information is identified in the Response File (see Network Adapter section), detection may be set to False.

Device Detection	= <string<
Default	True
Values	True or False
Required	No
Example	Device Detection = True
Purpose	Controls whether detection of storage devices and driver matching is performed. If storage adapter and driver information is identified in the Response File (see Storage Device section), detection may be set to False.

HotPlug Detection	= <string<
Default	True
Values	True or False
Required	No
Example	HotPlug Detection = True
Purpose	Controls whether detection of HotPlug devices and driver matching is performed.

[NWI:Multi-Processor System] Section

Driver File	= <filename<
Default	(none)
Values	(name of driver)
Required	No, unless PSM Detection=False
Example	Driver File = MPS14.PSM
Purpose	Identifies the driver to use for the server's multiprocessor system.

[NWI:Storage Adapter n] Section(s)
Example	[NWI:Storage Adapter 1]
Description	This section may be included for each storage adapter in the server. Several keys described under this section are optional. If the driver is detectable by NetWare, only the Driver File key is required for the section. The other keys and values are varied and are extracted from the driver's corresponding DDI file.

Driver File	= <filename<
Default	(none)
Values	(name of driver)
Required	No, unless Storage Detection=False
Example	Driver File = AHA2940.HAM
Purpose	Identifies the driver to use for the storage adapter.

SLOT	= <integer<
Default	(none)
Values	(may be a 5-digit Hardware Instance Number assigned on servers with buses that support detection - such as PCI)
Required	No, unless the driver is for an ISA adapter
Example	SLOT = 2
Purpose	Specifies the bus slot of the storage adapter to which the driver should be loaded.

INT	= <hexadecimal number<
Default	(none)
Values	1-F
Required	No, unless the driver is for an ISA adapter
Example	INT = F
Purpose	Specifies the interrupt that the adapter is set to; this parameter is commonly used for ISA bus adapters.

PORT	= <number<
Default	(none)
Values	(3-digit memory address)
Required	No, unless the driver is for an ISA adapter
Example	PORT = 170
Purpose	Specifies the memory address the adapter is set to; this parameter is commonly used for ISA bus adapters.

[NWI:Storage Device n] Section(s)
Example	[NWI:Storage Device 1]
Description	This section may be included for each storage device in the server.

Driver File	= <filename<
Default	(none)
Values	(name of driver)
Required	No, unless Device Detection=False
Example	Driver File = IDECD.CDM
Purpose	Identifies the driver to use for the storage device.

[NWI:Network Adapter n] Section(s)
Example	[NWI:Network Adapter 1]
Description	This section may be included for each network adapter in the server. Several keys described under this section are optional. If the driver is detectable by NetWare, only the Driver File key is required for the section. The other keys and values are varied and are extracted from the driver's corresponding LDI file.

Driver File	= <filename<
Default	(none)
Values	(name of driver)
Required	No, unless Network Detection=False
Example	Driver File = 3C59X.LAN
Purpose	Identifies the driver to use for the network adapter.

SLOT	= <integer<
Default	(none)
Values	(may be a 5-digit Hardware Instance Number assigned on servers with buses that support detection - such as PCI)
Required	No, unless the driver is for an ISA adapter
Example	SLOT = 10001
Purpose	Specifies the bus slot of the network adapter to which the driver should be loaded.

INT	= <hexadecimal number<
Default	(none)
Values	1-F
Required	No, unless the driver is for an ISA adapter
Example	INT = F
Purpose	Specifies the interrupt that the adapter is set to; this parameter is commonly used for ISA bus adapters.

PORT	= <number<
Default	(none)
Values	(3-digit memory address)
Required	No, unless the driver is for an ISA adapter
Example	PORT = 170
Purpose	Specifies the memory address the adapter is set to; this parameter is commonly used for ISA bus adapters.

Adapter Name	= <string<
Default	(none)
Values	(text up to 255 characters)
Required	No
Example	Adapter Name = 3C59X_1
Purpose	Specifies a unique name for this adapter.

Frame Type n	= <frame type<
Default	(none)
Values	(frame types supported by the driver are found in the driver's LDI file)
Required	No
Example	Frame Type 1 = Ethernet_802.2
Purpose	Identifies the network frame type to be used when loading the driver. There may be as many descriptions as there are frame types supported by the driver - n uniquely identifies the frame type (for example, 1, 2, etc.).

Logical Name n	= <string<
Default	(none)
Values	(text combining the Frame Type with the Adapter Name)
Required	No
Example	Logical Name 1 = 3C59X_1_E82
Purpose	Identifies the name to be used when binding a protocol to a frame type on this adapter. There must be a logical name for each frame type loaded with the driver - n uniquely identifies the frame type (for example, 1, 2, etc.).

Octet Bit Order	= <string<
Default	LSB
Values	LSB or MSB
Required	No
Example	Octet Bit Order = LSB
Purpose	Specifies the bit order (Least Significant Bit or Most Significant Bit) that this network adapter uses for deciphering the node address.

[NWI:HotPlug System] Section

Driver File	= <filename<
Default	(none)
Values	(name of driver)
Required	No, unless HotPlug Detection=False
Example	Driver File = CPQSBD.NLM
Purpose	Identifies the driver to use for the Hotplug system.

[NWI:NetWare Loadable Module] Section

Driver File	= <filename<
Default	(none)
Values	(name of NLM)
Required	No
Example	Driver File = ROUTE.NLM
Purpose	Identifies the NLM to load during installation. This is typically used for network support NLMs.

[NWI:NW Volume] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the SYS Volume and Partition screen is displayed.

SYS Partition Size	= <integer<
Default	(all free space on the first drive identified by NetWare)
Values	(dependent on drive size - takes into account the Minimum SYS Volume Size set by NetWare) (MB)
Required	No
Example	SYS Partition Size = 1000
Purpose	Identifies the size of the NetWare partition on which the SYS volume will be created.

SYS Partition HotFix Size	= <integer<
Default	(calculated on SYS Partition Size)
Values	0 to 120 (MB)
Required	No
Example	SYS Partition HotFix Size = 20
Purpose	Identifies the size of the HotFix redirection area on the partition.

SYS Volume Size	= <integer<
Default	(SYS Partition Size minus SYS Partition HotFix Size)
Values	(250 to The total free space in MB on the SYS partition)
Required	No
Example	SYS Volume Size = 500
Purpose	Identifies the size of the SYS volume.

Allow Volume Properties	= <string<
Default	True
Values	True or False
Required	No
Example	Allow Volume Properties = True
Purpose	Makes the F3 Volume Properties key available on the sys volume screen.

Block Size	= <integer<
Default	(calculated on SYS Volume Size)
Values	4 or 8 or 16 or 32 or 64
Required	No
Example	Block Size = 64
Purpose	Identifies the SYS volume's block size.

Compression	= <string<
Default	True
Values	True or False
Required	No
Example	Compression = True
Purpose	Specifies whether compression is enabled on volume SYS:

Suballocation	= <string<
Default	True
Values	True or False
Required	No
Example	Suballocation = True
Purpose	Specifies whether suballocation is enabled on volume SYS:

Data Migration	= <string<
Default	False
Values	True or False
Required	No
Example	Data Migration = True
Purpose	Specifies whether data migration is enabled on volume SYS:

GUI Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	GUI Prompt = True
Purpose	Controls whether the File System screen is displayed during the graphical portion of the install. Note: If all detectable disk space is not taken by Volume SYS, the graphical disk carving screen will display even if GUI Prompt=False.

[NWI:Misc] Section

Relogin Password	= <string<
Default	(none)
Values	(text)
Required	No, unless it is a network installation
Example	Relogin Password = Novell
Purpose	Specifies the password for the user connection being used while installing across the network. When this section is properly used, the install bypasses the reauthentication screen following the loading of the LAN driver and prior to the preliminary file copy.

[NWI:File Server] Section

Note: Note: This is the first section used during the graphical portion of the installation.

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the screen is displayed.

Servername	= <string<
Default	(none)
Values	(text up to 47 characters - see NetWare documentation for valid set of characters)
Required	Yes
Example	Servername = Novell
Purpose	Specifies the name of the server. (A server is brought up with temporary name until a valid Servername is entered.)

Server ID Number	= <hexadecimal number<
Default	(randomly generated)
Values	00000001-FFFFFFFF
Required	Yes
Example	Server ID Number = 01010101
Purpose	Uniquely identifies the server for network communication purposes. This number should not conflict with any existing IPX addresses or server ID numbers on your network.

[NWI:Protocols] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the protocols screen is displayed.

[NWI:TCPIP] Section

The variable n uniquely identifies each set of bindings (for example, 1, 2, and so on). The address, subnet mask, and gateway variables should have the same value as the corresponding Logical Name.

Logical Name n	= <string<
Default	(none)
Values	(logical name identified in the Network Adapter section(s) of the Response File)
Required	No, unless IP is to be bound
Example	Logical Name 1 = 3C59X_1_EII
Purpose	Identifies the name of the adapter and frame type to which the protocol is to be bound.

IP Address n	= <decimal number<
Default	(none)
Values	(valid IP address)
Required	No, unless Logical Name is set
Example	IP Address 1 = 130.1.130.1
Purpose	Specifies the IP address to be bound with Logical Name n.

Subnet Mask n	= <decimal number<
Default	(none)
Values	(valid IP address)
Required	No, unless Logical Name is set
Example	Subnet Mask 1 = 255.255.255.0
Purpose	Specifies the subnet. Divides the IP address into network address and node address.

Gateway n	= <decimal number<
Default	(none)
Values	(valid IP address)
Required	No
Example	Gateway 1 = 127.127.0.254
Purpose	Identifies the gateway or router through which this server may communicate outside the subnet.

[NWI:IPX] Section

The variable n uniquely identifies each set of bindings (for example, 1, 2, and so on). The address variable should have the same value as the corresponding Logical Name.

Logical Name n	= <string<
Default	(none)
Values	(logical name identified in the Network Adapter section(s) of the Response File)
Required	No, unless IPX is to be bound
Example	Logical Name 1 = 3C59X_1_E82
Purpose	Identifies the name of the adapter and frame type to which the protocol is to be bound.

IPX Address n	= <hexadecimal number<
Default	(address detected or randomly generated by the installation program)
Values	00000001-FFFFFFFF
Required	No, unless Logical Name is set
Example	IPX Address 1 = 01010102
Purpose	Specifies the IPX address to be bound with the Logical Name n.

[NWI:Time Zone] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the time zone screen is displayed.

Time Zone	= <string<
Default	(none)
Values	(3- or 4- character abbreviation. Values are specifed in INSTALL\NLS\<language number<\COMOTHR.ILS on the CD image.)
Required	Yes
Example	Time Zone = MST
Purpose	Specifies the standard time zone.

Use Daylight Saving Time	= <string<
Default	True, if Time Zone supports Daylight Saving Time
Values	True or False
Required	No
Example	Use Daylight Saving Time = True
Purpose	Controls whether daylight savings time is set.

[NWI:NDS] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the NDS input screen is displayed.

Tree Name	= <string<
Default	(none)
Values	(text)
Required	Yes
Example	Tree Name = Novell
Purpose	Specifies the tree name for either a new tree or an existing tree in which to install the server.

New Tree	= <string<
Default	False
Values	True or False
Required	Yes
Example	New Tree = True
Purpose	Specifies whether the NDS tree to be installed is a new tree or install into an existing tree. Note: this key is only used when Prompt=False.

Server Context	= <string<
Default	(none)
Values	(NDS distinguished name)
Required	Yes
Example	Server Context = .install.novell
Purpose	Identifies the NDS context in which the server is to be installed.

Add Replica	= <string<
Default	(none)
Values	True or False
Required	No
Example	Add Replica = True
Purpose	Controls whether a replica is added to the server. This only applies if the server is not one of the first three servers added to an NDS tree (by default the first three servers receive replicas).

Upgrade User Conflict Action	= <string<
Default	(none)
Values	Delete or Merge or Rename
Required	No, unless it is an upgrade from NetWare 3.1x
Example	Upgrade User Conflict Action = Merge
Purpose	Determines what action is to be taken during the upgrade of a NetWare 3.1x server into an NDS tree when objects of the same name are found during the conversion of the bindery to NDS. If conflicts arise, the NDS object of the same name remains intact.

Schema Extensions	= <string<
Default	(none)
Values	(DOS path and schema extension(s) separated by commas)
Required	Yes
Example	Schema Extensions = c:\nwupdate\new.sch
Purpose	Specifies additional schema extensions to be applied during the installation. If the NWI:NDS section is included in a user-defined Response File, the schema extensions found in the Default Response File (in \INSTALL\RESPONSE.TXT on the CD image) must be included in the user's Response File.

Schema Extensions Pre DS	= <string<
Default	(none)
Values	(DOS path and schema extension(s) separated by commas)
Required	Yes
Example	Schema Extensions Pre DS = c:\nwupdate\new.sch
Purpose	Specifies additional schema extensions to be applied during the installation prior to the installation of NDS. If the NWI:NDS section is included in a user-defined Response File, the schema extensions found in the Default Response File (in \INSTALL\RESPONSE.TXT on the CD image) must be included in the user's Response File.

Admin Login Name	= <string<
Default	(none)
Values	(text)
Required	Yes
Example	Admin Login Name = Admin
Purpose	Specifies the name for the server administrator.

Admin Context	= <string<
Default	(none)
Values	(NDS distinguished name)
Required	Yes
Example	Admin Context = .install.novell
Purpose	Identifies the NDS context in which the server administrator is to be installed.

Admin Password	= <string<
Default	(none)
Values	(text)
Required	Yes
Example	Admin Password = Novell
Purpose	Specifies the password for the server administrator. Note that for security purposes, this password is removed from the Response File after NDS is installed.

Admin Language	= <integer<
Default	4 (English)
Values	1-100 (values are specified in INSTALL\PROFILE.TXT on the CD image)
Required	Yes
Example	Admin Language = 4
Purpose	Specifies the language of the server administrator. User objects created by the server administrator will be assigned this language.

Display Summary	= <string<
Default	True
Values	True or False
Required	Yes
Example	Display Summary = True
Purpose	Controls whether the NDS Summary screen is displayed

[NWI:License] Section

Prompt	= <string<
Default	True
Values	True or False
Required	Yes
Example	Prompt = True
Purpose	Controls whether the license screen is displayed.

License File	= <string<
Default	(none)
Values	(existing DOS path and envelope file name - up to 255 characters)
Required	No, unless a license is to be installed
Example	License File = C:\NWSERVER\0000001.NLF
Purpose	Identifies the directory and file name of a license envelope file. If Prompt=False and no License File value is found, the server will be installed without a license.

Display License Agreement	= <string<
Default	True
Values	True or False
Required	Yes
Example	Display License Agreement = False
Purpose	Controls whether the license agreement screen is displayed at the beginning of the installation.

[NWI:Time Synchronization] Section

Time Server Type	= <string<
Default	(Single if new tree, Secondary if existing tree)
Values	Single or Primary or Secondary or Reference
Required	No
Example	Time Server Type = Single
Purpose	Specifies the time server type.

[NWI:DNS] Section

Domain	= <string<
Default	(none)
Values	(text)
Required	No
Example	Domain = novell.com
Purpose	Specifies a domain.

Nameservers	= <decimal numbers separated by commas<
Default	(none)
Values	(valid IP addresses)
Required	No
Example	Nameservers = 131.1.131.1, 131.1.131.2
Purpose	Identifies the servers to be used for name resolution.

[NWI:SNMP] Section

Hardware	= <string<
Default	(none)
Values	(text)
Required	No
Example	Hardware = Personal Computer
Purpose	Identification information that is sent with SNMP traps to assist in troubleshooting.

Location	= <string<
Default	(none)
Values	(text)
Required	No
Example	Location = Building A
Purpose	Identification information that is sent with SNMP traps to assist in troubleshooting.

Contact	= <string<
Default	(none)
Values	(text)
Required	No
Example	Contact = John Doe
Purpose	Identification information that is sent with SNMP traps to assist in troubleshooting.

Trap Targets TCPIP	= <decimal numbers separated by commas<
Default	(none)
Values	(valid IP addresses)
Required	No
Example	Trap Targets TCPIP = 127.1.127.3
Purpose	Identifies IP address of a computer to which SNMP traps are sent.

Trap Targets IPX	= <MAC address separated by commas<
Default	(none)
Values	(8-character IPX address:12-character node number)
Required	No
Example	Trap Targets IPX = C9990111:000001B555555
Purpose	Identifies MAC addresses of a computer to which SNMP traps are sent.

[NWI:Add To Startup] Section

Prepend Line n	= <string<
Default	(none)
Values	(text)
Required	No
Example	Prepend Line 1 = SET IGNORE DISK GEOMETRY=ON
Purpose	Adds the line to the beginning of the STARTUP.NCF file. If multiple lines are listed, n should increment sequentially.

Append Line n	= <string<
Default	(none)
Values	(text)
Required	No
Example	Append Line 1 = LOAD NFS.NAM
Purpose	Adds the line to the end of the STARTUP.NCF file. If multiple lines are listed, n should increment sequentially.

[NWI:Append To Autoexec.ncf] Section

Line n	= <string<
Default	(none)
Values	(text)
Required	No
Example	Line 1 = LOAD MONITOR
Purpose	Adds the line to the end of the AUTOEXEC.NCF file. If multiple lines are listed, n should increment sequentially.

* 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.