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

 SystemDrive – Drive label for the system drive the operating system is installed

 SystemDiskNumber – Physical drive number for the system drive the operating system is installed. This

custom attribute is not meant to be set by the end user. It is set automatically during build plan execution and

is used to make sure the Windows installer does not install to the Intelligent Provisioning flash drives. During

re-provisioning, this value might be left over from a previous installation and cause the install to fail. Deleting

the custom attribute before running the build plan solves this.

ProLiant COMBO - BFS + RHEL6.5 + SPP

This build plan configures ProLiant Bladeservers' System ROM to enable Boot from SAN functionality (BFS), performs a

scripted install of Red Hat Enterprise Linux 6.5 x64 using a generic kickstart file, and installs the Service Pack for

ProLiant (SPP) on the Linux operating system.

Requirements:

 HP ProLiant Bladeserver with iLO and fibre channel controller

 IC server provisioning Media Server must contain the OS distribution

 IC server provisioning Media Server must contain a SPP

Required Custom Attributes: None

Optional Custom Attributes:

 encrypted_root_password – root password in encrypted form

 boot_disk

 kernel_arguments

ProLiant HW - Add Migrated Linux Server

ProLiant HW - Add Migrated Windows Server

Automatically registers an RDP migrated server’s iLO by temporarily rebooting the server into maintenance.

NOTE: These two build plans are designed to work only with target servers that were migrated to this appliance from

RDP. They make use of software that is installed as part of an RDP installation.

NOTE: These build plans will reboot the running target server into maintenance.

When a target server is initially migrated to IC server provisioning from RDP, the iLO from that server is still unknown to

the appliance. Since the iLO is required for most build plans, the iLO must be registered before other build plans can be

run. This can be done manually, or automatically by using these build plans.

Add Migrated Linux Server uses the /sbin/hpbootcfg utility to set the one-time PXE boot to a service OS and is run on

Linux-based targets. Add Migrated Windows Server uses the ProLiant Scripting Toolkit hponcfg utility to set the one-

time PXE boot to a service OS and is run on Windows-based targets. The target server will be booted into the LinuxPE

environment where the server's iLO will be registered and then booted back into production.

Requirements:

 Runs only on ProLiant Servers with iLO that were migrated from an RDP server.

 Appliance must have DHCP/PXE support.

 Presence of /sbin/hpbootcfg for Linux-based servers.

Custom Attributes: None

ProLiant HW - Boot Linux Service OS

ProLiant HW - Boot WinPE Service OS

Boots the target server into the appropriate service OS, maintenance mode, per the build plan title.

These are the build plans used when adding a server via its iLO and booting to maintenance.

Requirements: HP ProLiant server with iLO