Set AutoInstall Attributes

Configure the following settings for a Kickstart script bundle to be used to automate a Red Hat installation. When the device boots, the Kickstart bundle is executed before the operating system boots. Preboot Services cannot control what might happen if the Kickstart bundle has errors in it.

Preboot Environment Variables

Before configuring the Preboot environment variables, ensure that you have copied the kernel and RAM drive files from the Red Hat Enterprise Linux installation source to the /srv/tftp/kickstart/ on your Imaging server. By default, the kernel file (vmlinuz) and the RAM drive file (initrd.img) are located in the /isolinux directory in the Red Hat Enterprise Linux installation source.

Linux Kernel Filename: Specify the relative path of vmlinuz in the tftp directory. The path should be relative to the default directory of the TFTP daemon.

For example, if vmlinuz is located in the /srv/tftp/kickstart/ directory on your Imaging server, you must specify the path of the file as kickstart/vmlinuz.
Initial RAM Drive Filename: Specify the relative path of initrd.img in the tftp directory.The path should be relative to the default directory of the TFTP daemon.

For example, if initrd.img is located in the /srv/tftp/kickstart/ directory on your Imaging server, you must specify the path of Linux kernel file as kickstart/initrd.img.
Additional Kernel Parameters: Specify the additional kernel parameters that your Linux kernel might need. These are not Preboot Services or ZENworks parameters. They are parameters that your Linux kernel needs. For more information about the kernel parameters, see your Linux documentation.

Kickstart Configuration Source

Configure the location of the Kickstart configuration file, and the settings required to acess the file. You can either specify the file location or browse for and select the file.

Specify Script Location: Configure the following settings to access the configuration file:
- Protocol: Select the protocol to be used to access the device containing the Kickstart configuration file. The available protocols are NFS and HTTP.
- Script Name and Path (Relative to Protocol Default Directory): Specify the Kickstart configuration filename and its complete path. The path should be relative to the home directory of the selected protocol daemon.
  
  For example, if you specify HTTP as the protocol, myserver.provo.novell.com as the DNS name, and /config/ks.cfg as the complete path of the configuration file, the URL to the installation directory is:
  
  http://myserver.provo.novell.com/config/ks.cfg
  
  In this example, /config/ks.cfg is relative to the protocol and server ID.
Browse for Script: Browse for the Kickstart configuration file, and upload it to the Imaging server.
1. Click to display the Upload File dialog box.
2. Click Browse to browse for and select the Kickstart configuration file (.cfg).
3. When you are prompted to upload the file to the Imaging server, click OK.
  
  The Status field displays the upload status.
4. Click OK.
5. (Optional) Modify the configuration file content:
  1. Click Edit Script.
    
    The content of the configuration file is displayed in the Edit Kickstart File dialog box.
  2. Edit the script content, then click Save.
    
    You can also specify ZENworks system variables in the script. For more information about ZENworks system variables, see the Novell ZENworks 11 System Administration Reference.