HP Insight Control Server Provisioning 7.3 Update 1 Build Plans Reference Guide
64
This script is used as a validation step to verify that the imagex utility has been properly uploaded to the appliance. It is
used so that the build plan can check for this, warn the user, and fail early in the build plan, before irreversible changes
are made to the target server. This step should always follow the deploy imagex package step.
On a new appliance, the ImageX zip package conatins a dummy file and does not contain the imagex.exe utility.
imagex.exe is one of the things that are uploaded to the appliance when you build and upload WinPE as described in the
installation guide.
This script validates that imagex.exe made it into the ImageX package and has been installed in the
SystemDrive\HPPROVTEMP directory using the Install ZIP Package - ImageX step if the target server is in the
production OS, or in X:\Windows\System32 if the target server is in WinPE service OS where SystemDrive is the
Windows production system drive letter. On the production OS, the SystemDrive\HPPROVTEMP directory is
removed after the contents of the ImageX package have been verified.
Type: Windows .BAT
Parameters: None
Custom Attributes: None
Validate WinPE Version
This script is used as a validation step to verify that the target server is booted into the correct WinPE version.
Beginning with IC server provisioning 7.3.1, WinPE 4.0 or WinPE 3.1 can be used with the product; however, Windows
2008 SP2 and Windows 2008 R2 can only be successfully installed via WinPE 3.1.
NOTE: With Intelligent Provisioning v1.60 or greater, WinPE version is 4.0.
Type: Python
Required Parameter:
--version=n where n is 3.1, 4.0, a list of versions ("3.1,4.0"), or any. The version of the booted WinPE is
checked against the parameter specified. If no option is specified, then the option defaults to 3.1.
Custom Attributes: None
Verify Supported Boot Modes
Verifies that the target server is configured in a boot mode that is supported by the build plan. The boot modes that the
build plan supports can be specified using the options listed below. For example, if the build plan installs an operating
system which does not support the UEFI boot mode, then the -uefi=false option should be specified, so that the
build plan execution is stopped before the operating system is attempted to be installed.
Multiple parameters can be used together to list all the boot mode restrictions.
Type: OGFS
Parameters:
--legacy={true|false} Specifies whether the build plan can be run on a server whose boot mode is set to
Legacy BIOS mode. Default is “true”.
--uefi={true|false} Specifies whether the build plan can be run on a server whose boot mode is set to UEFI
mode. Default is “true”.
--optimized={enabled|disabled|any} Specifies whether the build plan can only be run on a server with UEFI
optimization enabled, disabled, or any. The default is "any".
--secure={enabled|disabled|any} Specifies whether the build plan can only be run on a server with UEFI secure
boot enabled, disabled, or any. The default is "any".
Custom Attributes: None
Verify server has iLO4 or newer
Verifies that the target server has an iLO4 management processor or newer. If the target server has iLO, iLO2, iLO3, or
no iLO at all, the script will return an error.