Implementing Microsoft Windows Server 2008 on HP ProLiant servers

Appendix A: known issues and workarounds

ProLiant servers with Windows Server 2008

Table A-1 lists the known issues with ProLiant servers with Windows Server 2008.

Table A-1. Known issues on ProLiant servers (Windows Server 2008 32-bit and x64 editions)

Issue Details

Issue 1 The write cache and advanced performance drive policies do not stay on Smart Array logical

volumes.

Description If write caching and advanced performance drive policies are set in the device

manager for logical volumes on an HP Smart Array controller, these polices are not

saved when the device manager is exited.

Workaround Since write cache on a Smart Array is for the controller and not for individual logical

volumes, these polices in device manager do not have any effect. Use the Array

Configuration Utility (ACU) to set the write cache characteristics.

Issue 2 Incorrect slot numbers may be reported by certain storage applications for certain storage adapters or

NICs.

Description This issue affects certain storage applications, including storage agents, SAS/SATA

event services, and Array Configuration Utility (ACU).

Workaround Update the ROM to the minimum ROM version listed in Table 2.

Issue 3 A blue screen error may display during installation of Windows Server 2008.

Description A blue screen displaying a “BUGCODE_USB_DRIVER” error may display upon

installation of Windows Server 2008.

Workaround If this error occurs, download and install iLO 2 firmware Version 1.29 (or later).

Issue 4 Storage drivers do not get loaded during Driver Injection on Windows Server 2008 x64 edition.

Description During installation, if a driver is injected, no controllers supported by the injected driver

are listed.

Workaround There is no workaround at this time.

Issue 5 On servers booting from Internal 4/8 Port SAS Controller, upgrading from Windows Server 2003 to

Windows Server 2008 stops responding (hangs).

Description

An LSI IDE RAID driver is causing the system to hang.

Workaround

Remove lsicsb6.sys from the systems by either removing the lsicsb6.sys file

from the \windows\system32\drivers directory (and any other locations) or

removing any INF files that reference the lsicsb6 driver.