Using the HP Rapid Deployment Pack 3.7 to Deploy Microsoft Windows Server 2003 for IA64

1 Overview
This document describes modifying HP Rapid Deployment Pack (RDP) deployment jobs to
deploy tested Microsoft® Windows® Server 2003 IA-64 operating systems to HP Integrity mid-range
and high-end systems, including the HP Integrity rx7620, rx7640, rx8620, rx8640, Superdome sx1000,
and Superdome sx2000. To perform the procedures described in this document, you must have
a good understanding of both RDP and Integrity mid-range and high-end systems. After reading
this document, you should be able to create customized jobs to deploy Windows to Integrity
systems using either scripting or imaging. However, RDP cannot manage every aspect of Integrity
mid-range and high-end systems. You must perform certain tasks, including partition creation,
before using RDP.
NOTE: For information about creating disk partitions, see the Smart Setup Guide located on
your Smart Setup Media or at http://docs.hp.com/en/windows.html.
These procedures have been tested using the following versions of Windows:
Microsoft Windows Server 2003 Service Pack (SP) 1 and SP2, Enterprise Edition for IA64
Microsoft Windows Server 2003 SP2, DataCenter Edition for IA64
Prerequisites
Before performing the procedures in this document, RDP must be installed and configured
on a ProLiant G3 or G4 server with two or more processors and 2 GB RAM, or on an
equivalent virtual machine. For detailed information about installing RDP, see the HP Rapid
Deployment Pack Installation Guide at http://www.hp.com/servers/rdp.
RDP cannot be installed through a Terminal Services, remote shell, or network share
connection or using vMedia.
DHCP must be installed and accessible on the network before installing RDP.
RDP components requiring no modification
Certain tasks, such as a Preboot eXecution Environment (PXE) boot, are performed in the same
way on Integrity mid-range and high-end systems, as well as HP Integrity entry—class systems.
If you select a LAN boot entry, the system searches for a PXE server on the network and boots
from that server. When you power on the system, it displays an Extensible Firmware Interface
(EFI) menu similar to the following screen.
In this example, PXE-boot is enabled from the network cards connected on the network.
Prerequisites 9