A.4 Using the Response File Generator in the Deployment Manager

The Response File Generator utility is launched from the Novell Deployment Manager and guides you through configuration questions that appear during a normal NetWare installation or upgrade. The input you provide for those configuration questions is used to generate a response file that can be used to automate your NetWare server installations and upgrades.

IMPORTANT:The Response File Generator is designed for installing selectable products with their default parameter values only. Custom values must be entered into the response file manually, using information found in Section A.5.3, Response File Sections and Keys.

A.4.1 Launching the Response File Generator

  1. On a Windows 2000 or Windows XP Professional Edition workstation that has the latest Novell Client™ installed on it, log in to your existing network as a user with the Supervisor right.

    If you are prompted to log in again while running Novell Deployment Manager, you can specify the IP address of the server by clicking Details.

  2. Insert NetWare 6.5 SPx CD 1 (Operating System) into the CD drive and run the Deployment Manager (nwdeploy.exe or nwdeploynobrowser.exe for the nonbrowser version) located at the root of the CD.

  3. In the left frame of the browser window, under the heading Install/Upgrade Options, click the Automate an Installation link.

  4. Read the instructions on automating the NetWare installation using a response file.

  5. To launch the Response File Generator utility, click the Response File Generator link.

A.4.2 Creating a Response File with the Response File Generator

The Response File Generator takes you through a series of screens to gather the information it needs to create a response file. Some of these screens are unique to the Response File Generator; others are similar to screens you see in the NetWare installation program.

Accepting the License Agreements

You are first prompted to accept two license agreeements: one for Novell software and one for the JReport* Runtime software used by the Response File Generator. Accepting both license agreements means that you have read and agreed to the terms and conditions contained in the license agreements.

  1. Select I Accept to accept the Novell Software license agreement.

  2. Select I Accept to accept the JReport Runtime license agreement.

Selecting the Response File Type

You have the option to create a response file for a new server, a factory install, a local server upgrade, or a remote server upgrade.

  1. Click the radio button next to the selection you want:

    • New Server: Select this option to create a response file for a new NetWare server installation.

    • Upgrade Server Locally: Select this option to create a response file to be used when performing a local upgrade of a NetWare server.

    • Upgrade Server Remotely: Select this option to create a response file to be used when upgrading a server from a workstation on the network, using either Novell Deployment Manager or Novell iManager.

    • Factory Install/Blade Image: Select this option to create a response file to be used when performing a factory installation of a NetWare server.

  2. Click Next.

Selecting a Template Response File

If you have a template response file, you can use it as a starting point in the creation of your customized response file. The settings found in the template response file are used to automatically fill in the input fields as you go through the Response File Generator. You can change these settings as required for your purposes.

  1. If you want to use a template response file, select Use a Response File Template. Otherwise, proceed to the next screen.

  2. Specify the path and name for the template response file, or use the browse button to select the template file.

    The description for the template response file is displayed to help you confirm that you have selected the correct file.

  3. Click Next.

Entering the Source Server Information

To facilitate the automated installation or upgrade of NetWare servers, you can copy the NetWare installation files from NetWare 6.5 SPx CD 1 (Operating System) and NetWare 6.5 SPx CD 2 (Products) to a “source” server. The install program can then access the files from this source server instead of from a local CD drive or hard disk.

  1. If you have copied the installation files to a NetWare source server, select Remote NetWare Server for new server and factory installations, or NetWare Server for local upgrades.

    If you want to access the installation files locally, select Local Storage (HDD, CD-ROM) for new server and factory installations, or Workstation for remote upgrades. Proceed to the next screen.

  2. In the Server Name field, type the name of the source server containing the installation files.

  3. In the Server IP Address fields, type the IP address of the source server.

  4. In the Source Location Path field, type the path to the folder where you copied the NetWare installation files.

  5. Click Next.

  6. In the next screen, specify the following eDirectory information for the source server:

    • Tree Name: The name of the eDirectory tree in which the source server’s Server object exists.

    • Context for Server Object: The full path of the source server object in the eDirectory tree. For example, if the source server object is in an Organizational Unit (OU) named Sales under the Organization (O) named Novell, the context would be denoted as OU=Sales.O=Novell or Sales.Novell.

    • User Name: The Common Name (CN) of the user to use when logging in to the tree.

    • User Context: The full eDirectory context for the user object.

    • Password: Type and retype the user's password to verify accuracy.

  7. When the warning about passwords being saved in the response file in clear text displays, click OK.

