HP Integrity Servers with Microsoft Windows Server 2003 Release Notes v6.2

Installation from graphics console might require additional steps
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.
Servers rx6600, rx3600
Workaround For more information on editing boot entries, see the Smart Setup Guide.
Component time outs cause installation failure
Issue If a Smart Component takes longer than 15 minutes to install, the installation
of the Support Pack most likely fails. This normally occurs in cases where the
system has many cards, such as numerous NIC cards, installed.
Servers All Integrity
Workaround Install the Smart Component separately, and then install the Support Pack.
Screen is blank at system startup
Issue During system startup the screen may remain blank for 3 to 8 minutes (actual
time depends on the quantity of the installed system memory).
Servers All Integrity
Workaround This is normal. The system activity can be monitored within a few seconds of
system power-on using a remote terminal.
Maximum Payload Size parameter must be off
Issue HP Integrity servers based on the HP ZX2 chipset using PCI Express backplanes
enable you to control a feature called Maximum Payload Size (MPS). This feature
must be off for Windows Server 2003, and is delivered off on factory-installed
system. If the server is ever used with another operating system, ensure that
the MPS setting is off before installing Windows Server 2003.
Servers rx6600, rx3600, rx2660, HP Integrity BL860c Server Blade, HP Integrity BL870c
Server Blade
Workaround
Use the ioconfig in EFI to view and configure this value. To view the value,
enter:
shell>ioconfig
To turn the value off (required on Windows Server 2003), enter:
shell>shell> ioconfig mps_optimize off
To turn the value on, enter:
shell>shell> ioconfig mps_optimize on
Use Esc+8 instead of F8 key on headless server
Issue The Telnet and Hyperterminal applications on Windows NT4 and Windows
2000 do not correctly map the ASCII string for the function keys. For example,
during Power On Self Test (POST) the Smart Array firmware displays a banner
and configuration menu with instructions to press the Esc key to continue or
the F8 key to enter the configuration utility. When running the system in a
headless configuration, pressing F8 does not display the configuration menu.
Servers All Integrity
Workaround To transmit the correct ASCII string using these applications from a remote
terminal, press the Esc key immediately followed (within 1 second) by the
numeric value of the desired function key. For example, to send the ASCII string
Troubleshooting Common Issues 25