1.4 Response File Usage Scenarios

This section provides basic instructions for the following response file usage scenarios:

In each of these scenarios, you can save time and a CD swap by copying the NetWare installation files from NetWare 6.5 SP5 CD 1 (Operating System) and NetWare 6.5 SP5 CD 2 (Products) to a source location that is accessible to the install program. Depending on the scenario, this could be a remote NetWare server, a server’s local hard disk drive or, in the case of a remote silent upgrade, the workstation that you are running Deployment Manager on.

1.4.1 Automating a New Server Installation

To automate a new server installation, either fully or partially, with a response file, follow these steps.

  1. At a Windows 2000 or XP workstation, insert NetWare 6.5 SP5 CD 1 (Operating System).

  2. Start Deployment Manager by executing nwdeploy.exe (or nwdeploynobrowser.exe for the nonbrowser version) from the root of the CD.

  3. Under Installation/Upgrade Options, click Automate an Installation.

  4. Read the information about automated server installations, then click the Response File Generator link.

  5. After accepting the license agreements, click New Server.

    As prompted, fill in the install information for the new server. See the online help for assistance.

    At the end of this process, you designate the response file name, a temporary local path for the response file, and a location where the install program should look for the response file and license files. You can also type a customized description to identify the purpose of the response file.

    Refer to Section 2.0, Using the Response File Generator for details.

  6. Make sure you have prepared the new server hardware as discussed in Preparing the Computer in the OES NetWare Installation Guide.

  7. Copy the response file and license file to the location you designated when creating the response file.

  8. Insert NetWare 6.5 SP5 CD 1 (Operating System) into the server’s CD drive and reboot the machine.

  9. Press any key to interrupt the preparation to install, then press P to specify additional installation parameters.

  10. Enter [inst: rf=response_file_path_and_name].

    For example, [inst: rf=c:\response\response.rsp].

  11. Press I to proceed with the installation using the parameters specified in the response file.

If the response file contains all of the necessary installation parameters, the install program proceeds with little or no intervention required.

If some of the necessary parameters were left out of the response file, the install program prompts you for the missing information.

1.4.2 Performing a Factory Installation

A factory installation can reduce the complexity and the amount of time spent on an installation. In this scenario, much of the hardware configuration and file copying is done in the factory so that you need to use only the graphical portion of the NetWare installation to complete the on-site configuration. Because the network operating system files are precopied to the server, installation time is reduced to just a few minutes.

In a factory installation, the NetWare server installation is split into two phases:

  • Phase 1 performs the disk detection, disk partitioning, volume sys: creation, and file copy portions of the install. This phase is meant to be performed in a factory or configuration center.
  • Phase 2 focuses on user configuration parameters. It includes the setting of the server name; protocol binding; creation of volumes other than sys:; and configuration of time zone, eDirectory™, licensing, and other products. This phase is meant to be performed by the customer at the server’s permanent location.

After Phase 1 is completed, the machine can be powered off. When the server is restarted, the graphical interface launches for Phase 2 of the installation.

To ensure that all required keys for an automated install are included in the response file, Novell recommends using the Response File Generator. Be sure to select the Factory Install/Blade Image option described in Selecting the Response File Type.

If you are manually creating a response file for a factory install, add the following section and key:

[Initialization]

Install State=Second

Name the finished response file response.tmp and save it in the c:\nwinst.tmp directory on the server’s C: drive.

1.4.3 Automating a Local Server Upgrade

A local upgrade is one that is performed on the server itself. To automate a local upgrade of a NetWare server with a response file, follow these steps.

  1. At a Windows 2000 or XP workstation, insert NetWare 6.5 SP5 CD 1 (Operating System).

  2. Start Deployment Manager by executing nwdeploy.exe (or nwdeploynobrowser.exe for the nonbrowser version) from the root of the CD.

  3. Under Installation/Upgrade Options, click Automate an Installation.

  4. Read the information about automated server installations, then click the Response File Generator link.

  5. After accepting the license agreements, click Upgrade Server Locally.

    As prompted, fill in the information for the server to be upgraded. See the online help for assistance.

    At the end of this process, you designate the response file name, a temporary local path for the response file, and a location where the install program should look for the response file and license files. You can also type a customized description to identify the purpose of the response file.

    Refer to Section 2.0, Using the Response File Generator for details.

  6. Copy the following files additionally created by the Response File Generator, along with the response file and license file, to the location you designated when creating the response file:

    • response_file_name.ncf
    • response_file_name.ips

  7. Make sure you have prepared the server for the upgrade as discussed in Preparing the Computer in the OES NetWare Installation Guide.

  8. At the server console, execute the .ncf file to start the upgrade.

  9. (Conditional) If the upgrade fails after the health checks have been performed, you can resume the upgrade as follows:

    1. Shut down the server.

    2. Insert NetWare 6.5 SP5 CD 1 (Operating System) into the CD drive and reboot the machine.

    3. Press any key to interrupt the installation preparation, then press P to specify additional installation parameters.

    4. Enter [inst: upgrade rf=response_file_path_and_name].

      For example, [inst: upgrade rf=c:\response\response.rsp].

    5. Press I to proceed with the upgrade.

1.4.4 Automating a Remote Server Upgrade

A remote upgrade is one that is performed from a workstation on the network, using either Deployment Manager or iManager. To automate a remote upgrade of a NetWare server with a response file, follow these steps.

  1. At a Windows 2000 or XP workstation, insert NetWare 6.5 SP5 CD 1 (Operating System).

  2. Start Deployment Manager by executing nwdeploy.exe (or nwdeploynobrowser.exe for the nonbrowser version) from the root of the CD.

  3. Under Installation/Upgrade Options, click Automate an Installation.

  4. Read the information about automated server installations, then click the Response File Generator link.

  5. After accepting the license agreements, click Upgrade Server Remotely.

    As prompted, fill in the information for the server to be upgraded. See the online help for assistance.

    At the end of this process, you designate the response file name, a temporary local path for the response file, and a location where the install program should look for the response file and license files. You can also type a customized description to identify the purpose of the response file.

    Refer to Section 2.0, Using the Response File Generator for details.

  6. Make sure you have prepared the server for the upgrade as discussed in Preparing the Computer in the OES NetWare Installation Guide.

  7. At your Windows workstation, open a command prompt window.

  8. Change to the folder where you have copied the NetWare installation files.

  9. Start the upgrade by entering the following command:

    nwdeploy -rf=response_file_path_and_name -cfg=ni/windows/install.cfg

    For example, nwdeploy -rf=h:\install\response.rsp -cfg=ni/windows/install.cfg.

  10. (Conditional) If the upgrade fails to reconnect after the first server reboot, run the finishup.ncf command at the server console.

    The upgrade finishes locally.