Windows Server 2008 R2 and Windows Server 2008 R2 with Service Pack 1 on HP Integrity Servers Release Notes v7.1

Crash Dump
No visual status indication when creating a crash dump
Issue When a crash dump is automatically created after a Windows blue screen, there
is no visual indication such as the percentage complete status. The system might
appear to be hung.
Servers HP Integrity BL8x0 i2 server blade
Workaround Do not reset the system manually. To get a successful crash dump, you must wait
for the system to reboot automatically after completing the dump. For a kernel
dump, this might take 10 minutes or less. For a full memory dump, this might take
up to 1 hour.
Event Log
Corrected hardware errors
Issue Integrity Servers running Windows Server 2008 R2 might receive Windows Event
Log messages describing Corrected Hardware Errors for memory and processor
components. These messages from the Microsoft WHEA-LOGGER service can
occur several times daily on large memory configurations running under high
load.
Servers All Integrity
Workaround These event log messages do not indicate a problem. The underlying hardware
is operating correctly.
Extensible Firmware Interface (EFI) and EFI-based Setup Utility (EBSU)
I/O card firmware values display as unknown
Issue The EBSU Maintain Firmware feature displays some I/O card firmware values
as unknown in the Local version column. This occurs when the card firmware
does not return a data structure that EBSU recognizes because the card firmware
is configured for 32-bit systems, it lacks an EFI driver, or has corrupted firmware.
Servers All Integrity
Workaround Flash the card firmware to correct the problem. If the card still has unknown values
after flashing it and resetting the system, contact your local support specialist or
visit http://www.hp.com/support/itaniumservers for help.
Windows does not start on Reboot after restoring system image
Issue Occasionally, if you use EBSU before restoring the system image to a Fibre
Channel boot controller or if only restoring the system image to a Fibre Channel
boot controller, the system does not boot to Windows and might do either of the
following:
• Stop at the EFI prompt
• Restart WinPe, if the reinstall DVD is still inserted
This occurs because the Windows boot entry is missing from the boot menu.
Servers HP Integrity BL8x0 i2 server blades
Workaround To create the missing entry, enter the following command at the EFI prompt:
EFI_drive_letter:\EFI\Microsoft\Boot\bootmgfw.efi
Where EFI_drive_letter: is the mapping of the drive corresponding to the
EFI System Partition (for example: fs:). The boot process then continues normally.
The bootmgfw command automatically creates the Windows boot entry.
20 Release 7.1 Overview