Entering the Destination Server Information

The destination server is the new server for new server and factory installations, or the server to be upgraded for remote upgrades. If you are creating a response file for a local server upgrade, skip to the next section.

  1. In the Server Name field, specify the name for the new server or the server to be upgraded remotely.

    The NetWare server name must be unique from all other servers in the eDirectory tree. The name can be between 2 and 47 alphanumeric characters and can contain underscores (_) and hyphens (-), but no spaces. The first character cannot be a period (.).

    IMPORTANT:The server name must be different from the name that you plan to use for the eDirectory tree.

  2. If you are creating a response file for a remote server upgrade, type the IP address of the server to be upgraded in the Server IP Address fields.

  3. Click Next.

  4. In the next screen, specifyt he following eDirectory information for the destination server:

    NOTE:If the new server is to be installed into a new eDirectory tree, select New Tree. Leave New Tree deselected to install the server into an existing eDirectory tree.

    • Tree Name: The name of a new or existing eDirectory tree in which you want the server’s Server object to be created.

    • Context for Server Object: The full path of the Server object in the eDirectory tree. For example, a NetWare server might be installed into an OU named Sales under the O named Novell. The context would be denoted as OU=Sales.O=Novell or Sales.Novell.

    • Admin Name: The Common Name (CN) of an Admin user with rights to install servers in the tree.

    • Admin Context: The full eDirectory context for the Admin user object.

    • Password: Type and retype the Admin password to verify accuracy.

  5. When the warning about passwords being saved in the response file in clear text displays, click OK.

If you are creating a response file for a server upgrade, skip to Specifying License Location.

Configuring the Networking Protocols

NetWare provides support for IP (Internet Protocol) network packets and traditional IPX (Internetwork Packet Exchange™) packets. Both protocols can be assigned to a single network board, which allows the server to communicate using both IP and IPX.

IP is selected by default. To configure the networking protocols for your destination server:

  1. In the IP Address fields, type the server’s IP address.

    The IP address identifies the server on the network. The address consists of 32 bits, which are represented as decimal values separated by periods, such as 123.45.67.89. If your server will connect to the Internet, you must specify a unique IP address.

  2. In the Subnet Mask fields, type the subnet mask for your subnet.

  3. In the Router (Gateway) fields, type the IP address of the nearest router or gateway for the destination server to use.

  4. (Optional) To enable support for IPX, select the IPX check box.

  5. Select the frame types you want the server to support (Ethernet_802.2, Ethernet_802.3, Ethernet_SNAP, or Ethernet_II) by clicking the corresponding radio buttons.

  6. Type the server ID in the field provided. This is an 8-digit hexadecimal number used to identify the server in IPX communications.

    You can add IPX after the server installation by adding the SERVERID 8_digit_number command after the SERVERNAME command in autoexec.ncf. If you choose to install IP but not IPX, the SERVERID reference is not used and is removed from autoexec.ncf.

  7. Click Next.

Selecting the Language and Regional Settings

NetWare servers can display information in several languages. The language selection screen lets you select the language, country code, code page, and keyboard code you want the server to use.

  1. Select a language from the drop-down list provided.

    English is the default.

  2. Select a country code from the drop-down list provided.

    001 (USA) is the default.

  3. Select the code page you want from the drop-down list provided.

    437 (United States English) is the default.

  4. Select the keyboard code you want from the drop-down list provided.

    United States is the default.

  5. After making your selections, click Next.

Specifying License Location

NetWare servers must have a valid license in order to function. The server license (*.nlf) file is located on the NetWare 6.5 CDs in the /LICENSE folder. If you have an older version of NetWare 6.5, the license is located on the NetWare 6.5 License/Cryptography diskette.

When creating a response file, you must indicate the location of the license file to use for the server to be installed or upgraded. This is done in the Licenses screen. Later, when you save the response file, you will indicate where the NetWare install program should look for the license file.

  1. In the License Location field, specify the path to the license file or click the browse icon to locate the folder containing your license (.nlf) files.

    In most cases, you would specify a location on the server’s local hard drive where you have copied the license files from the installation CDs. If you have a NetWare 6.5 License/Cryptography diskette, the License Location would be A:\.

  2. Select Verify License Path if you want the Response File Generator to verify that a specific .nlf file exists in the location you specified in Step 1. Otherwise, just specify the path and it will use the first .nlf file found in that path.

    IMPORTANT:If no valid license file can be found when the response file installation is run, the install fails.

  3. (Optional) To have the response file install or upgrade NetWare without licenses, select Install Without Licenses.

    Although a server can be installed without a license, the unlicensed server will allow only two user connections. After installation, you can use the Novell iManager utility to install additional licenses. See Section 4.25.2, Installing NetWare Licenses for instructions.

  4. Click Next.

