Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators

Beginning with SmartStart 6.30, server deployment of Windows Server 2003 is now consistent and easy every time with ROM-based utilities, whether you choose a SmartStart assisted installation or a manual OS installation.

To fully optimize the performance of your hardware platform, a SmartStart assisted installation walks you through the entire OS installation process. SmartStart prepares the server for installation, enables you to install the OS using the vendor-supplied CDs, and provides automated installation of server support software using PSPs.

For a manual installation of the OS, you can take advantage of the ROM-based utilities and vendor-supplied OS media before manually installing server support software from the SmartStart CD.

For more information on SmartStart, go to the SmartStart Web site at http://www.hp.com/servers/smartstart. The installation guide, available on this Web site, walks you through both SmartStart installation paths.

Preinstallation Tasks

To prepare for installation, gather the following supported software:

• Obtain PSP for Windows Server 2003 v6.30A (or later) at http://h18001.www1.hp.com/ partners /microsoft/windowsserver2003/support.html or from the SmartStart 6.30 or later CD. This PSP contains device drivers, management agents , and utilities supported under Windows Server 2003.

  tip

  After the PSP for Windows Server 2003 v6.30A (or later) is installed, you can use Systems Insight Manager (SIM) from http://www.hp.com/go/hpsim to manage your Windows Server 2003 servers. SIM requires installing Microsoft SQL Server or Microsoft Database Engine (MSDE) before installing SIM. MSDE is delivered in the SIM SoftPaq. SIM currently runs under Windows 2000 and Windows Server 2003.

• Obtain SYSTEM Configuration Utility v2.58 (or later for pre-RBSU enabled ProLiant Servers) at http://h18023.www1.hp.com/support/files/server/us/locate/1950.html and create the associated bootable floppy disk set. Invoke the utility and verify that all system configuration options conform to those listed for the platform you have chosen .

note

Create the bootable diskette set if you plan to use the SmartStart Assisted Installation path .

The ProLiant servers listed in Table 7.8 and later model ProLiant servers are preconfigured with the RBSU. This utility must be used to specify the OS on the server if you are using the SmartStart Assisted Installation path.

Table 7.8. ProLiant Servers Utilizing the RBSU

Procedures for Performing a Clean Installation

This section outlines the proper procedures to follow when performing a clean (new) installation of the Windows Server 2003 OS on ProLiant servers.

To complete a Windows Server 2003 installation fully supported by HP, follow these steps when setting up the system. Read the sequence in the following sections completely before you begin.

Blade Installation

The ProLiant Essentials Rapid Deployment Pack (RDP) is a server deployment product that facilitates the 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 supported with all ProLiant servers, the RDP 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 RDP v1.40 (or later).

All blade enclosures ship with a BL Foundation Pack, which includes the RDP CD. The RDP CD contains all of the drivers, agents, and support software that the blade needs. Use the RDP CD with any deployment method chosen to install software on ProLiant BL servers.

For additional product information and usage instructions for RDP with Windows 2003, see the HP ProLiant Essentials RDP Windows Edition Installation Guide at http://www.hp.com/servers/rdp.

You can get details about other deployment options at the following locations:

• For ProLiant BL-e class : http://h18004.www1.hp.com/products/servers/proliant-bl/e-class/deployment.html.

• For ProLiant BL-p class : ftp://ftp.compaq.com/pub/supportinformation/techpubs/installation_guides/307153-001_rev1_us.pdf.

Manual Install

To perform a manual installation, follow these steps:

1. Select a supported system platform from the server platforms listed previously in Table 7.2.

2. Inspect the system to confirm that it conforms to the platform-specific configuration listed in Table 7.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 in Table 7.9 to determine whether this step is necessary for your server.

Table 7.9. Known Issues and Workarounds for Implementing Windows 2003

