Implementing Microsoft Windows Server 2003 On Proliant Servers
Implementing Microsoft Windows Server 2003 On Proliant Servers
Standard Servers
1
Implementing Microsoft Windows Server 2003 on ProLiant servers
Abstract This integration note describes the level of support available for Microsoft Windows Server 2003:
This paper describes the level of support available for Microsoft Windows Web Server, Standard
Server, and Enterprise Server editions of the Windows Server 2003 family. It does not describe support
for Itanium® 2-based systems.
Additionally, the focus of this document does not include performing upgrades to Windows Server
2003. For information of this nature, refer to the integration note titled upgrading to Microsoft Windows
Server 2003 on ProLiant servers. This document and others pertaining to Windows Server 2003 can be
found on the HP Windows Server 2003 website at
http://h18001.www1.hp.com/partners/microsoft/windowsserver2003/support.html.
Symbols in The following symbols can be found in the text of this document:
text
CAUTION: Text set off in this manner indicates that failure to follow directions could
result in damage to equipment or loss of information.
IMPORTANT: Text set off in this manner presents clarifying information or specific
instructions.
Note: Text set off in this manner presents commentary, sidelights, or interesting points of information.
Introduction Windows Server 2003 is an extension of the Windows 2000 operating system (OS) environment
developed to enhance the customer experience and to improve the overall usability and deployment.
to With few exceptions, application code developed for use under Windows 2000 will work with
Windows Windows Server 2003 family of operating systems.
Server Microsoft provides Windows Server 2003 in both 32-bit and 64-bit editions. The 64-bit edition supports
2003 the Intel® Itanium® and Intel ® Itanium® 2 processors.
This paper covers the 32-bit editions of Windows Server 2003 running on ProLiant servers based on the
IA-32 architecture.
2
Implementing Microsoft Windows Server 2003 on ProLiant servers
Supported Windows Server 2003 should load and run on any ProLiant server that meets the recommended
configurations hardware configuration established by Microsoft.
Carefully review this document for the recommended system configuration and possible issues you
might encounter. Performing due diligence optimizes your resources and testing scenarios. Do not
use this paper as your sole source of information. In addition to the websites mentioned throughout
this paper, you might also want to visit the Windows Server 2003 support page at
http://h18001.www1.hp.com/partners/microsoft/windowsserver2003/support.html and the
Microsoft website at www.microsoft.com/.
Recommended Table 1 lists the recommended minimum system configuration established by Microsoft for Windows
system Server 2003. The recommendations listed here pertain to the Windows Server 2003 operating
configuration system only and do not include the requirements for software applications that run on your system.
Please check your application requirements to make certain your system can run both the operating
system and your software. Most software vendors have this information posted to their website.
3
Implementing Microsoft Windows Server 2003 on ProLiant servers
Server platforms Table 2 lists the ProLiant servers, ROM version, and ROM date that support Windows Server 2003.
Refer to the following resources on the Web to assist in determining the ROM version and family of
your ProLiant server.
4
Implementing Microsoft Windows Server 2003 on ProLiant servers
Supported Table 3 lists supported ProLiant utilities, drivers, and other value-add software and their
software corresponding version needed for Windows Server 2003.
5
Implementing Microsoft Windows Server 2003 on ProLiant servers
Supported Table 4 lists supported ProLiant storage options and recommended driver revisions needed to
storage options interface with Windows Server 2003.
6
Implementing Microsoft Windows Server 2003 on ProLiant servers
7
Implementing Microsoft Windows Server 2003 on ProLiant servers
Supported Table 5 lists supported ProLiant network interface controllers (NICs) and driver revisions supported by
network Windows Server 2003.
interface
Table 5. Supported ProLiant Network Interface Controllers for Windows Server 2003
controllers
NIC Driver Location Digital
signature
NC3120 Fast Ethernet N100325.SYS Windows Server 2003 CD Yes
NC3121 Fast Ethernet N100325.SYS Windows Server 2003 CD Yes
NC3122 Fast Ethernet N100325.SYS Windows Server 2003 CD Yes
NC3123 Fast Ethernet N100325.SYS Windows Server 2003 CD Yes
NC3131 Fast Ethernet N100325.SYS Windows Server 2003 CD Yes
NC3132 Fast Ethernet Upgrade N100325.SYS Windows Server 2003 CD Yes
Module
NC3133 Fast Ethernet Upgrade N100325.SYS Windows Server 2003 CD Yes
Module
NC3134 Fast Ethernet N100325.SYS Windows Server 2003 CD Yes
NC3135 Fast Ethernet Upgrade N100325.SYS Windows Server 2003 CD Yes
Module
NC3162 Fast Ethernet (Embedded) N100325.SYS Windows Server 2003 CD Yes
NC3163 Fast Ethernet (Embedded) N100325.SYS Windows Server 2003 CD Yes
NC4621 Token Ring NIC CPQTRND5.SYS Windows Server 2003 CD Yes
NC6132 Gigabit Module N1000NT5.SYS Windows Server 2003 CD Yes
NC6133 Gigabit Module N1000NT5.SYS Windows Server 2003 CD Yes
NC6134 Gigabit N1000NT5.SYS Windows Server 2003 CD Yes
NC6136 Gigabit N1000NT5.SYS Windows Server 2003 CD Yes
NC7131 Gigabit N1000NT5.SYS Windows Server 2003 CD Yes
NC7132 Gigabit Module N1000NT5.SYS Windows Server 2003 CD Yes
8
Implementing Microsoft Windows Server 2003 on ProLiant servers
ProLiant A critical goal of HP’s Adaptive Enterprise is to offer customers the ability to reduce exposure to
unplanned downtime through automated software and hardware tools that predict, diagnose, and
cluster
respond immediately to potential fault conditions. HP delivers intelligent fault resilience with its High
support Availability Clustering product solutions and kits built on Windows Server 2003, Enterprise Edition,
industry standard ProLiant servers, Smart Array Cluster Storage, or StorageWorks platforms
integrated with HP management tools.
The ProLiant DL380 G3 Packaged Cluster, ProLiant DL380 G2 Packaged Cluster, and ProLiant
CL380 Packaged cluster now support Windows Server 2003, Enterprise Edition.
The ProLiant Cluster Kits HA/F500 for Enterprise Virtual Array, HA/F500 for MA8000, and
HA/F100 & F200 for MSA1000 will be available shortly after launch.
PCI Hot Plug PCI Hot Plug is the ability to physically insert, remove, or replace PCI adapters while a ProLiant
server is powered on. PCI Hot Plug operations may be performed under Windows Server 2003 on
support supported ProLiant servers with the PCI Hot Plug Filter Driver installed. ProLiant storage options and
network interface controllers are supported for PCI Hot Plug operations.
Higher availability on HP and Microsoft solutions is achieved through the deployment of Hot Plug
RAID Memory, the most robust memory-protection solution in the HP Advanced Memory Protection
strategy. With the introduction of the next generation of industry-leading ProLiant 8-way platforms,
the ProLiant DL760 G2 and ProLiant DL740, HP is the first and only vendor to offer Hot Plug RAID
Memory in an industry-standard platform. With the introduction of these two new platforms based on
the HP F8 chipset, customers will be able to, for the first time, deploy mainframe levels of availability
9
Implementing Microsoft Windows Server 2003 on ProLiant servers
in their industry-standard IT environments, without the high cost of mainframe technology. With the
HP/Microsoft solution, customers can dynamically hot-add memory capacity without powering down
the server which delivers true resource scalability and maximum uptime for enterprise customers. The
Hot Add Memory feature in the specified 4-way and 8-way ProLiant servers is only supported in
Windows Server 2003.
The following Hot Plug RAID Memory driver and utility are included in Version 6.30A of the ProLiant
Support Pack for Microsoft Windows Server 2003:
Remote Remote management products, such as Integrated Lights-Out, Remote Insight Lights-Out Edition, and
Remote Insight Lights-Out Edition II, remain an important part of the ProLiant solution adding new
management support for the Windows Server 2003 operating system. Drivers for these products are included in
support the ProLiant Support Pack for Microsoft Windows Server 2003. Refer to Table 6 for supported remote
management features and functionality on Windows Server 2003.
10
Implementing Microsoft Windows Server 2003 on ProLiant servers
For detailed QuickSpecs and other information about remote management products, visit:
www.hp.com/servers/manage.
SmartStart Beginning with SmartStart 6.30, server deployment of Microsoft Windows Server 2003 is now
consistent and easy every time with ROM-based utilities, whether you choose a SmartStart assisted
installation installation or a manual operating system installation.
paths
To fully optimize the performance of your hardware platform, a SmartStart assisted installation walks
you through the entire operating system installation process. Using an assisted installation, SmartStart
prepares the server for installation, allows you to install the operating system using the vendor-
supplied CDs, and provides automated installation of server support software using ProLiant Support
Packs (PSPs).
For a manual installation of the operating system, you can take advantage of the ROM-based utilities
and vendor-supplied operating system media before manually installing server support software from
the SmartStart CD.
11
Implementing Microsoft Windows Server 2003 on ProLiant servers
Pre- To prepare for installation, gather the supported software detailed below.
installation 1. Obtain ProLiant Support Pack (PSP) for Microsoft Windows Server 2003 Version 6.30A (or
tasks later) at http://h18001.www1.hp.com/partners/microsoft/windowsserver2003/
support.html or from the SmartStart 6.30 CD. This PSP contains device drivers, management
agents, and utilities supported under Windows Server 2003.
Note: Once the ProLiant Support Pack for Microsoft Windows Server 2003 Version 6.30A
(or later) is installed, you can use Insight Manager 7 SP2 available at
http://h18000.www1.hp.com/products/servers/management/cim7-intermediate.html to
manage your Windows Server 2003 servers. Insight Manager 7 SP2 requires installing
Microsoft SQL Server or Microsoft Database Engine (MSDE) before installing Insight
Manager 7 SP2. MSDE is delivered in the Insight Manager 7 SP2 SoftPaq. Insight Manager
7 SP2 currently runs under Microsoft Windows NT® 4.0, Microsoft Windows 2000, and
Microsoft Windows Server 2003.
IMPORTANT: Create the bootable diskette set if you plan to use the
SmartStart Assisted Installation Path.
The ProLiant servers listed below are pre-configured with the ROM-Based Setup Utility
(RBSU). This utility can be used in place of the System Configuration Utility and must be used
to specify the operating system on the server if you are using the SmartStart Assisted
Installation Path.
12
Implementing Microsoft Windows Server 2003 on ProLiant servers
Procedures This section outlines the proper procedures to follow when performing a clean (new) installation of
the Windows Server 2003 operating system on ProLiant servers.
for
performing a To complete a Windows Server 2003 installation fully supported by HP, follow these steps when
setting up the system. Read the following sequence completely before you begin.
clean
installation
Blade The ProLiant Essentials Rapid Deployment Pack is a server deployment product that facilitates the
installation installation, configuration, and deployment of high-volumes of servers via a GUI-based console using
either scripting or imaging technology.
Especially designed for the ProLiant BL servers, but supporting all ProLiant servers, the Rapid
Deployment Pack has advanced features that can detect and display server blades based on their
physical rack, enclosure, and bay location. You can set the deployment console to automatically
install or redeploy a previous computer's configuration to a new blade when replaced.
To install Windows Server 2003 on ProLiant BL servers, HP recommends using Rapid Deployment
Pack Version 1.40 (or later).
All blade enclosures ship with a BL Foundation Pack which includes the Rapid Deployment Pack CD.
The Rapid Deployment Pack CD contains all of the drivers, agents, and support software that the
blade needs. Use the Rapid Deployment Pack CD with any deployment method chosen to install
software on ProLiant BL servers.
For additional product information and usage instructions for Rapid Deployment Pack, visit
http://h18013.www1.hp.com/products/servers/management/rdp/index.html.
Details about other deployment options can be found at the following locations:
1. Select a supported system platform from the server platforms listed in Table 2.
2. Inspect the system to confirm that it conforms to the platform-specific configuration listed in
Table 2. If necessary, update the system ROMs as specified in this table.
3. Use the System Configuration Utility to configure the hardware for your server. See the list of
RBSU-capable ProLiant servers on page 12 to determine if this step is necessary for your
server.
4. If the server has a Smart Array 642, Smart Array 641, Smart Array 5300, Smart Array 531,
Smart Array 5i, Smart Array 431, or Integrated Smart Array Controller installed as the boot
controller, configure these arrays by accessing the Option ROM Configuration for Arrays
utility via the F8 key during boot. Once the configuration is complete, exit the utility to
continue the boot process.
13
Implementing Microsoft Windows Server 2003 on ProLiant servers
Note: Alternatively, you may set your array controller as the secondary controller and install
the OS to a SCSI controller. Once the OS is installed, configure the array through the Array
Configuration Utility (ACU) using the PSP for Microsoft Windows Server 2003 Version
6.30A.
5. Insert the Windows Server 2003 CD into CD-ROM drive to begin installation.
6. After Windows Server 2003 has been installed, install the Simple Network Management
Protocol (SNMP), if you want to use the functionality of the ProLiant Management Agents.
• Run the SETUP.EXE program included with the PSP. By default, all software components
are selected for installation. In most circumstances, this default selection should not be
altered.
• Click the Install button to proceed with the installation. Although all software components
are selected for installation by default, only those required by the server will install. After
the installation is complete, the utility will display successfully installed components, non-
applicable components, and any component installation failures.
Command prompt installation
• Use the SETUPC.EXE to install the PSP from a command line prompt without user
interaction. This utility is designed as a tool that can be scripted. As with the SETUP.EXE
program, all components appropriate for the target server will be installed.
• For additional usage information, refer to the BP000150.TXT file included with the
downloaded files and the ProLiant Support Pack and Deployment Utilities User Guide
posted on the download Web page for the PSP.
14
Implementing Microsoft Windows Server 2003 on ProLiant servers
Unattended For detailed procedures on unattended installs, refer to Microsoft documentation. When using an
install UNATTEND.TXT file, follow these additional procedures.
1. Add the following line in the unattend section if the UNATTEND.TXT file has the
OEMPreinstall flag set.
[UNATTEND]
DisableVirtualOemDevices=Yes
2. Ensure that any special hardware-specific drivers appropriate for your ProLiant server are
available in the specified OEMFilesPath. The drivers for the supported devices may not be
included on the base media.
Note: These changes are only necessary when using an UNATTEND.TXT file with the
OEMPreinstall flag set. Failure to set this flag could cause installs to abort with the following
message: “File [filename] could not be loaded. Error code is 18. Setup cannot continue.”
Known issues This section details the known issues with installing Windows Server 2003 on ProLiant servers and
provides information about resolving them.
and
workarounds Table 7. Known Issues
Management Issue 1 Yellow exclamation mark gets displayed in ATI Device Manager with Remote
product issues Insight Lights-Out Edition installed.
Description When using Remote Insight Lights-Out Edition, the Windows Server 2003
Device Manager displays a yellow exclamation mark beside the ATI device.
However, when this happens, there is no loss of functionality or other reported
symptoms.
Memory issues Issue 2 Hibernation issue exists with 4 GB or more system memory.
Description The Hibernation tab does not install on servers with 4 GB or more system
memory.
Networking Issue 3 Embedded network interface controllers are not enumerated consistently.
issues
Description After installing and configuring embedded network interface controllers (NICs)
post Windows Server 2003 installation, the port configurations may not operate
as expected.
15
Implementing Microsoft Windows Server 2003 on ProLiant servers
Storage issues Issue 4 Dynamic disk drives attached to Compaq Fibre Channel HBAs disappear after
“hot-swap.”
Description After hot removal and subsequent hot addition of the Compaq Fibre Channel
Array or the Compaq Fibre Channel Host Controller /P (64-bit/66-MHz Fibre
Channel Host Adapter) from one slot to another, the dynamic disk drive letters
associated with the drives attached to the Compaq Fibre Channel Array or the
Compaq Fibre Channel Host Controller /P are no longer listed in the Device
Manager.
Workaround Reboot the server for the correct dynamic disk drive letters to return.
Issue 5 The Smart Array 4200 Controller Driver does not install during Setup.
Description During the install of Windows Server 2003, a popup box reports the following:
The Smart Array 4200 Controller will not be installed during Windows Server
2003 Setup if this controller is set as the boot controller.
Issue 6 Software fault tolerant volumes (dynamic disks) fail during driver upgrade or
rollback.
Description When a device driver is updated for a device containing dynamic disks, the
software fault tolerant volumes located on these dynamic disks will fail and will
require regeneration.
Description When a device driver for a secondary device is updated, the Windows Server
2003 operating system may request a reboot.
16
Implementing Microsoft Windows Server 2003 on ProLiant servers
Issue 8 Incorrect port number and port ID returned in insertion and removal events.
Description When using Smart Array 5xxx Notification Driver, CPQCISSE.SYS, Version
5.42.0.32 with Smart Array Cluster Storage, the port number and port ID in
removal and insertion events are reported incorrectly.
Issue 9 The native OS backup utility may prohibit appending data to the tape drive.
Description When performing a backup using the native OS backup utility, you might
receive a message describing a hardware error.
In this case, the following message will be displayed at the end of the backup
job:
Drive Error: The device reported an error on a request to write
data to media. Error Reported: Invalid command. There may be a
hardware or media problem. Please check the system event log for
relevant failures.
The backup log will suggest that drive C is not a valid drive or that you do not
have access to the drive.
After you receive this error, you can no longer append data to that tape drive.
17
Implementing Microsoft Windows Server 2003 on ProLiant servers
System health Issue 10 ProLiant Advanced System Management Controller Driver for Microsoft
issues Windows Server 2003 (CPQASM.SYS) will not load on the ProLiant 3000,
5500, or 6500.
Description The ProLiant Advanced System Management Controller Driver for Microsoft
Windows Server 2003 (CPQASM.SYS) will not load on the ProLiant 3000,
5500, or 6500. The Windows Server 2003 version of this driver depends on
ACPI support, and these ProLiant models do not support ACPI. Other
components that depend on this driver may fail to load or may not provide full
functionality.
Workaround Install version 5.30.2195.1 (or later) of the ProLiant Advanced System
Management Controller Driver for Microsoft Windows 2000. The Windows
2000 version of this driver does not have a dependency on ACPI support and
provides the same functionality on the affected systems as the Windows Server
2003 version of the driver.
Solution A Windows Server 2003 driver will be available shortly at the following
location: http://h18001.www1.hp.com/partners/microsoft/
windowsserver2003/support.html.
Unattended Issue 11 Unattended installs abort when using UNATTEND.TXT file with the
installation issues OEMPreinstall flag set.
18
Implementing Microsoft Windows Server 2003 on ProLiant servers
The problem occurs because the Windows Server 2003 Installer interacts with
the embedded virtual install disk when the OEMPreinstall flag is set in the
UNATTEND.TXT file, but no files are specified to be preinstalled.
In order for this error condition to be triggered, all of the following conditions
must be met:
Workaround To work around this problem, use one of the following methods:
Preferred method:
If the OEMPreinstall flag is set to Yes in the UNATTEND.TXT file, set the
"DisableVirtualOemDevices" flag to Yes in the [UNATTENDED] section of the
UNATTEND.TXT file, as shown in the following example:
[UNATTENDED]
DisableVirtualOemDevices=Yes
Other methods:
Avoid setting the OEMPreinstall flag to Yes in the UNATTEND.TXT file if files are
not specified to be preinstalled.
OR
Disable the virtual install disk in the advanced options of the ROM-Based Setup
Utility (RBSU) for the affected server.
19
Implementing Microsoft Windows Server 2003 on ProLiant servers
For more For more information about the Windows Server 2003 program, visit the Windows Server 2003
support page at http://h18001.www1.hp.com/partners/microsoft/windowsserver2003/support.html
information and the Microsoft website (www.microsoft.com/).
Feedback Help us improve our technical communication. Let us know what you think about the technical
information in this document. Your feedback is valuable and will help us structure future
communications. Please send your comments to: [email protected].
6/2003
Document Number TC030609IN
20