A Kickstart bundle contains the location and access protocol of an KickStart configuration file for Red Hat Linux. This bundle allows you to launch an automated installation of Red Hat Linux using Preboot Services
To configure a Kickstart bundle and assign devices to the bundle:
In ZENworks Control Center, clickin the left pane to display the Bundles panel.
Click> to start the Create New Bundle Wizard.
Select, then click .
On the Select Bundle Category page, select, then click to display the Define Details page.
Fill in the fields:
Bundle Name: (Required) Although bundles can be identified in ZENworks Control Center by their type of icon, as well as the folder they are listed under, you should develop a naming scheme that differentiates the Kickstart bundles that are listed together in a folder.
Folder: Browse for the location where you want the Kickstart bundle displayed in ZENworks Control Center. The folder must exist. You cannot specify a non-existent folder, because ZENworks does not create them from this wizard.
Icon: Browse for and select an icon if you plan to use one on your desktop for this bundle.
Description: Provide a description to help you later recognize the exact purpose of this Kickstart bundle.
Clickto display the Set AutoInstall Attributes page.
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:
Before configuring the Preboot environment, 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.
Configure the following Preboot environment:
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.
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. If the configuration file has system variables, you must choose theoption to import and upload the file to the Primary Server whose ZENworks Control Center you are using as the variables are automatically resolved while applying the bundle on the managed devices.
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 areand .
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:
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.
Click to display the Upload File dialog box.
Click .cfg).to browse for and select the Kickstart configuration file (
If the imported XML file has ZENworks system variables defined, the variables are resolved when the bundle is applied to the device.
When you are prompted to upload the file to the Primary Server whose ZENworks Control Center you are using, click.
Thefield displays the upload status.
(Optional) Modify the configuration file content:
The content of the configuration file is displayed in the Edit Kickstart File dialog box.
Edit the script content, then click.
You can also specify ZENworks system variables in the script. For more information, see Section 3.10.2, Managing Bundle Variables.
Clickto display the Summary page.
Do the following:
If you want to perform other configuration tasks after the bundle has been created, select thecheck box.
For example, you can make assignments to the bundle in thetab, add actions in the tab, and so on.
If you want to deploy the bundle as a sandbox version, select thecheck box. A sandbox version of a bundle enables you to test it on your device before actually deploying it.
Review the configuration, then click one of the following:
Back: Allows you to make changes after reviewing the summary.
Finish: Creates the Kickstart bundle as configured per the settings listed on this Summary page.