Setting Miscellaneous Options for Server Upgrades

This section applies only if you are creating a response file for a local or remote server upgrade.

  1. Specify whether you want to back up the server boot directory files by selecting the appropriate option. Yes is the default.

  2. If you answer Yes, type the location where you want the existing files in c:\nwserver to be backed up prior to beginning the upgrade. The default location is c:\nwserver.old.

  3. Specify whether you want the server to automatically reboot after the upgrade is complete by selecting the appropriate option. The default is Yes.

  4. Specify whether you want the NetWare install program to use untested LAN and disk drivers if no certified drivers can be found by selecting the appropriate option. No is the default.

  5. Select a Default or Manual upgrade by selecting the appropriate option.

    The Default (formerly called Express) upgrade automatically detects the server hardware and selects appropriate drivers. It also uses the default NetWare server installation settings.

    The Manual (formerly called Custom) upgrade lets you modify detected drivers and configure server settings.

  6. Click Next.

Specifying SLP Parameters

NOTE:This procedure is optional.

Service Location Protocol (SLP) is an IETF standard for enabling network-based applications to automatically discover the location, including the address or domain name and other configuration information, of a required service. Using SLP, clients can connect with and make use of services on an IP network. Without SLP, network resources must be manually configured or entered into a separate configuration file.

If you choose to use SLP, it should be configured properly if the server is going to be a part of a migration that uses the NetWare Migration Wizard utility.

  1. Specify the IP addresses of the Directory Agents (DAs) on your network in the fields provided.

    If no Directory Agents exist on your network, select Configure This Server As a DA.

  2. Type the SLP scope list in the field provided.

  3. (Optional) To configure this server to be a DA, select Configure This Server as a DA (Directory Agent).

  4. (Optional) To enable multicasting, select Enable Multicast Routing on This Server.

  5. Click Next.

Setting Up Domain Name Service

NOTE:This procedure is optional. If this server is not available to the Internet, you can skip this screen and ignore any associated error messages.

The IP protocol identifies computers and systems by their assigned IP addresses, such as 123.45.56.89. Domain Name Service (DNS) allows a specific server on the network to maintain a list of simple, readable names that match IP addresses. Applications (or protocols) that require IP addresses rather than names can use a DNS server to translate from one form to another.

  1. Provide the following information on the Domain Name Service page:

    • Host Name: The simple, readable name on the DNS server that matches this NetWare server’s name (or the name that you have bound to the network board).

      You can set up the host computer name on the DNS server to use the NetWare server name.

    • Domain: The hierarchical name that represents the organization of your network, such as novell.com.

    • Name Servers: The IP address of the DNS server that maintains the list containing this NetWare server’s simple, readable name and IP address. For more information, contact your network administrator or Internet Service Provider.

  2. (Optional) To have the install verify the domain name service information for you, select Verify the DNS Information.

  3. Click Next.

Setting the Server Time Zone

The server time and time zone are important in order to synchronize network events.

  1. On the Time Zone page, select the correct time zone setting from the available list.

  2. Select Daylight Saving Time if you want the system to adjust the server’s clock automatically for this.

  3. Click Next.

Configuring Time Synchronization

Specifying the type of time server allows the synchronization of the reported time across the network. It also provides expiration dates and time stamps to establish the order of events taking place in eDirectory. NetWare distinguishes three types of time servers that provide network time: Single Reference, Reference, and Primary. All other servers are called Secondary time servers because they receive their time from the time providers.

  1. On the Time Synchronization page, select the time server type that you want.

  2. (Conditional) If you do not want to accept the defaults, do the following:

    1. Select Use Timesync Configured Sources.

    2. Type the time sources in the fields provided (up to three).

      Timesync time sources can be specified in any of three different formats:

      • IP address

      • DNS name

      • Server name (IPX required)

    3. (Conditional) If your time source uses Network Time Protocol (NTP), select the NTP option to the right of the time source.

  3. Click Next.

Setting Miscellaneous Installation Options

This section applies only if you are creating a response file for a new server or factory installation.

  1. Specify whether you want the server to automatically reboot after the install is complete. The default is Yes.

  2. Specify whether you want the NetWare install program to use untested LAN and disk drivers if no certified drivers can be found. No is the default.

  3. Click Next.

