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

Linux and ESXi kickstart and autoyast answer files use encrypted_root_password custom attribute instead of the

root_password custom attribute

The old root_password custom attribute was replaced with encrypted_root_password in all of the default Linux and ESXi

configuration files to help reduce confusion and make it clear to users that the password being provided is expected to

be encrypted. Underlying functionality has not changed as the root password was always encrypted in previous versions.

This is an optional change for your old build plans.

Set Media Source parameter changed from /mnt/ms to /mnt/media in some build plans

In build plans that mount the media server from a Linux OS, the mount point when using Set Media Source is now set to

/mnt/media. Scripts that use this mount point have been updated to recognize /mnt/ms or /mnt/media. Since this is a

parameter defined for each OSBP, it is not necessary update customizable OSBPs.

All Windows image OS build plans - Uninstall HP Agents and Utilities replaced with Uninstall HP ProLiant Utilities

Since the Uninstall HP Agents and Utilities script did not uninstall agent information, the script name was changed to

Uninstall HP ProLiant Utilities to more accurately reflect that only HP utilities are being uninstalled. This script is used

within the Windows Image capture OS Build Plans. Updating customized OS Build Plans is not necessary.

Windows SPP Build Plans – New scripts used to install the SPP and collect results

In build plans that install the Windows SPP, the Install Windows SPP script was replaced by the following three steps;

Install Windows SPP In Background, Wait for HP SA Agent, and Report Windows SPP Installation Results. See the

descriptions of these scripts in the reference section above for complete details.

Also note that HP SUM is now copied from the media server to the target server before executing so that a network

interruption will not interfere with the execution.

New Changes for IC server provisioning Release 7.2.2

Custom Attribute added for several ProLiant HW build plans

A new custom attribute, configuration_location was added to the following ProLiant HW build plans:

 ProLiant HW - iLO Capture Configuration

 ProLiant HW - Smart Array Capture Settings

 ProLiant HW - System ROM Capture Settings

This custom attribute is the absolute filename where the captured configuration file is to be stored and it will contain a

default value. The value is considered to be a temporary location where the file will reside until it is consumed by a later

step in the build plan. Adding this custom attribute to any existing build plans is not required unless specific control is

necessary where these temporary files are stored.

Script step added to ESXi build plans for network gateway validation

A new build plan script step was added to the beginning of all ESXi scripted installation build plans. This Validate

Gateway Setting for Static Network Configuration script build plan step verifies that a gateway was specified if static

networking information is provided for the target server. Unlike most other operating systems, ESXi requires that a

gateway be specified when configuring static IP information during an installation. The only purpose of this script is to

do error checking and fail the build plan before the ESXi installation is started. Adding this step to existing ESXi build

plans is recommended as an extra safety check, but is not required.

New ProLiant Driver package naming to include SPP version

For all Windows and Linux scripted install build plans, the ProLiant drivers packages have been named to include the SPP

version with format as ProLiant Drivers for xxxx – yyyy where xxxx is the operating system name and version and yyyy is

the SPP version. This new naming convention will allow storage of multiple SPP versions of the ProLiant driver packages

on the appliance. After an upgrade, all HP-provided build plans will use the latest versions of the driver packages. Any

customized build plans will continue to use older versions of the driver packages. To use the latest driver packages for

customized build plans, a build plan modification will be required to replace the older ProLiant drivers package build plan

step with these new ones.