This document describes how to install and configure the operating system and HP software on
HP Integrity servers running Windows Server 2003.
The document printing date and part number indicate the document’s current edition. The
printing date changes when a new edition is printed. Minor changes may be made at reprint
without changing the printing date. The document part number changes when extensive changes
are made.
Document updates may be issued between editions to correct errors or document product changes.
To ensure that you receive the updated or new editions, you should subscribe to the appropriate
product support service. See your HP sales representative for details.
The latest version of this document can be found online at http://www.docs.hp.com.
Intended Audience
This document is intended for system administrators and HP support personnel responsible for
installing, configuring, and managing HP Integrity servers.
This document is not a tutorial.
New and Changed Information in This Edition
This document includes the following changes since its last release:
•Added “About This Document” section
•Added introductory/overview content at the beginning of Chapters 1 and 2
•Added additional steps to “Specify server settings” procedures in Chapter 2
•Removed references to Intelligent Networking Pack licensing (INP functionality was
integrated into the core product)
Document Organization
This document is organized as follows:
Chapter 1
Chapter 3
Chapter 4
Appendix A
Appendix B
Appendix C
Chapter 1 “Preparing for the installation”. Describes the steps to prepare the server for
installation of the operating system, SmartSetup, and management software.
Chapter 2 “Installing the OS”. Describes how to install the operating system software.Chapter 2
Chapter 3 “Installing the Management Tools”. Describes how to install the server
management software.
Chapter 4 “Performing hot-plug operations”. Describes how to add and remove server
hardware such as network interface cards (NICs) or RAID cards.
Appendix A “Preparing the server for Microsoft SQL Server 2005”. Describes how to
configure and install Microsoft SQL Server 2005.
Appendix B “EFI Utilities”. Describes the server's Extensible Firmware Interface (EFI) and
EFI-Based Setup Utility (EBSU).
Appendix C “Management processor and Special Administration Console”. Describes
the server's management processor (MP) and Special Administration Console (SAC).
These are tools for monitoring the operating system installation and administering the
server from a headless console.
Typographic Conventions
This document uses the following typographical conventions:
Intended Audience11
WARNINGA warning calls attention to important information that if not understood
or followed will result in personal injury or nonrecoverable system
problems.
CAUTIONA caution calls attention to important information that if not understood
or followed will result in data loss, data corruption, or damage to
hardware or software.
IMPORTANTThis alert provides essential information to explain a concept or to
complete a task
NOTEA note contains additional information to emphasize or supplement
important points of the main text.
KeyCap
Computer output
User input
Command
Ctrl+xA key sequence. A sequence such as Ctrl+x indicates that you must hold
[]The contents are optional in command line syntax. If the contents are a
{}The contents are required in command line syntax. If the contents are a
...The preceding element can be repeated an arbitrary number of times.
Indicates the continuation of a code example.
|Separates items in a list of choices.
The name of a keyboard key or graphical interface item (such as buttons,
tabs, and menu items). Note that Return and Enter both refer to the
same key.
Text displayed by the computer.
Commands and other text that you type.
A command name or qualified command phrase.
down the key labeled Ctrl while you press another key or mouse button.
list separated by |, you must choose one of the items.
list separated by |, you must choose one of the items.
Related Information
You can find more information about HP Integrity servers, server management, and software
in the following locations:
•For an overview of the HP Integrity server family: http://www.hp.com/go/integrity
•For other documents supporting Windows Server 2003 on HP Integrity Servers (see the
section titled “Windows 64–bit on HP Integrity Servers”):
http://docs.hp.com/en/windows.html
•For technical support resources (drivers, patches, upgrades, migration issues, to sign up for
alerts, etc.):
The publishing history below identifies the edition dates of this manual. Updates are made to
this publication on an unscheduled, as needed, basis. The updates will consist of a complete
replacement manual and pertinent online or CD documentation.
Manufacturing Part
Number
5992-0926
Supported Operating
Systems
Server 2003 for
Itanium-based
Systems, 64–bit
HP Encourages Your Comments
HP encourages your comments concerning this document. We are committed to providing
documentation that meets your needs. Send any errors found, suggestions for improvement, or
compliments to:
feedback@fc.hp.com
Please include the document title, manufacturing part number, and any comment, error found,
or suggestion for improvement you have concerning this document.
Installing Microsoft® Windows® Server 2003 for Itanium®-based systems on an HP Integrity
server involves preparing the hardware for operating system (OS) installation, loading the OS,
and updating the system with the latest OS patches. This chapter helps you plan the installation
based on the server model, the OS edition, the source of the OS media, and your network
environment. Subsequent chapters guide you through the installation process.
NOTE:HP Integrity servers must run Windows Server 2003 with either Service Pack 1 (SP1)
or Service Pack 2 (SP2). If your operating system is already installed and you are running an
earlier version of Windows Server 2003, you must upgrade your operating system to SP1 or SP2.
When updating to SP1 or SP2, perform the update in the following order:
1.Install the latest HP Integrity Support Pack.
2.Reboot the machine.
3.Install the desired Service Pack.
4.Reboot the machine again.
5.Use the Windows Update Service to ensure that you have the latest Microsoft updates.
If the Windows Server 2003 operating system has already been installed on your system, or if it
was pre-installed by HP before your system was delivered, you do not have to perform any of
the steps described in this chapter (Chapter 1 “Preparing for the installation”) or in Chapter 2
(Chapter 2 “Installing the OS”). You can proceed directly to Chapter 3 (Chapter 3 “Installing the
Management Tools”) and begin the installation of your management tools software.
If your Windows Server 2003 operating system is not already installed, or if you wish to reinstall
it for some reason, or if you wish to migrate to Windows Server 2003 from another operating
system, you will need to perform one or more of the following steps described in this chapter,
in the following order:
•Choose an installation method
•Check hardware compatibility
•Back up your existing data
•Choose your installation environment and media
•Locate your Microsoft Certificate of Authenticity
•Choose an installation option:
— Local installation choices (pick one):
◦Integrated Remote Console, or IRC (available on rx2660, rx3600, rx6600, BL860c,
and BL870c servers only)
◦Preboot execution environment (PXE) + Remote Installation Server (RIS)
Choosing an installation method
When you purchase an HP Integrity server, you can order additional hardware, support options,
and an OS enablement kit (such as the HP Integrity Essentials Foundation Pack for Windows).
You can also order factory installation of the OS. Depending on your order (or subsequent use),
your system is in one of the following states:
•Factory-installed Windows Server 2003
Windows Server 2003, Datacenter Edition, is usually factory-installed. To get the system up
and running, verify that the OS was installed correctly, set up the system, and update it with
Choosing an installation method15
the latest firmware, drivers, and Microsoft patches and fixes (QFEs) available in the latest
HP Integrity Essentials Foundation Pack or from the HP Integrity servers support website:
http://www.hp.com/support/itaniumservers/
•Factory-installed OS other than Windows Server 2003
If you choose to run Windows Server 2003 instead of the factory-installed OS, you can
perform the migration yourself on an entry-level server or engage an HP Customer Engineer
(CE) to perform the migration on a mid-range or high-end server. Contact HP support or
sales to engage the CE.
When you migrate to Windows Server 2003 from another OS, pay close attention to the
differences in supported hardware I/O, in particular, between the two operating systems.
You must replace incompatible components with those supported on Windows Server 2003.
If you want to keep the data residing on the server hard disk, you must back up the data
and verify that you can restore it elsewhere. Then prepare the server hardware for installation.
Use the HP Smart Setup media and the Microsoft Windows Server 2003 media to load the
OS and HP value-added software (drivers, tools, utilities, and agents) on the server. After
installation, set up the system, and update it with the latest firmware, drivers, and Microsoft
patches and fixes (QFEs) on the HP Smart Update media included in the latest HP Integrity
Essentials Foundation Pack or from the HP Integrity servers support website:
http://www.hp.com/support/itaniumservers/
•No operating system installed
Prepare the server hardware for installation. Use the HP Smart Setup media and the Microsoft
Windows Server 2003 media to load the OS on the server. After installation, verify that the
OS was installed correctly, configure the system, and update it with the latest drivers and
Microsoft patches and fixes (QFEs) on the HP Smart Update media included in the latest
HP Integrity Essentials Foundation Pack or from the HP Integrity servers support website:
http://www.hp.com/support/itaniumservers/
•Installed Windows Server 2003 incorrect or inoperable
Prepare the server hardware for installation. Use the HP Reinstallation media to restore the
OS files. After reinstallation, verify that the OS was installed correctly, configure the system,
and update it with the latest firmware, drivers, and Microsoft patches and fixes (QFEs) on
the HP Smart Update media included in the latest HP Integrity Essentials Foundation Pack
or from the HP Integrity servers support website:
http://www.hp.com/support/itaniumservers/
Ensuring platform compatibility
If you are migrating from another operating system to Windows Server 2003, ensure that the
hardware is compatible with Windows Server 2003 and that any data on the server disk is backed
up..
Check hardware compatibility
To verify that your existing hardware is compatible with Windows Server 2003, complete the
following steps:
1.See the Options & Accessories page for each server to check supported hardware
configurations. For example, the Options & Accessories page for the rx8620 server found at
http://h20341.www2.hp.com/integrity/cache/342107-0-0-0-121.html lists the processors,
memory, adapters, cards, and controllers that are available for that server.
2.Verify existing device compatibility at the HP Integrity server connectivity website:
3.Verify storage compatibility by reviewing the HP Integrity Server-Storage support matrices
at http://www.hp.com/products1/serverconnectivity/support_matrices.html. This list is not
exhaustive because storage vendors can support more configurations than those indicated
at the site. As a general rule, check with your storage vendor and an HP sales representative
for a definitive statement on server and storage compatibility.
Back up existing data
To restore the data on the hard disk of the server after migrating to Windows, you must first
back up the data and verify that you are able to restore it:
1.Perform a complete server backup using your existing backup utilities.
2.Verify the integrity of the backup by restoring samples of data to another server.
3.Store the backup in a safe place.
Choosing an installation environment
The installation environment consists of the server model, the OS edition, a GUI console or a
headless console, and the media you need to perform the installation. In addition to installing
from Smart Setup and Microsoft media or reinstallation media, you can automate the installation
of Windows Server 2003 using a Remote Installation Service (RIS) server on the network and a
preboot execution environment (PXE) client on the HP Integrity server.
Table 1-1 lists the HP Integrity server models, the console options, and relevant media choices.
Table 1-1 Installation matrix
GUI consolerx1620
rx2620
rx2660
rx3600
rx4640
rx6600
BL860c
BL870c
Cell-based servers
rx8620
rx8640
rx7640
Superdome
(sx1000 and
sx2000)
Headless console
Integrated Remote Console
(rx2660, rx3600, rx6600, BL860c,
and BL870c only)
PXE/RIS
GUI consolerx7620
Headless console
PXE/RIS
MediaConsoleServer
HP Smart Setup, HP Smart Update, and Microsoft Windows
Server 2003 with SP2
HP Reinstallation
HP Smart Setup, HP Smart Update, and Microsoft Windows
Server 2003 with SP2
HP Reinstallation
Virtual Media (vMedia) + HP Smart Setup, Smart Update,
Windows Server 2003 with SP2,
or HP Reinstallation
HP Smart Setup, HP Smart Update, and Microsoft Windows
Server 2003 with SP2
HP Reinstallation
HP Smart Setup, HP Smart Update, and Microsoft Windows
Server 2003 with SP2
HP Reinstallation
HP ReinstallationGUI console
HP ReinstallationHeadless console
Choosing an installation environment17
Choosing the Installation media
The HP Integrity Essentials Foundation Pack for Windows includes the HP Smart Setup media.
You can use the HP Smart Setup media both before and after you install the OS.
•Before installing the OS, boot the server with the Smart Setup media in the CD/DVD drive.
The server boots to the EFI-Based Setup Utility (EBSU). EBSU provides an easy-to-use
interface for offline setup and configuration tasks, such as creating hard disk partitions and
updating the firmware. Moreover, EBSU provides a utility called Express Setup, which
guides you through the process of installing the OS. EBSU works in conjunction with the
Microsoft media, which holds the OS image. HP strongly recommends that you use EBSU
to install the OS. For more information about EBSU, see Appendix B.
•After installing the OS, use the Smart Setup media to install drivers, utilities, and important
fixes to ensure the stability and performance of the system. You can also use Smart Setup
to browse the documentation for the server, including an electronic version of this document.
Then use the Smart Update media to update the server with critical operating system and
security QFEs from Microsoft.
Using the Microsoft OS media
You can purchase the Microsoft OS media either with the HP Integrity Essentials Foundation
Pack for Windows from HP or separately from a Windows reseller. Possibly your organization
already has a volume license for Windows Server 2003, Enterprise Edition with SP2 for
Itanium-based servers. You need this media and the license key to install Windows Server 2003
(if Windows is not factory-installed) on HP Integrity servers.
Using the HP Reinstallation media
HP Integrity servers factory-installed with Windows Server 2003 provide the HP Reinstallation
media, which you can use to restore the server to its factory condition if necessary. You must
have the corresponding license key to reinstall Windows Server 2003. The license key is found
on your server’s Certificate of Authenticity (COA).
Locating the Microsoft Certificate of Authenticity
The certificate contains the CD key for Microsoft Windows Server 2003. You must enter this key
as part of the installation procedure. The physical location of the Certificate of Authenticity
(COA) depends on the server model. Table 1–2 identifies the locations of COAs for supported
HP Integrity servers.
18Preparing for the installation
Table 1-2 Locating the Microsoft COA
LocationIntegrity Server
rx1620
rx2620
The COA is on the underside of the pullout strip located near the power switch, as shown
here (server is upside down in the image):
The COA is on a pullout strip located on the front of the system, adjacent to the hard drives,
as shown here:
The COA is located on the left side panel, in the middle, as shown here:rx2660
Locating the Microsoft Certificate of Authenticity19
Table 1-2 Locating the Microsoft COA (continued)
LocationIntegrity Server
The COA is located on the left side panel, as shown here:rx3600
The COA is located on the left side panel, as shown here:rx4640
BL860c and BL870c
The COA is located on the left side panel. It as shown here:rx6600
The COA is located on the left side panel. If there is more than one label on the side panel,
the COA is the one farthest left, as shown here:
20Preparing for the installation
Table 1-2 Locating the Microsoft COA (continued)
LocationIntegrity Server
rx7620 and rx7640
rx8620 and rx8640
The COA is located on the front of the system, above the light panel, next to the UUID label,
as shown in the first illustration that follows. Additional COAs are shown in the second
illustration.
The COA is located in the front of the system, at the bottom, near the power supply as shown
in the first illustration that follows. If additional COAs are required, they are located as shown
in the second illustration.
Superdome (sx1000
and sx2000)
The COA is located inside the unit, on the left, in the open space between the cells and the
extended I/O cabinet (IOX), as shown here:
Locating the Microsoft Certificate of Authenticity21
Setting up a console
If you are installing locally, you must set up your server with either a headless console or a GUI
console.
Set up a headless console
A headless console is a PC running terminal emulation software such as PuTTY (available on
the Smart Setup media or from the web) or HyperTerminal, that connects to the server through
its management processor (MP) serial port or LAN port. The headless console provides a method
for connecting to servers that do not have legacy VGA graphics or PS/2 keyboard and mouse
hardware installed on them. It is good practice to configure servers this way (without legacy
VGA or keyboard/mouse hardware) because they are easier to setup, maintain, and operate.
Figure 1-1 shows headless consoles connected to an HP Integrity rx4640 server.
Figure 1-1 Headless console configurations
When you use a headless console to install Windows, you can view detailed installation
information for each component by monitoring the setup log channels. See “Special Administration
Console” (page 94) for more information.
From the headless console, you can access the EFI Shell, the management processor (MP), and
the Microsoft Special Administration Console (SAC). You can use these utilities while installing
and administering Windows Server 2003 on HP Integrity servers. For more information about
the MP and SAC, see “Special Administration Console” (page 94).
You can configure a headless console in one of the following ways:
•Using a null modem cable
•Using a cat5 LAN cable
•Using a Remote Serial Console (applies to rx2660, rx3600, rx6600, BL860c, and BL870c servers
only)
The first two methods require a terminal emulation application such as HyperTerminal or PuTTY.
PuTTY is a free implementation of telnet and SSH for 32-bit Windows and UNIX. PuTTY provides
an X terminal. You must use PuTTY Version 0.59 or higher, available on the Smart Setup media
or from the PuTTY website at:
Set up the headless console using a null modem cable
To set up the headless console using a null modem cable, complete the following steps:
1.Connect the PC to the server MP serial port with a null modem cable.
22Preparing for the installation
2.Install PuTTY on the client PC and specify these port settings:
•Bits per second: 9600
•Data bits: 8
•Parity: none
•Stop bits: 1
•Flow control: Xon/Xoff
3.Use the Keyboard Configuration Panel to map the backspace key to Control + H.
4.Boot the server.
5.Run PuTTY and press Enter. The MP login prompt appears.
6.Enter your user name and password, and the MP command prompt appears.
7.Enter the CO command to access the headless console.
Set up the headless console using a LAN
To set up the headless console over a LAN, complete the following steps:
1.Connect the PC to the server LAN port with a cat5 cable.
2.Use telnet to access the MP. The MP login prompt appears.
3.Enter your user name and password, and the MP command prompt appears.
4.Enter the CO command to access the headless console.
Set up the headless console using a Remote Serial Console (rx2660, rx3600, rx6600, BL860c,
and BL870c only)
To set up the headless console (on rx2660, rx3600, rx6600, BL860c, and BL870c servers only) using
Remote Serial Console, complete the following steps:
1.Point a secure web browser at the name or IP address of the server MP.
2.Enter your user name and password to log in to the System Management Homepage.
3.On the Remote Console tab, and select Remote Serial Console in the left panel.
4.Click the Launch button and a new window appears, providing access to the headless
console.
Set up a GUI console
A GUI console is a VGA monitor, a USB HP keyboard, and a USB mouse connected to the server.
(You can use a USB-to-PS2 converter to connect to a console switch).
NOTE:If a VGA card is not already installed, you must install the HP Graphics and USB Combo
Card to use a GUI console. No other graphics card is supported by HP Integrity servers. Also,
only HP keyboards are supported with this card.
Figure 1-2 shows a GUI console connected to an HP Integrity rx4640 server.
Setting up a console23
Figure 1-2 GUI console configuration
A GUI console provides complete access to all the installation and administration tasks that you
can perform on the server. You can use the GUI console to prepare the server for installation,
install the OS, and check server status after installation.
On servers configured with an internal graphics card, you can connect a monitor, keyboard, and
mouse directly to the appropriate ports. On servers without an internal graphics card, you must
first install an HP Graphics and USB Combo Card and connect the console to the appropriate
ports. Then, from an existing headless console, modify system configuration to redirect the output
to the GUI console.
Table 1-3 Graphics support on server models
Graphics CardServer Model
Built-in video graphicsrx1620, rx2660, rx3600, rx4640, rx6600,
BL860c, BL870c
Optional HP Graphics and USB Combo Card (HP part number A6968A)rx7620, rx8620, Superdome/sx1000
Optional HP Graphics and US Combo Card (HP part number A6968B)rx7640, rx8640, Superdome/sx2000
To install the HP Graphics and USB Combo Card using the Legacy interface (black background),
complete the following steps:
1.Install the HP Graphics and USB Combo Card in an open PCI slot in the server.
2.Connect a VGA monitor, USB HP keyboard, and USB mouse to the appropriate ports.
3.Boot the server to EFI.
4.At the headless console, from the EFI Boot Manager, select Boot Option Maintenance Menu.
5.Select Select Active Console Output Devices.
6.Highlight the line with the graphics card PCI device.
If the line does not begin with an asterisk, the device is disabled. Use the space bar to toggle
the state of the card from disabled to enabled (as indicated by the asterisk).
7.Select Save Settings to NVRAM and then Exit. The video display is now directed to the
GUI console.
To install the HP Graphics and USB Combo Card using the Enhanced interface (grey background),
complete the following steps:
1.Install the HP Graphics and USB Combo Card in an open PCI slot of the server.
2.Connect a VGA monitor, USB HP keyboard, and USB mouse to the appropriate ports.
3.Boot the server to EFI.
4.From the EFI Boot Manager, select Boot Configuration.
5.Select Console Configuration.
24Preparing for the installation
6.Select Select Output Console.
7.Select the graphics card PCI device and press Enter. The video display is now directed to
the GUI console.
Set up an Integrated Remote Console (rx2660, rx3600, rx6600, BL860c, and BL870c
only)
The Integrated Remote Console (IRC) lets you use Windows clients running Internet Explorer
to remotely view and manage HP Integrity servers featuring the iLO 2 management processor.
This functionality is supported on rx2660, rx3600, rx6600, BL860c, and BL870c servers only.
The IRC combines keyboard, video, and mouse into a remote, virtual interface. Use it to view
the server’s display and directly interact with it. When you use IRC in combination with Virtual
Media (See “Set up a Virtual Media (vMedia) drive” (page 25)), you can perform remote GUI
installations of server operating systems and software. You can also use the IRC to perform server
maintenance tasks and run applications remotely that require keyboard and mouse input.
NOTE:You can use the Integrated Remote Console in place of the GUI Console method of
installation anywhere the GUI method is described in this document.
The IRC and vMedia features are enabled only after you have obtained and installed an iLO 2
MP Advanced Pack license (part number AB500A). If you are not licensed and try to use these
features, you see the message: iLO 2 feature not licensed. Free limited-term trial licenses
are also available.
For more information about the iLO 2 MP Advanced Pack licensing, or to obtain a free limited-term
license, go to:
Follow the factory installation or manual installation instructions located on the Integrated
Lights-Out Advanced Pack for HP Integrity Servers; Certificate of License to Use; License Installation
Card to activate your license.
This document is not intended to be a complete description of IRC or vMedia. For more
information about these powerful features, see the HP Integrity rx3600 and HP Integrity rx6600:Integrated Lights-Out 2 Management Processor Operations Guide at:
http://docs.hp.com/en/AD217-9001A/index.html or
http://docs.hp.com/en/AD217-9001A/AD217-9001A.pdf
To set up an Integrated Remote Console (on rx2660, rx3600, rx6600, BL860c, and BL870c servers
only), complete the following steps:
1.Point a secure web browser at the name or IP address of the server MP.
2.Enter your user name and password to log in to the System Management Homepage.
3.On the Administration tab, select Licensing in the left panel.
4.Enter the license number.
5.On the Remote Console tab, select Integrated Remote Console in the left panel.
6.Click the Launch button. If Launch is greyed out, the license might be invalid or expired.
A new window appears, providing access to the IRC.
Set up a Virtual Media (vMedia) drive
Virtual Media (vMedia) provides you with virtual devices that mimic physical hardware devices
just as if they were physically connected, such as a virtual CD/DVD drive that can connect through
a network to the managed server. The vMedia device can be a physical CD/DVD drive on the
management workstation, or it can be an image file stored on a local disk drive or network drive.
Floppy disk or USB memory devices are not supported.
Setting up a console25
Booting from the iLO 2 MP CD/DVD enables you to upgrade the host system ROM, upgrade
device drivers, deploy an OS from network drives, and perform disaster recovery of failed
operating systems, among other tasks.
The iLO 2 MP device uses a client/server model to perform the vMedia functions. The iLO 2 MP
device streams the vMedia data across a live network connection between the remote management
console and the host server. The vMedia Java™ applet provides data to the iLO 2 MP as required.
NOTE:You can use a vMedia drive in place of a local CD or DVD drive anywhere that a local
CD/DVD drive is described in this document.
To set up a vMedia drive (on rx2660, rx3600, rx6600, BL860c, and BL870c servers only), complete
the following steps:
1.Point a secure web browser at the name or IP address of the server MP.
2.Enter your user name and password to log in to the System Management Homepage.
3.On the Administration tab, select Licensing in the left panel.
4.Enter the license number.
5.On the Virtual Devices tab, select Virtual Media in the left panel.
6.Click the Launch button. If Launch is greyed out, the license might be invalid or expired.
A new window appears, providing access to Virtual Media. Do on of the following actions:
•Select Local Media Drive, specify the CD or DVD drive on your client machine, and
insert the CD or DVD into that drive.
•Select Local Image File, and specify the ISO image of the desired CD or DVD.
7.Click Connect. The server now detects a new USB drive attached to it. This is the vMedia
drive.
Setting up PXE/RIS
A Remote Install Server (RIS) is a specialized Windows server used to perform multiple software
installations across a network. The RIS server, working in conjunction with an agent (the PXE
client) residing on target systems, performs automated installations. This method of installation
offers the following advantages:
•Installations are automated; no user intervention is needed
•You can install multiple servers in one batch job
•Each server receives a standardized image
•You can perform an installation from anywhere on the intranet
Figure 1-3 shows a sample PXE/RIS setup.
26Preparing for the installation
Figure 1-3 PXE/RIS configuration
NOTE:When you perform a PXE/RIS headless installation, note the following:
•Headless installations using PXE/RIS are not supported with Windows Server 2003,
Datacenter Edition. Use the HP Reinstallation media instead.
•Do not connect the RIS server to the Integrity server using your intranet during initial
Windows OS installation. Set up a small private network, populated with the RIS server, a
hub, and the system LAN NIC of the HP Integrity server. This protects the intranet from
errors that might occur during the Windows installation process. When the Windows OS
installation has completed, connect the RIS to the target Integrity servers using your intranet.
Remote Installation Services (RIS) enables you to create, maintain, and quickly install identical
OS and software configurations on multiple headless systems with a predefined level of user
interaction. RIS uses the preboot execution environment (PXE) to enable client computers without
an operating system to boot remotely to a RIS server. The RIS server then installs the operating
system over a TCP/IP network connection. You can create different sets of RIS images for different
groups of client computers. You can also use Group Policy settings to limit the installation options
that RIS presents to clients. In addition, you can configure RIS for either interactive or fully
automated installations.
Set up a RIS server
Setting up one or more RIS servers in your network requires careful planning, design, and
implementation. The following checklist provides an overview of the tasks involved in setting
up a RIS server:
•Ensure that both your RIS server and client (Integrity server) hardware meet the Remote
Installation Services (RIS) hardware requirements. The server hardware must meet the
minimum requirements for the version of Windows Server 2003 that you are installing.
•Ensure that your network is based on TCP/IP, and that a Domain Name System (DNS) server
exists on the network. You do not need to use the Microsoft version of DNS.
•Ensure that a Dynamic Host Configuration Protocol (DHCP) server exists on the network.
You do not need to use the Microsoft version of DHCP.
•Ensure that Active Directory exists on the network.
Setting up PXE/RIS27
Install RIS
•Install the RIS component on the RIS server.
•Run the RIS Setup Wizard.
See Also
For detailed descriptions of the concepts, tasks, best practices, and troubleshooting tips for setting
up a RIS server, see the Microsoft Windows Server 2003 Technical Reference website:
You can install RIS either using the Control Panel or through an unattended Setup answer file.
To install using Add or Remove Programs, complete the following steps:
1.Go to Start > Settings > Control Panel, then double-click Add or Remove Programs and
select Add/Remove Windows Components to install the RIS component.
2.Open the RIS Setup Wizard and click Next. The RIS Setup wizard prompts you for
information about specific settings used in the RIS installation. The wizard prompts you to
do the following:
1.a. Enter the disk drive and directory to install RIS. The disk must be dedicated to the
RIS server with a recommended minimum 4 GB of space.
2.b. Select Respond to client computer requesting service. The RIS server begins
responding to client computers when the wizard is complete. Select Do not respondto unknown client computers if you want the RIS server to respond only to prestaged
client computers in Active Directory.
3.c. Enter the location of the client images. This can be either the Windows Server 2003
Enterprise Edition with SP2 CD or a shared folder on the network that contains the
installation files.
4.d. Enter help text that describes the operating system installation choices to users or
clients of RIS.
Configure RIS
After the Remote Installation Services Setup Wizard completes, depending on the settings chosen,
the RIS server either services client computers or pauses while you configure advanced settings
using the RIS administration settings. The following list describes the available configuration
options.
•Specify which RIS servers are allowed to run on your network. This option prevents
•Use the Active Directory Users and Computers snap-in to set properties on individual RIS
•Use Group Policy to specify which installation options are presented to different groups of
•Use security descriptors or discretionary access control lists (ACLs) to specify which users
unauthorized (often referred to as rogue) RIS servers, ensuring that only those RIS servers
authorized by administrators can service clients. If an attempt is made to start an
unauthorized RIS server on the network, it will be shut down automatically and thus unable
to service client computers. A RIS server must be authorized before it can service client
computers.
servers that control how the server supplies RIS to requesting clients. To access the snap-in
go to Start > Programs > Administrative Tools, and then clicking Active Directory Usersand Computers.
users by the Client Installation wizard (CIW). For example, you can choose to allow a group
of users access only to the automatic setup option, and restrict access to all other options to
administrators.
or group of users can have access to the operating system images available on the RIS server.
You can use this method to guide users through the selection of the unattended OS installation
28Preparing for the installation
appropriate for their account privileges. By default, when an operating system image is
added to a RIS server, the image is available to all users serviced by that RIS server.
To configure settings for new clients for RIS, complete the following steps:
1.Open Active Directory Users and Computers.
2.In the console tree, go to Active Directory Users and Computers > Applicable domain> Applicable organizational unit (such as Computers/Applicable RIS server) and right-click
the applicable RIS server.
3.Click Properties. In the Properties dialog box, go to the Remote Install tab and click
Advanced Settings.
4.In the Advanced Settings dialog box, go to the New Clients tab.
5.Select the client computer naming format you want to use, or click Customize to create a
client computer naming format.
6.To specify where to create the client computer account, click one of the following options:
•Default directory service location
•Same location as the user setting up the client computer
•The following directory service location
7.If you choose the last option, click Browse and specify where to create the computer accounts.
Authorize a RIS server in Active Directory
A RIS server must be authorized in Active Directory to be able to respond to clients requesting
service. If RIS is installed on a server that is not an authorized DHCP server, or added to a DHCP
server that is not authorized in Active Directory, you must complete the following steps:
1.Log in to the domain in which the RIS server resides. (The account you use must be a member
of the Enterprise Admins group.)
2.From the Start menu, point to Programs and Administrative Tools and click DHCP from
the list. This starts the DHCP Management snap-in.
3.Right-click the DHCP root node in the scope pane, and then click Manage AuthorizedServers.
4.Click Authorize, enter the IP address or name of the RIS server, and then click OK. When
prompted to ensure that this is the correct RIS server to authorize, click Yes.
The server will not respond to client requests until the changes to Active Directory have taken
effect. For these rights to apply immediately, on the domain controller on which your rights have
been set, complete the following steps:
1.On the Start menu, click Run.
2.Enter the cmd command.
3.At the command prompt, enter:
secedit /refreshpolicy /MACHINE_POLICY
Use the Client Installation Wizard
The following installation options are included in the Client Installation Wizard (CIW). Automatic
setup is available by default. RIS uses Group Policy settings to allow access to the automatic
setup option only, and to restrict all users and administrators from the rest of the installation
options described in the following list:
•Automatic Setup—This option allows you to select which operating system to install, but it
does not prompt you for specific configuration settings. If only one operating system option
is offered, you are not prompted, and an unattended installation of the operating system
image starts automatically.
•Custom Setup—This option allows you to override the automatic computer naming process
and the default location within the Active Directory where client computer accounts will
Setting up PXE/RIS29
Loading...
+ 67 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.