Windows Integrity Enterprise Edition Release Notes

Release Notes
Troubleshooting common issues
HP Integrity Servers with Microsoft® Windows® Server 2003, Enterprise Edition
27
Issue The LPutil64 Delete button does not work with the A7298A, AB232A, AB466A,
or the AB467A adapters.
Workaround Disable the desired EFI driver using LPutil64's Enable/Disable button instead.
Another solution is to simply flash to a newer version of the EFI driver, which
will overwrite the existing version.
Superdome,
rx8640, rx8620,
rx7640, rx7620
Combining legacy Fibre Channel HBAs with newer 4 Gb Fibre Channel HBAs
(AD167A/AD168A) requires an upgrade to EFI driver v3.11a4 for all adapters in the
system
Issue The driver for the newer 4 Gb Fibre Channel host bus adapters is incompatible
with the driver for the older Fibre Channel adapters. This incompatibility
interferes with the flashing and normal operation of all adapters in a mixed
system.
Workaround You must upgrade all host bus adapters in the system to EFI driver version 3.11a4.
Hard Disk Configuration
all Integrity
servers
Boot LUN (logical unit number) configurations made using EBSU Express Install do
not appear after reboot.
Issue When configuring a boot LUN in EBSU Express Install using a direct connect
configuration to an MSA1000, the storage hard disk device configuration may be
lost after rebooting the system.
Workaround The Emulex FC EFI driver (minimum rev. 3.11a4) has a Device Discovery delay
function. Change the Delay Device Discovery parameter located at: >Setup
Utility >Configure Boot Parameters menu to 30.
Installation
rx6600, rx3600 Installing Windows Server 2003 from a graphics console may require either
disconnecting the console or editing the boot entry.
Issue When using vKVM to install Windows Server 2003 on rx3600 or rx6600 with a
graphics console attached, you must either disconnect the graphics console or edit
the boot entry to add the /NOVESA option.
Workaround See the Windows Integrity Smart Setup Guide for more details on editing boot
entries.
all Integrity
servers
When using the Smart Setup to install, a warning that the PAL_HALT_LIGHT
component can not install appears on the monitor.
Issue The PAL_HALT_LIGHT registry entry is meant for installation only on a
Dual Core Intel® Itanium® 2 processor. If your system does not use this
processor, please ignore the Smart Component install warning.
Workaround If your system has a Dual Core Intel® Itanium® 2 processor the
PAL_HALT_LIGHT registry entry should install without any notification. To
attempt a manual install of this entry:
1. Double-click the Smart Component