Management Product Issues
Issue 1	Yellow exclamation mark gets displayed in ATI Device Manager with RILOE installed.
Description	When using RILOE, 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.
Workaround	This condition is normal and does not cause any loss of functionality.
Solution	HP engineers are working with Microsoft to resolve this issue.
Memory Issues
Issue 2	Hibernation issue exists with 4GB or more system memory.
Description	The Hibernation tab does not install on servers with 4GB or more system memory.
Workaround	See solution.
Solution	Hibernation with 4GB or more system memory is not supported in Windows Server 2003.
Networking Issues
Issue 3	Embedded NICs are not enumerated consistently.
Description	After installing and configuring embedded NICs post Windows Server 2003 installation, the port configurations might not operate as expected.
Workaround	Switch cables if you are experiencing this situation.
Solution	HP engineers are working with Microsoft to resolve this issue.
Storage Issues
Issue 4	Dynamic disk drives attached to Compaq Fibre Channel HBAs (host bus adaptors) 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/66MHz 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.
Solution	Scheduled to be fixed in a later Microsoft OS release.
Issue 5	The Smart Array 4200 controller driver does not install during setup.
Description	During the install of Windows Server 2003, a pop-up box reports the following: "Setup had problems installing the following device: Compaq Smart Array 4200 Controller. Do you want to delay installing this device until after setup is complete?" The Smart Array 4200 controller will not be installed during Windows Server 2003 setup if this controller is set as the boot controller.
Workaround	Manually install the CPQARRY2.SYS driver by pressing F6 during setup.
Solution	HP engineers are working with Microsoft to resolve this issue.
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 fail and require regeneration.
Workaround	No workaround is available at this time.
Solution	Scheduled to be fixed in a later Microsoft OS release.
Issue 7	Upgrading miniport driver for secondary device requires reboot.
Description	When a device driver for a secondary device is updated, the Windows Server 2003 OS might request a reboot.
Workaround	Reboot the server as prompted.
Solution	Scheduled to be fixed in a later Microsoft OS release.
Issue 8	Incorrect port number and port ID returned in insertion and removal events.
Description	When using Smart Array 5xxx Notification Driver, CPQCISSE.SYS, v5.42.0.32 with Smart Array Cluster Storage, the port number and port ID in removal and insertion events are reported incorrectly.
Workaround	No workaround is available at this time.
Solution	HP engineers are working to resolve this issue.
Issue 9	The native OS backup utility might 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.
Workaround	See solution.
Solution	Download the Microsoft hotfix WindowServer2003-KB817688-I386-ENU.EXE from this Web site: http://h18001.www1.hp.com/partners/microsoft/windowsserver2003/support.html. Then, run this executable in the Windows Server 2003 environment.
System Health Issues
Issue 10	ProLiant Advanced System Management Controller Driver for Windows Server 2003 (CPQASM.SYS) will not load on the ProLiant 3000, 5500, or 6500.
Description	The ProLiant Advanced System Management controller driver for 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 (Advance Configuration Power Interface) support, and these ProLiant models do not support ACPI. Other components that depend on this driver might fail to load or might not provide full functionality. The following message will be displayed in CPQSETUP.LOG after the driver is installed: Name: hp ProLiant Advanced System Management Controller Driver for Windows Server 2003 New Version: 5.30.3718.0 Beginning Silent Session... The software is not installed on this system, but is supported for installation. -the component will be installed Installation failed on at least one device. One of the devices may have been deleted through Device Manager and a reboot may be necessary to complete the driver installation for this device. The operation was not successful.
Workaround	Install v5.30.2195.1 (or later) of the ProLiant Advanced System Management Controller Driver for 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 Installation Issues
Issue 11	Unattended installs abort when using UNATTEND.TXT file with the OEMPreinstall flag set.
description	Unattended installs abort with the following message: File [filename] could not be loaded. Error code is 18. Setup cannot continue. When installing any edition of Windows Server 2003 on a ProLiant server that has an embedded virtual install disk, this error message may be generated when using an UNATTEND.TXT file that includes the OEMPreinstall flag. 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 . For this error condition to be triggered, all of the following conditions must be met: Installation of Windows Server 2003 (or later) on a server. Installation must be performed using an UNATTEND.TXT script and must follow these rules: Installation must be CD-ROM or floppy disk-based. The OEMPreinstall flag must be set in the UNATTEND.TXT file. The UNATTEND.TXT file must not specify any files to be preinstalled. The server must have an active virtual install disk.
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 theUNATTEND.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 RBSU for the affected server.
Solution	HP engineers are working with Microsoft to resolve this issue.

4. If the server has a Smart Array 64xx , 642, 641, 53xx, 531, 5i, 431, or Integrated Smart Array controller installed as the boot controller, configure these arrays by accessing the Option ROM Configuration for Arrays (ORCA) utility via the F8 key during boot. After the configuration is complete, exit the utility to continue the boot process.

note

Alternatively, you can set your array controller as the secondary controller and install the OS to a SCSI controller. After the OS is installed, configure the array through the ACU using the PSP for Windows Server 2003 v6.30A or later.

5. Insert the Windows Server 2003 CD into your 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. To install SNMP, follow these steps:

1. Select Control Panel from the Start menu.

2. Select Add/Remove Programs.

3. Click the Add/Remove Windows Components button.

4. Select Management and Monitoring Tools from the list of components.

5. Click the Details button.

6. Select Simple Network Management Protocol so that a check mark is displayed in the check box.

7. Click the OK button and then the Next button.

8. Click the Finish button.

7. Install v6.30A (or later) of the PSP for Windows Server 2003, which is available at http://h18001.www1.hp.com/partners/microsoft/windowsserver2003/support.html. The PSP contains numerous files. For the PSP to be installed properly, all files must be present in the same directory as the PSP's SETUP.EXE program.

Primary Installation Method

1. 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 .

2. 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, nonapplicable components, and any component installation failures.

Command Prompt Installation

1. Use the SETUP.EXE program 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.

2. For additional usage information, refer to the BP000150.TXT file included with the downloaded files and the PSP and Deployment Utilities User Guide posted on the download Web page for the PSP.

Unattended Install

For detailed procedures on unattended installs, refer to the documentation included on the Windows 2003 CD. When using an 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 might 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 and Workarounds

Table 7.9 outlines the known issues and workarounds for the Windows Server 2003 installation. In addition to reviewing this table, be sure to check the HP and Microsoft Web sites for updates on Windows Server 2003 installation issues.

note

Installations performed using SmartStart, RDP, PXE/Network, or Disk Image (for example, the OS image is copied to the hard drive) are not affected.