HP Insight Control Server Provisioning 7.3 Update 1 Administrator Guide

configuration can be applied to other servers. Use caution with this step as you can easily create
a large number of configuration files if you run a Build Plan against many servers.
Working with OS Build Plans
All of the HP-provided Build Plans and Build Plan steps are read only to ensure a consistent and
reliable source for working samples. Although most of the HP-provided Build Plans will work without
modification, it is highly unlikely the HP-provided Build Plans will exactly meet your requirements.
You will most likely need to create your own Build Plans based on the provided examples.
NOTE: See the online help section on OS Build Plans for best practices for OS Build Plans, how
to use the UI to create, edit, run, monitor, delete and combine OS Build Plans and also find out
more about how to customize OS Build Plans for specific situations.
Since the HP-provided Build Plans and steps are read only, to create your own Build Plans you will
need to make a copy and edit it.
The following provides an example of how to modify a Build Plan to use a new configuration file:
1. In the Configuration Files screen, open the HP-provided configuration file to be modified and
make a copy using Actions→Save as.
2. Modify the new configuration file.
3. In the OS Build Plans screen, open the HP-provided Build Plan to be modified to use the new
configuration file and make a copy using Actions→Save as.
4. To edit the newly copied Build Plan:
a. In the Steps section of the OS Build Plans Edit screen, find the HP sample configuration
file to be replaced and select the Edit icon for that step. This will open the edit screen for
that step.
b. If there are parameters associated with this step, select them and copy them to the paste
buffer, since they will clear when the new step is selected.
c. Click the drop down and select the newly modified configuration file created in Step 2.
d. If there were parameters with this Build Plan step, paste them back into the text box.
e. Click OK to save the step change.
f. Click OK to save the new Build Plan.
The steps listed in a Build Plan are references or links. That means that if the contents of a script
or a configuration file are modified, every Build Plan that uses that step will change with that
modification. However, the parameters that are specified for that Build Plan step are stored with
the Build Plan and can be changed without affecting the other Build Plans.
Modifying a Build Plan should not require many changes. Most of the steps in the sample Build
Plans are required, since they perform actions such as boot the server, setup the installation and
install agents.
The following sections cover some of the most common types of changes that you may need to
make.
• “Modifying configuration files” (page 37)
• “Adding scripts” (page 38)
• “Modifying Build Plan step parameters” (page 38)
• “Combining Build Plans” (page 38)
Modifying configuration files
The HP-Provided Build Plans come with sample configuration files. These might be sample unattended
files for installing Windows, kickstart or autoyast files for installing Linux, or hardware configuration
files for configuring a system option. Additionally, sample configuration files are provided for each
supported Windows edition. By far, the most common modification will be to replace the
Working with OS Build Plans 37