HP Insight Control 7.3 Update 1 Release Notes

Suggested action
This message is benign and can be safely ignored.
BL460c Gen8 server fails to boot from SAN
When running the ProLiant HW — System ROM Enable Boot from SAN on Blade server OSBP on
a BL460c Gen8 target server, the local array controller is not disabled, and the SAN controller is
not set as the first boot controller within the BIOS. Despite this, the OS Build Plan completes
successfully and no error is displayed to the user.
Suggested action 1
Update to System ROM firmware to version 9/18/2013 or newer.
Suggested action 2
Disable the local Smart Array controller manually through RBSU and set the SAN controller as the
first boot controller within the BIOS.
UEFI Optimized Mode restrictions
Some operating systems, such as Windows 2008 R2 do not install in UEFI (Unified Extensible
Firmware Interface) mode if optimized is enabled.
Suggested action
See the support matrix for full OS support.
File path name length limitations when importing a VM appliance
There are file path name length limitations when importing a VM appliance from the distribution
zip files for both Hyper-V and VMware.
For Hyper-V, the size of the path is limited to 196 characters. The path of the file as it gets unzipped
is already 179 characters, so that leaves only 17 characters for the rest of the path name, including
the device letter and any user-defined directory name the file is unzipped to. If the name is too
long, you see an error message stating Hyper-V did not find the virtual machines
to import from location ....
Suggested action
If the total path length is too long, you must move or rename the user-defined directory to a shorter
name for the total path length to be below the limit. For VMware, the fully qualified file name must
be less than 260 characters, and the directory name must be less than 248 characters. This leaves
more space for additional path components than in the Hyper-V case, but it is still possible to hit
the limit. VMware displays a informative message that clearly explains the problem.
Major issues
ProLiant SW – Offline Firmware Update Build Plan issues and restrictions
When run on a server that has been PXE-booted into the Linux service OS, the ProLiant SW –
Offline Firmware Update Build Plan may incorrectly report some components as being up-to-date,
even though newer firmware for those components is available. The Build Plan completes
successfully, giving the impression that all the firmware is up-to-date, when it may not be. The
issue has existed for all versions of Insight Control server provisioning since 7.2.
Suggested action
The ProLiant SW – Offline Firmware Update Build Plan is modified so that it only runs in the
Intelligent Provisioning service OS of a Gen8 or newer server. When run in a PXE service OS, this
Issues and suggested actions 19