Choosing a Server Pattern

This section applies only if you are creating a response file for a new server or factory installation. If you are creating a response file for a server upgrade, skip to Selecting Components to Upgrade.

On the Choose a Pattern page, you are given the opportunity to select a pattern for the server you want to install. Selecting a special-purpose server (pattern) displays a description of that server pattern in the Description window.

Table A-1 lists the server patterns available in NetWare 6.5. The exact patterns that are available vary depending on the NetWare 6.5 Support Pack level.

Table A-1 Server Patterns in NetWare 6.5

Server Pattern

Description

Customized NetWare Server

Lets you select the optional products you want to be installed on the server.

Basic NetWare File Server

Installs only basic NetWare with the minimum required additional products.

Pre-Migration Server

Creates a server that data will be migrated to at a later time by using the Netware Migration Wizard.

DNS/DHCP Server

Sets up the Novell eDirectory tree for directory-enabled DNS/DHCP services.

exteNd™ J2EE* Web Application Server

Installs an optimized configuration of the Novell exteNd Application Server.

LDAP Server

Installs Lightweight Directory Access Protocol (LDAP) Services for Novell eDirectory.

NetWare AMP (Apache, MySQL, PHP, and Perl) Server

Lets you host open source Web database applications on a NetWare server.

NetWare Backup Server

Installs the infrastructure for backup and restore services on the NetWare platform.

QuickFinder Server

Installs the products necessary for a QuickFinder™ Web search server.

Network Attached Storage (NAS) Server

Installs multiple-file protocol storage for your network.

Novell iPrint Server

Installs the Novell recommended print solution

Apache/Tomcat Server

Installs Apache Web Server and the Jakarta-Tomcat Servlet Container for use in hosting dynamic, application-driven Web sites.

Novell Nsure™ Audit Starter Pack Server

Installs the centralized auditing service that is built into NetWare.

iSCSI SAN Storage Server

Turns your NetWare server into an iSCSI Storage Server (also known as an iSCSI Target).

Management Server

Installs Novell iManager and Novell ConsoleOne® network administration software to provide a complete management solution for your server environment.

Novell iFolder Storage Server

Installs a dedicated iFolder® server.

Virtual Office Server

Installs Virtual Office, which provides a collaboration solution that addresses the need for users to be self sufficient with their IT needs.

  1. Select the server pattern you want.

  2. Click Next.

Skip to Saving the Response File.

Selecting Components to Upgrade

This section applies only if you are creating a response file for a server upgrade.

The Response File Generator lists the components available to be installed during the server upgrade. For NetWare 6.5, these include the following:

  • Apache2 Web Server and Tomcat 4 Servlet Container

  • iPrint

  • NetWare FTP Server

  • QuickFinder Server

  • WAN Traffic Manager Services

  • Novell DNS/DHCP Services

  • Novell iFolder Storage Services

  • eDirectory SNMP Subagent

  • MySQL

  • Tomcat 5 Servlet Container

  • exteNd Application Server

  • Novell Nsure UDDI Server

  • Novell Nsure Audit Starter Pack

  • iSCSI Target

  • Refresh native File Access Login Methods

  • Novell netstorage

  • OpenSSH

  • WAN Connectivity

  • eGuide

  • Novell iManager

  • Novell Virtual Office

Selecting a component adds that component to the list of software to be installed or upgraded as part of the server upgrade. Deselecting removes the component from the list of products and services to be installed, but does not cause the component to be uninstalled if it already exists on the server.

  1. Select the components you want to be installed or upgraded. When you select a component, a description of that component is displayed in the Description box.

    To select all available components, select Select All.

    To deselect all components, select Clear All.

  2. Click Next.

Saving the Response File

In order to use the response file generated by this utility, it must be saved to a location where the install can find it. Saving the response file to a floppy disk is recommended.

  1. Type the response file name in the field provided.

  2. In the Temporary Response File Location field, type a local path or click the Browse icon and browse to the location where you want to save the response file.

    The default is A:\.

  3. In the Response File and Licenses Install Location field, type the path where the NetWare installation program should look for the response file and server license file.

    The default is A:\. If you plan to copy the response file and license to another location, such as a folder on the server’s C: drive, be sure to do so before you run the automated install or upgrade.

  4. (Optional) Provide a customized description for this response file by typing it in the field provided.

  5. Click Next.

The generated response file is saved to the specified location and is now ready to be used for a response file installation or upgrade.