HP Insight Control Server Provisioning 7.3 Update 1 Administrator Guide

• “Capture configuration files step” (page 36)
Run script step
The run script step is the key component of the product, and represents the vast majority of steps
used in Build Plans. This step type causes a script to be executed, either on the target server or on
the appliance. IC server provisioning comes with an extensive library of scripts that perform many
of the most common tasks you will need when creating Build Plans. In addition, you can create
your own scripts based on the ones HP provides or entirely from scratch.
IC server provisioning supports the following script types:
• OGFS scripts control the HP Server Automation engine that is inside the IC server provisioning
appliance. These are the only scripts that execute on the appliance. All other script types run
on the target server. Most of the OGFS scripts shipped with the appliance come from Server
Automation, are written in Python, and are not meant to be modified in any way. They provide
vital functions like booting target servers, monitoring tasks, and manipulating data. HP does
not recommend creating OGFS scripts unless you have advanced knowledge of Server
Automation.
• Python scripts execute on the target server. This is the only script type that can be run on either
Windows or Linux systems.
• Standard Unix/Linux shell scripts that execute on the target server.
• Standard Windows batch scripts that execute on the target server.
• Standard Windows Visual Basic scripts that execute on the target server.
• IC server provisioning does not currently support PowerShell as a script type. However, a
Windows batch script can be created that performs the following:
◦ dynamically generates the PowerShell script and then runs the script on the target server
◦ pipes the PowerShell content into the PowerShell interpreter to run it
◦ or copies a PowerShell script from the Media Server to the target server and then runs it.
Deploy package step
IC server provisioning packages are ZIP files that are stored on the appliance. When the deploy
package step is used, the zip file is transferred to the target server and uncompressed into the
specified location. Pre-installation and post-installation scripts may also be specified with the
package and will execute before or after the package is saved to the target server and the files
extracted. All the packages on your appliance are provided by HP. They are typically things like
driver bundles and software libraries needed for installing on ProLiant servers. At this time, there
is no option to allow you to upload your own packages or save and modify copies on the appliance,
although that functionality is planned for a future IC server provisioning release.
Deploy configuration file step
Configuration text files are stored on the appliance that are used for text-based data such as
unattended installation files or hardware configuration files. The deploy configuration file step
takes the specified configuration file and writes it to a user-specified location on the target server.
These steps are often followed by a run script step that makes use of the configuration file. HP
provides many sample configurations. You can use these configurations or create your own.
Capture configuration files step
You can also capture a configuration 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 process
is typically used to capture the configuration of a hardware component, so that the same
36 Using OS Build Plans