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 SPx CD 1 (Operating System) and NetWare 6.5 SPx 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.
To fully or partially automate a new server installation with a response file:
Create or edit a response file, using either the NetWare Response File Utility in YaST or the Response File Generator in Deployment Manager.
Be sure to select as the installation type for the response file.
Refer to Section A.3, Using the NetWare Response File Utility in YaST or Section A.4, Using the Response File Generator in the Deployment Manager for details.
Make sure you have prepared the new server hardware as discussed in Section 4.3, Preparing the Computer.
Copy the response file and license file to the location you designated when creating the response file.
Insert NetWare 6.5 SPx CD 1 (Operating System) into the server’s CD drive and reboot the machine.
Press any key to interrupt the preparation to install, then press P to specify additional installation parameters.
Enter [inst: rf=response_file_path_and_name].
For example, [inst: rf=c:\response\response.rsp].
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.
Although local and remote server upgrades are no longer supported in NetWare 6.5 SP8, the ability to create a response file to automate these types of upgrades remains in the NetWare Response File Utility and in the Response File Generator for compatibility with previous versions of NetWare.
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:
Create or edit a response file, using the NetWare Response File Utility in YaST or the Response File Generator in Deployment Manager.
Be sure to select or as the installation type for the response file.
Refer to Section A.3, Using the NetWare Response File Utility in YaST or Section A.4, Using the Response File Generator in the Deployment Manager for details.
Copy the following files additionally created by the NetWare Response File Utility or 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
Make sure you have prepared the server for the upgrade as discussed in Section 4.3, Preparing the Computer.
At the server console, execute the .ncf file to start the upgrade.
(Conditional) If the upgrade fails after the health checks have been performed, you can resume the upgrade as follows:
Shut down the server.
Insert NetWare 6.5 SPx CD 1 (Operating System) into the CD drive and reboot the machine.
Press any key to interrupt the installation preparation, then press P to specify additional installation parameters.
Enter [inst: upgrade rf=response_file_path_and_name].
For example, [inst: upgrade rf=c:\response\response.rsp].
Press I to proceed with the upgrade.
A remote upgrade is one that is performed from a workstation on the network, using either Deployment Manager or iManager.
NOTE:In NetWare 6.5 SP8 (NetWare 6.5 SP8), the remote upgrade functionality has been removed from both Deployment Manager and iManager. The procedure described below can be completed only if you have a previous version of NetWare 6.5.
To automate a remote upgrade of a NetWare server with a response file;
At a Windows 2000 or XP workstation, insert NetWare 6.5 SPx CD 1 (Operating System).
Start Deployment Manager by executing nwdeploy.exe (or nwdeploynobrowser.exe for the nonbrowser version) from the root of the CD.
Under , click .
Read the information about automated server installations, then click the link.
After accepting the license agreements, click .
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 A.4, Using the Response File Generator in the Deployment Manager for details.
Make sure you have prepared the server for the upgrade as discussed in Section 4.3, Preparing the Computer.
At your Windows workstation, open a command prompt window.
Change to the folder where you have copied the NetWare installation files.
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.
(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.
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 sys:creation, and file copy portions of the install. This “image” 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 sys:; and configuration of time zone, eDirectory™, licensing, and other products. This “configuration” phase is meant to be performed 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 NetWare Response File Utility or the Response File Generator. Be sure to select Factory Installation as the installation type for the response file.
IMPORTANT:In a factory install, a response file must be used for both phases of the installation. You cannot use a response file for Phase 1 and then answer the installation prompts manually for Phase 2.
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.