Response File Information
Articles and Tips: tip
Novell, Inc.
01 Aug 2002
Entering a Response File at the Command Line
To enter a response file at the command line, perform the following steps:
Copy the response file to a diskette, to a hard disk, or to a network directory that is accessible by the server upon which you are installing NetWare.
Start the server installation from the CD, hard disk, or network directory by entering:
INSTALL /RF=response_file_DOS_path\filename
Replace the response file DOS path with the path for the response file, and filename with the name of the response file. For example, if you are installing NetWare from a CD and the response file is on a diskette, you could enter:
D:\INSTALL /RF=A:\RESPONSE.TXT
Using a Response File During a Server Installation
To use a response file during a server installation, perform the following steps:
Copy the response file to a diskette, to a hard disk, or to a network directory that is accessible to the server upon which you are installing NetWare.
Enter INSTALL to start the server installation.
On the Install Options screen (the first screen after the language section), press <F3> for the Response File window.
Enter the path for the response file, and then press <Enter>.
Continue with the rest of the server installation.
Editing a Response File from a Previous Server Installation
You can generate a response file from a server installation or upgrade and then use that file 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 configurations. The steps are:
Perform the first server installation, and then reboot the server by clicking 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 either a diskette or to the new server.
Modify the file by adjusting the parameters and removing unwanted sections.
* 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.