HP Insight Control Server Provisioning 7.2 Online Help

Table Of Contents
ProLiant HW System ROM Configuration Apply Captured Settings
ProLiant HW - Smart Array Configuration Set RAID 5
ProLiant HW - Smart Array Configuration Capture Settings
ProLiant HW - Smart Array Configuration Apply Captured Settings
ProLiant HW - iLO Configuration Capture Settings
ProLiant HW - iLO Configuration Apply Captured Settings
5.1.4 Make sure firmware and driver levels agree
HP designs its firmware, drivers, and agents to work together at specific revision levels. Insight
Control server provisioning service OS’s and driver insertion packages for the OS Build Plans
contain the latest SPP version; see the HP Insight Management Support Matrix at http://
www.hp.com/go/insightmanagement/docs for details. For best results, you should keep your
system firmware at this same revision. Failure to do so might cause deployment problems. See
“Deploy a Support Pack for ProLiant (SPP)” (page 28) for instructions.
5.1.5 Make sure you have HP ESXi distros
Installing VMware ESXi to target servers requires HP-supplied VMware ESXi distribution files that
include the appropriate ProLiant drivers and certain firmware recipes. For information, see http://
vibsdepot.hp.com/hpq/recipes/. You might need to update firmware to a minimum version in
order to deploy VMware ESXi to a target server.
5.1.6 On SAN, present only OS system disk when installing an OS
Before running an OS Build Plan on a SAN, make sure you only present the LUN for the system
disk where the OS is to be installed. Once the OS is installed, the LUN for the other disks may be
presented.
5.2 Capturing and installing images
Insight Control server provisioning provides Build Plans to create captured images and perform
image installations.
5.2.1 Requirements
The following requirements must be met for image capture and install Build Plans.
Images are in Windows Imaging Format (WIM) and can only be captured from servers running
a version of Windows supported by IC server provisioning. See the HP Insight Management
Support Matrix at http://www.hp.com/go/insightmanagement/docs for details.
When capturing an image, the target server must be booted up and running a production
OS.
You must have an Images folder on your Media Server directly under the top level folder of
your file share. If you used the HP Insight Control server provisioning Media Server setup utility
to set up your Media Server, the folder was created for you.
You must have WinPE uploaded to your appliance. The WinPE image contains imagex.exe,
which is required for capturing and installing WIM images. This is true even if you do not PXE
boot your servers. See the HP Insight Control Server Provisioning Installation Guide, available
at http://www.hp.com/go/insightcontrol/docs, for information on generating and uploading
WinPE to the appliance.
The custom attribute WimFileName must be defined. This custom attribute specifies the file
name for the WIM image you are creating or installing. Images will always be located in the
Images folder on your Media Server unless you modify the parameters to the Capture
Windows Image and Apply WIM Image Build Plan steps to use another folder.
50 OS Build Plans