HP Insight Control Server Provisioning 7.3 Update 1 Build Plans Reference Guide

12
Capture Configuration File
This step allows you to capture a text file from the target server and upload it to your appliance database so that it can
later be used as part of a deploy configuration file step. This capture step is typically used to capture the configuration
of a hardware component, so that the same 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 which gives you 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. It is expected that you will create your own build plans
based on the examples we have provided.
Here is a very common customization example of how to modify a build plan to use a new configuration file:
1. Open the HP-provided configuration file to be modified and make a copy using Actions > Save as.
2. Modify the new configuration file.
3. Open the HP-provided build plan to be modified with the new configuration file and make a copy using Actions
> Save as.
4. Edit the newly copied build plan.
a. In the Steps section of the edit page, 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. Click the drop down and select Select Another and then the newly modified configuration file created
in Step 2.
c. The parameters from the original configuration file will remain, although they can be edited if
necessary.
d. Click OK to save the step change.
e. Click OK to save the new build plan.
It is important to understand that 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 a lot of changes. Most of the steps in the sample build plans are required,
because they do 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. The detailed build plan descriptions in later
sections will give indications as to which steps commonly need to be changed.
Modifying Configuration Files
The default 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 HP sample configuration file with a customized configuration file.
Adding Scripts
Another common modification is to perform additional tasks on the target server after it has been installed. You can do
this by creating scripts, and then adding those scripts to the end of the build plan after the operating system installation
is complete.