HP Insight Control Server Provisioning 7.
© Copyright 2012-2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Table of contents Summary 10 OS Build Plans ProLiant Hardware ProLiant Operating System ProLiant Software ProLiant Combination 10 10 10 10 10 OS Build Plan Steps Run Script OGFS Python Unix Windows BAT Windows VBScript Powershell Deploy Package Deploy Configuration File Capture Configuration File 11 11 11 11 11 11 11 11 11 11 12 Working with OS Build Plans Modifying Configuration Files Adding Scripts Modifying Build Plan Step Parameters Combining Build Plans 12 12 12 13 13 Detailed Breakdow
ProLiant COMBO - BFS + Windows 2012 R2 + SPP ProLiant COMBO - BFS + RHEL6.
ProLiant OS - Windows 2012 Standard x64 Image Install ProLiant OS - Windows 2012 R2 Standard x64 Image Install ProLiant OS - Windows 2008 SP2 Standard x64 Scripted Install ProLiant OS - Windows 2008 R2 SP1 Standard x64 Scripted Install ProLiant OS - Windows 2012 Standard x64 Scripted Install ProLiant OS - Windows 2012 R2 Standard x64 Scripted Install ProLiant SW - Install Linux SPP ProLiant SW - Install Windows SPP ProLiant SW – Intelligent Provisioning Firmware Update ProLiant SW - Offline Firmware Update
Inject Kickstart Personalization Settings for ESXi 5 Inject Multi-NIC Kickstart Personalization Settings Inject Multi-NIC Personalization Settings Inject Multi-NIC Required ESXi 5 Kickstart Settings Inject Personalization Settings Inject Required AutoYaST Settings Inject Required ESXi 5 Kickstart Settings Inject Required Kickstart Settings Inject Required Unattend.
Update Intelligent Provisioning Firmware Validate Custom Attributes Validate Gateway Setting for Static Network Configuration Validate ImageX Package Contents Validate WinPE Version Verify Supported Boot Modes Verify server has iLO4 or newer Wait for ESXi installation Wait for HP SA Agent Windows Image Capture Configuration Files Summary Configure Windows Partitioning Scheme for Legacy Configure Windows Partitioning Scheme for Uefi ESXi 5.0 U1 Kickstart ESXi 5.0 U2 Kickstart ESXi 5.0 U3 Kickstart ESXi 5.
Windows 2008 R2 SP1 Web Server x64 en_us Unattend Windows 2012 DataCenter x64 en_us Unattend Windows 2012 Standard x64 en_us Unattend Windows 2012 R2 DataCenter x64 en_us Unattend Windows 2012 R2 Standard x64 en_us Unattend Packages Summary ESXi Installation Utilities GRub Boot Loader x86 Hponcfg for Windows x64 with One Time PXE Boot ImageX LinuxPE add-on packages LinuxPE HBA add-on packages ProLiant Drivers for RHEL 5.9 x64 - yyyy.mm.x ProLiant Drivers for RHEL 5.10 x64 - yyyy.mm.
Script step added to ESXi build plans for network gateway validation New ProLiant Driver package naming to include SPP version Windows build plans contain comment information regarding disk partitioning in the unattend answer files Linux build plans have firewall disabled in default kickstart or autoyast answer files Modifications to the Erase Server Disk build plan For more information 72 72 73 73 73 73
Summary Insight Control (IC) server provisioning provides OS Build Plans, scripts, packages, and configuration files that are used to deploy operating systems, configure hardware, and update firmware. OS build plans are the way tasks get done in IC server provisioning. These are the items you actually run to cause actions like installing a server or updating firmware to happen.
OS Build Plan Steps Build plans are made up of a series of build plan steps that execute in order to perform the actions. Four types of steps are available: Run Script, Deploy Package, Deploy Configuration File, and Capture Configuration File. Run Script 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.
Capture Configuration File This step allows you to capture a 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 step is typically used to capture the configuration of a hardware component, so that the same configuration can be applied to other servers. Use caution with this step as you can easily create a large number of configuration files if you run a build plan against many servers.
Modifying Build Plan Step Parameters Some build plan steps are controlled by the parameters associated with that step. You may wish to change these parameters to better suit your needs. For most of the HP-provided scripts, a summary of parameters for that script are listed in the script’s description field. Combining Build Plans Combining multiple build plans into one build plan may be desired if a series of build plans are frequently run in the same order.
WinPath@#z 8 9 10 11 12 13 14 15 16 17 18 19 Prepare Disks on HP ProLiant Gen8 OGFS Configure Windows Partitioning Scheme for Legacy Deploy configuration file x:\Windows\Temp\diskpart_legacy.txt Configure Windows Partitioning Scheme for Uefi Deploy configuration file x:\Windows\Temp\diskpart_uefi.txt Partition Disk for Windows Python --systemDiskNumber=@SystemDiskNumber:0@ Windows 2012 Standard x64 en_us Unattend Deploy configuration file x:\Windows\Temp\Unattend.
Verify Supported Boot Modes – This step 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 as a script parameter. The parameter --secure=disabled means this build plan can only be run on a server with UEFI secure boot disabled. See the reference section below for the other available boot modes.
Prepare Disks on HP ProLiant Gen8 – HP ProLiant Gen8 and newer servers have multiple embedded flash drives that are part of the new advanced features of these platforms. Some OS installation programs can see these flash drives and incorrectly try to install the operating system to them causing the installation to fail. This step does some work to help the OS installation program identify these drives and not install to them.
Step Number 1 2 3 4 5 6 7 8 9 10 Step Name Step Parameters Validate Custom Attributes 13 14 15 16 17 OGFS --custAttrNames "WimFileName" Check iLO Service OGFS Verify Supported Boot Modes OGFS --secure=disabled Unmap Network Drive Python --driveLetter=Z Set Media Source Python @__OPSW-Media-WinUser@@__OPSW-Media-WinPassword@@__OPSW-Media-WinPath@#z Prevent WIM File Overwrite Windows .
19 20 Unmap Network Drive --driveLetter=Z Set Media Source Python @__OPSW-Media-WinUser@@__OPSW-Media-WinPassword@@__OPSW-Media-WinPath@#z ImageX Configuration - Exclusion List Deploy configuration File x:\wimscript.ini Windows Image Capture 21 Python Python --wimFilePath="Z:\Images\@WimFileName@" --systemDiskNumber=@SystemDiskNumber:0@ Important: On a new appliance, the ImageX zip package used in build plan steps 6 and 14 contains a dummy file and does not contain the imagex.exe utility.
Steps 11 through 13 – Boot the server for capture The next set of steps is used to boot the target server into WinPE for the purpose of capturing the image. Boot – Reboots the target server into WinPE. Decommission Server – Turns off the agent management connection as described in Table 1. Wait for HP SA Agent – Waits for WinPE to boot and the SA agent to be available.
6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Wait for HP SA Agent OGFS --maintenance --atLeast=3 --atMost=20 Prepare Disks on HP ProLiant Gen8 OGFS Configure Windows Partitioning Scheme for Legacy Deploy configuration file x:\Windows\Temp\diskpart_legacy.txt Configure Windows Partitioning Scheme for Uefi Deploy configuration file x:\Windows\Temp\diskpart_uefi.
Steps 4 to 6 – Boot the server for provisioning The next set of steps are used to boot the server into the required service OS and reset the status of the server such that it can be provisioned. Refer to Table 1 – ProLiant OS – Windows 2012 Standard x64 Scripted Install build plan sample and the detailed descriptions in the Steps 4 to 6 – Boot the server for provisioning section for that table.
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 22 Wait for HP SA Agent OGFS --maintenance --atLeast=3 --atMost=20 Set Media Source Python @__OPSW-Media-LinURI@/rhel63-x64 RHEL 6.3 x64 en_us Kickstart Deploy configuration file /tmp/user.ks.cfg Inject Required Kickstart Settings OGFS Red Hat Enterprise Linux Server 6 X86_64 Inject Kickstart Personalization Settings OGFS Create Stub Partition Unix Copy Boot Media Unix ProLiant Drivers for RHEL 6.
--production --atLeast=3 --atMost=30 Steps 1 and 2 – Early error detection The first two steps help catch errors that might affect the running of the build plan later on. Refer to Table 1 – ProLiant OS – Windows 2012 Standard x64 Scripted Install build plan sample and the detailed description in the Steps 1 to 3 – Early error detection section.
Steps 17 to 22 – Perform the installation and post-install tasks These final steps actually perform the OS installation, add the production agent, and perform the final reboot of the server. Reboot – Reboots the target server for the purpose of booting the RHEL6.3 grub image and begin the Red Hat installation. Wait for HP SA Agent – This is the same step as before, but this time it is waiting for the agent that was deployed in build plan step 13 to register with the appliance.
10 11 12 13 Inject Kickstart Personalization Settings for ESXi 5 OGFS Create Stub Partition Unix Copy Boot Media Unix ESXi Installation Utilities Deploy package Deploy Agent Unix 14 -d /tmp/opt/opsware/agent/ogfs-agent.zip –p “Red Hat Enterprise Linux Server 5 X86_64” -u Add ESXi Module 15 16 17 18 19 Unix -s /opt/hpsa_agent –d Add ESXi Module Unix -s /tmp/user.ks.cfg –a ks.
ESXi 5.1 Kickstart – This is a deploy configuration file step. It writes the HP-provided kickstart file to the target server’s ram drive. It is recommended to replace this step with a customized kickstart file using the HPprovided configuration files as a template since these template files contain the Custom Attribute syntax. The path specified by the parameter is where the file is written.
--maintenance --atLeast=3 --atMost=20 5 6 7 8 9 10 LinuxPE add-on packages Deploy package ProLiant Scripting Toolkit for Linux x64 Deploy package System ROM Configuration – Enable Boot from SAN Deploy configuration file /tmp/sstk/conrep-bfs.xml Manage System Configuration Unix -l /tmp/sstk/conrep-bfs.
Sample Build Plan: ProLiant Software Install Table 7 – ProLiant SW – Offline Firmware Update build plan sample Step Number 1 2 3 4 Step Name Step Type Step Parameters Check iLO Service OGFS Verify Supported Boot Modes OGFS --secure=disabled Boot OGFS --serviceOS=linux64 Wait for HP SA Agent --maintenance --atLeast=3 --atMost=20 Set Media Source 5 6 7 8 9 OGFS Python @__OPSW-Media-WinUser@@__OPSW-Media-WinPassword@@__OPSW-MediaWinPath@#/mnt/media?noserverino LinuxPE add-on packages Deplo
where username:password are the credentials for the media server, and mount_point is the share that will be mounted. Optionally, all three custom attributes can be replaced with customized values as long as it conforms to URI specification above. Note that the noserverino option is neccessary when mounting a Windows share using the Linux service OS Samba client.
/tmp/sstk/conrep-bfs.xml 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 30 Manage System Configuration Unix -l /tmp/sstk/conrep-bfs.
@__OPSW-Media-WinUser@@__OPSW-Media-WinPassword@@__OPSW-Media-WinPath@#z 28 29 30 31 32 Install Windows SPP In Background Python --spp_version=@SPPversion:latest@ Wait for HP SA Agent OGFS --production --atLeast=2 --atMost=60 Report Windows SPP Installation Results Python Reboot OGFS Wait for HP SA Agent OGFS --production --atLeast=3 --atMost=30 How these build plans were combined This COMBO build plan gives an example of how multiple individual build plans that are frequently used together
to switch to the WinPE service OS which would make the build plan run that much longer while the server was rebooted. This is strictly efficiency and could have been omitted. Step 12 – Last step of the Boot from SAN section The Wait for SA Agent build plan script step will wait for the agent in the WinPE service OS before beginning the OS installation since the previous boot step was modified to boot to WinPE.
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.
Custom Attributes: None ProLiant HW - Boot Local Disk Boots a target server into production via its local disk. NOTE: The build plan expects an agent to be running on the target when the build plan completes or the build plan will fail, even if the target boots successfully. Requirements: HP ProLiant server with iLO Custom Attributes: None ProLiant HW - Clear UEFI Boot Menu Deletes all custom boot options from the UEFI boot menu.
Custom Attributes: None ProLiant HW - iLO Capture Configuration Captures HP Integrated Lights-Out settings into a configuration file. The configuration file is stored on the target server and then uploaded to the appliance. The configuration file format is defined by the ProLiant Scripting Toolkit iLO utility. Requirements: HP ProLiant server with iLO Required Custom Attribute: configuration_location – The absolute filename of the captured configuration xml on the target server.
Requirements: HP ProLiant server with iLO and a Smart Array controller Custom Attributes: None ProLiant HW - Smart Array Set RAID 1 Sets the HP Smart Array configuration for RAID 1 using two drives. This is a sample build plan that can be modified to set any Smart Array settings. Just replace the configuration file with one that specifies the settings you want. The configuration file format is defined by the ProLiant Scripting Toolkit SSACLI scripting utility.
This is a sample build plan that can be modified to set any System ROM settings on any ProLiant server. Just replace the configuration file with one that specifies the settings you want and that is appropriate for that particular server. In this particular case, boot from SAN is enabled by setting the fibre channel first in the boot order and disabling any embedded storage controller. Requirements: HP ProLiant BladeSystem with iLO and fibre channel controller Custom Attributes: None ProLiant OS - ESXi 5.
encrypted_root_password – root password in encrypted form. Refer to the HP Insight Control Server Provisioning online help on how to create an encrypted password.
ProLiant OS - Windows 2008 SP2 Standard x64 Image Install ProLiant OS - Windows 2008 R2 SP1 Standard x64 Image Install ProLiant OS - Windows 2012 Standard x64 Image Install ProLiant OS - Windows 2012 R2 Standard x64 Image Install Applies a previously captured Windows WIM image. This build plan is used to clone servers using an image captured from a reference server. Requirements: HP ProLiant server with iLO and similar hardware as the reference server. A previously captured WIM image on Media Server.
EncryptedAdminPassword – Administrator password in encrypted form. Refer to the HP Insight Control Server Provisioning online help on how to create an encrypted password. 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.
The target server will be booted into the Linux service OS and the SPP firmware update function will be run. Upon completion of this build plan, the target server will be left in the service OS. If you require the production OS, the build plan will need to be modified with the appropriate boot steps. Requirements: HP ProLiant server with iLO IC server provisioning Media Server must contain a SPP Optional Custom Attributes: SPPversion – SPP version in the form of yyyy.mm.x, for example 2014.02.
Parameters: -s file – a file or directory to create a module from -d – create a tar in tar image to get around VMware’s vgz format -a file – alias the file or directory Custom Attributes: None Add iLO User Adds an iLO user using the ProLiant Scripting Toolkit hponcfg utility. Type: OGFS Required Parameters: --username=USERNAME where USERNAME of the new iLO user.
OR o EncryptedDomainPassword – encrypted domain password. Refer to the HP Insight Control Server Provisioning online help on how to create an encrypted password. o Key – used to generate the value for EncryptedDomainPassword Adjust Windows System Disk Number on HP ProLiant Gen8 Adjusts the SystemDiskNumber custom attribute on Gen8 servers to account for the Virtual Install Disk.
The boot step completes as soon as the boot is initiated, and does not wait for a successful boot. For this reason, the boot step should always be followed by the Wait for SA Agent step. Sometimes the Decommission Server step can come between Boot and Wait for SA Agent. When checking the current state of the target server, the boot step cannot distinguish between a server that was booted using PXE or one booted using the embedded service OS.
unnecessarily fail if the iLO registration process is still in progress. The Check iLO Service script is added at the head of most build plans before the Boot step to verify that the target server has a valid iLO registered. If no iLO is registered, the script will wait some amount of time to allow the iLO to complete its registration. Once the iLO becomes registered, the step completes and the build plan continues. If no iLO is found before the timeout, the script fails and halts the build plan.
Ethernet 3 HP NC553i Dual Port FlexFabric 10G...#2 14 Disconnected 18-A9-05-C5-E1-B4 10 Gbps Table 10: Configure NIC Teaming for Windows sample parameters used for target server with network adapters setup as provided in Table 9.
base_path_or_img - A directory in the installation media, or a mountable image file. All other files are relative to this location. "file1" ["file2" ["file3" ...]] - list of files to copy onto the boot partition. Custom Attributes None Create Stub Partition Creates a partition on the local disk to load the Linux build image. This is one of the scripts used to prepare a server for a Linux installation. By default, the boot disk is identified as the first disk in /proc/partitions.
4. Update the ProLiant Drivers for Windows XXX OSBP step to use X:\$oem$ as the directory path parameter. This is necessary since C: partition will no longer be available with the removal of Create Windows System Drive step. NOTE: The X: (WinPE) drive is a RAM disk that only exists in memory. It is possible that the combined size of the drivers may be too large to fit in the available RAM disk space. If this occurs, please consider using Option #1 above. Type: Windows .
same name. Directories that don't exist will be created, note however that the basename will be considered as a file. Optional Parameters: -n NAME, --name=NAME The name of the file to download. -g SERVER, --gateway=SERVER Optional server to download from. If not present the agent config will be used to determine a valid gateway. Custom Attributes: None Embed files initrd Embeds a specified list of files or directories into a new initrd image.
Get Deployment Interface Details Retrieves and stores Deployment Interface Network details into the specified file. This is used with Install Windows SPP script to reset the network after a NIC firmware or driver update. Type: Python Required Parameter: absolute_filename – The absolute path to the file to write the network details.
Inject Multi-NIC Required ESXi 5 Kickstart Settings Injects required Matrix Operating Environment settings into a ESXi Kickstart answer file. The install NFS directive will be inserted with the values used at the mount NFS share step. This inject step also checks if an encrypted password was used, since such a password, cannot be used to automatically manage the hypervisor. The SSH service is also enabled and started.
o during the next reboot. post-exitpoint to write info file that the installation has finished Type: OGFS Required Parameter: HP SA Agent Name - The SA agent that needs to be started during installation. Custom Attributes: None Inject Required ESXi 5 Kickstart Settings This script injects required settings into the kickstart answer fill. This script modifies the Kickstart file and adds scripting that will allow IC server provisioning to monitor and control the operating system installation.
path_to_file - the OGFS path or absolute path on the target server to the unattend answer file. If this parameter is omitted, the script will look for an existing file at X:\Windows\Temp\Unattend.txt.
Type: Unix Optional Parameter: kernel_arguments=’value’ - a string of arguments that will be passed to the build images' kernel, for example, kernel_arguments=mpath used with Red Hat EL 5.8 for multipath support. Custom Attributes: None Install Linux SPP Install Windows SPP Installs the HP Service Pack for ProLiant (SPP) on the target server. IMPORTANT: The Install Windows SPP script is no longer used starting with IC server provisioning 7.3.1.
Set Media Source script. Since this script uses the HP SUM utility, an SPP should be used in the media server location. Copying a supplemental package to that location will fail the script since it won’t be able to find HP SUM. Type: Python Optional Parameters: --spp_version=directory_name - The name of the directory containing the SPP to be installed, such as 2013.09.0. If the value is blank or "latest", the script automatically selects the directory with the latest version as determined by sort order.
Type: Unix Required Parameters: To capture: -c output_filename To set: -i input_filename Optional Parameters: -nofail - indicates if the script should not fail if a Smart Array controller is not found. -internal - limit operation to internal controllers. Is not used with –external parameter. -external - limit operation to external controllers. Is not used with –internal parameter. -reset - removes existing data and overwrites current configuration with new configuration.
HP felt it was easier to create or extend custom partitions this way versus inside the unattend XML format. An error from diskpart may be more intuitive than trying to troubleshoot a partitioning error in setup.exe and will happen earlier in the build plan. The HP-provided OSBPs use this temporary partition to store the extracted driver files. This helps prevent running out of disk space on the WinPE RAM drive (X:).
http://technet.microsoft.com/en-us/library/cc721973 Type: Windows .BAT Optional Parameter: /unattend:path_to_answer_file – Path to the answer file that is passed to the Sysprep tool. Custom Attributes: None Prevent WIM File Overwrite Checks for the existence of the WIM image file. This ensures that an existing WIM image is not accidentally overwritten if another capture build plan is run that uses the same WIM file name.
--method='METHOD' - This parameter is not required as the target server should power off before the boot ever begins, but it can be specified without consequences. Possible values: - auto - it will behave as embedded or network, depending on the target server - embedded - supported only if the IloService is enabled on the target server and this is a HP ProLiant Gen8. The following service OSs are possible: linux, linux64, or winpe64.
“setup.exe_path_and_file” - Path and filename to the Windows setup.exe program. Parameter should include the double quotes. Custom Attributes: None Set Media Source Defines the connection from the target server to the Media Server. The Set Media Source script is where the location of the media to be used for a build plan is specified. The script will do different things depending on the protocol specified in the URI: SMB – This is the Samba/Windows file share protocol.
Send LM & NTLM - use NTLMv2 session security, if negotiated ntlm,ntlmv2,ntlmv2i Send NTLM response only ntlm Send NTLMv2 response only ntlmv2,ntlm Send NTLMv2 response only, Refuse LM ntlmv2,ntlm Send NTLMv2 response only, Refuse LM & NTLM ntlmv2 Microsoft network server: Digitally sign communications (always) ntlmv2i Microsoft network server: Digitally sign communications (if client agrees) ntlm,mtlmv2,ntlmv2i domain=name – This option is typically not needed.
Type: Python Required Parameters: --driveLetter - The letter that's associated with the network drive to be unmapped. Custom Attributes: None Unmount All Boot Disk Partitions Unmounts all the partitions belonging to the boot disk. By default, the boot disk is computed as the first hard drive listed in /proc/partitions. Type: Unix Parameters: None Optional Custom Attributes: boot_disk - The absolute path to the device file for the boot disk. For example, /dev/sda.
script step. For example, if the file share where the zipped HP SUM log file is to be copied to is mounted on /mnt/media and the destination directory is "hpsum_logs", then specify --hpsum_logs_dump_dir=/mnt/media/hpsum_logs. --no_show_log – Do not display the hpsum_log.txt contents in the job log. Custom Attributes: None Update Intelligent Provisioning Firmware Updates the Intelligent Provisioning (IP) firmware on a ProLiant Gen8 or newer target server.
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.
There are scenarios where a build plan can only be run on servers with iLO 4 or newer (one example: Intelligent Provisioning Firmware Update). This step is used in those build plans to ensure that the target server is running iLO 4 or newer. If not, it will fail early instead of unnecessarily going forward with build plan execution. Type: OGFS Parameters: -t MINUTES or --atMost=MINUTES - Wait at most MINUTES number of minutes before timing out. Default is 10 minutes.
Type: Python The parameters are specified in order, separated by spaces. Required Parameters: Full path where the WIM image file will be saved including the file name and .wim extension. Drive number to be captured Optional Parameter: Path to the optional wimscript.ini exclusion file. This file contains a list of files for ImageX to skip while imaging. The Capture Windows Image script will always add files to the exclusion list to prevent imaging the Server Automation agent files.
iLO Configuration - Set Minimum Password Length Sets the iLO Minimum Password Length with default as 8. This is a sample file used as a template for creating custom files. Refer to ProLiant Scripting Toolkit documentation for hponcfg configuration file details. Custom Attributes: None ImageX Configuration - Exclude Boot Directory Excludes the /Boot directory from the capture process using the imagex.exe /capture option.
System ROM Configuration - Enable Boot from SAN System ROM Configuration – Enable Virtualization Enables Boot from SAN on ProLiant Blade Servers or Virtualization BIOS functionality on ProLiant servers. Refer to ProLiant Scripting Toolkit documentation for conrep configuration file details.
Windows 2012 DataCenter x64 en_us Unattend Windows 2012 Standard x64 en_us Unattend Sample answer file for the specified operating system and edition. Refer to the appropriate operating system supplier for answer file details. NOTE: The HP-provided unattend files do not contain any disk partitioning information. The partitioning of the boot disk is performed in the Partition Disk for Windows OSBP step.
GRub Boot Loader x86 Contains the grub boot loader that will land on the stub partition. Even though the name contains x86, it is still used with x64 Linux deployments. Hponcfg for Windows x64 with One Time PXE Boot Contains hponcfg and support files to setup the one-time PXE boot. This package is part of the RDP migration related build plans. It puts hponcfg and support files needed to setup the onetime PXE boot on a target server running a Windows production operating system. The bundled hponcfg.
Appendix A – Changes in Build Plans for each release With each new release of Insight Control server provisioning, the HP provided build plans are updated to provide more functionality, support more platforms, be more robust, and correct defects. Any build plans you customized in a previous release may not have the latest changes, since those build plans are copies of the ones HP provided in the older release.
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.
Windows build plans contain comment information regarding disk partitioning in the unattend answer files Two commented lines have been added to all default Windows unattend answer files regarding the disk partitioning. The commented lines explain that disk partitioning is done within a script build plan step of the build plan and not within the unattend answer file. These are just comments and are not necessary for customized build plans.
