Hp ProLiant Essentials Rapid Deployment Pack Installation Guide

HP ProLiant Essentials Rapid Deployment Pack

Installation Guide

Part number 352869-402 Eleventh edition August 2007 Product version: 3.70

Legal notices

and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Windows Server 2003 is a U.S. trademark of Microsoft Corporation. AMD is a trademark of Advanced Micro Devices, Inc. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

Product version: 3.70

1 Licensing .....................................................................................................................................4

Licensing options ..................................................................................................................................... 4

Obtaining licenses ................................................................................................................................... 4

Evaluation licenses .............................................................................................................................. 4

Purchased licenses .............................................................................................................................. 5

Applying a license file .............................................................................................................................. 5

Applying license files during a first-time installation.................................................................................. 5

Applying license files during an upgrade installation ............................................................................... 5

Adding licenses to an existing installation .............................................................................................. 5

Replacing licenses in an existing installation........................................................................................... 6

2 Prerequisites................................................................................................................................. 7

Network infrastructure requirements ........................................................................................................... 7

Deployment Server requirements ................................................................................................................ 7

3 Installing...................................................................................................................................... 8

Getting started......................................................................................................................................... 8

Before you upgrade ................................................................................................................................. 8

Installing................................................................................................................................................. 8

4 HP support and contact information ..............................................................................................25

Related documents ................................................................................................................................. 25

Online resources.................................................................................................................................... 25

HP contact information ........................................................................................................................... 26

HP Software Technical Support and Update Service ................................................................................... 27

Appendix A Manually installing distribution files......................................................................................28

Appendix B Manually modifying configuration settings............................................................................. 29

Synchronize display names with computer names option ............................................................................29

Primary lookup key option....................................................................................................................... 30

PXE initial deploy boot timeout option....................................................................................................... 31

Client/server file transfer port option ........................................................................................................ 32

Creating an IIS FTP virtual directory option................................................................................................ 33

Windows product keys ........................................................................................................................... 34

Appendix C Installing an IIS FTP server ...................................................................................................35

Appendix D Creating and using automation boot media...........................................................................36

Index ..................................................................................................................................................37

Contents 3

1 Licensing

A license enables a server, either a physical server or a virtual machine, to be deployed and managed by the Altiris Deployment Server. One license is required for each server being managed. After a license is applied to a specific server, the license cannot be removed or transferred to another server.

A license file contains licenses for a predetermined number of servers. License files are not Rapid Deployment Pack version-specific.

Licensing options

The Rapid Deployment Pack offers five license purchasing options:

• One-node license—This license enables you to deploy and manage one server through the

Deployment Server.

• Ten-node license—This license enables you to deploy and manage 10 servers through the

Deployment Server.

• Flexible Quantity license—This options enable you to obtain an exact quantity of licenses in the

purchase of a single software option kit.

• Activation Key Agreement—This option enables you to order keys in the quantity desired for a

specific time and purchase a license for each server deployed over time.

• HP BladeSystem enclosure group—This option offers a bundle of 8 or 20 licenses with an

HP BladeSystem enclosure.

For more information about the Flexible Quantity license and Activation Key Agreement options, see ProLiant Essentials Licensing at http://www.hp.com/servers/rdp

Obtaining licenses

The following sections explain how to obtain evaluation or purchased licenses for your servers.

Evaluation licenses

Two types of evaluation licenses are available:

• A 10-node, 7-day evaluation license is built into the Deployment Server. No license file is

required. The evaluation license can be applied during the Deployment Server installation.

• A 10-node, 30-day evaluation license. To obtain and use this license:

a. Access http://www.hp.com/servers/rdp/eval. b. Follow the online instructions to complete the registration process. An evaluation license file is

emailed to you.

Licensing 4

Purchased licenses

Use your unique product registration number to obtain a license file. A 16-character alpha or 20-character alphanumeric registration number is located on a label on the outside back panel of a purchased software packaging box. The registration number is in the format:

xxxx-xxxx-xxxx-xxxx or xxxxx-xxxxx-xxxxx-xxxxx

IMPORTANT: Keep your product registration number for future reference.

1. Access http://www.hp.com/servers/rdp/register.

2. Follow the online instructions to complete the registration process. A license file is emailed to

you.

Additional purchased licenses can be transferred or combined with already-registered licenses. See the instructions at http://www.hp.com/servers/rdp/register

Applying a license file

The following sections explain how to apply evaluation or purchased licenses to your servers and how to add or replace existing licenses.

To view the number of licensed nodes from the console, select Help>About.

Applying license files during a first-time installation

A 10-node, 7-day evaluation license is built into the Deployment Server. To apply this license, select Free 7 day license during a first-time installation on the Deployment Share Information screen.

To apply a purchased or evaluation license file, enter the path to the license file in the License File field during the installation on the Deployment Share Information screen.

Applying license files during an upgrade installation

To continue using existing licenses after performing an upgrade, select Upgrade using existing license during the installation on the Deployment Share Information screen.

Adding licenses to an existing installation

To apply additional purchased licenses to an existing installation, add the new license file to your Deployment Server.

1. Shut down all connections to the Deployment Server Console and Deployment Server Web

Console.

2. Run the Altiris Product Licensing Utility by clicking Start>Programs>Altiris>Deployment Solution>

Product Licensing Utility.

3. Enter the path to the new license file in the Activation Key File Information field, and then click

Next.

4. Follow the online instructions to apply your additional licenses.

Licensing 5

Replacing licenses in an existing installation

If you have previously purchased, returned, or transferred licenses and have obtained a new license file to replace your existing license file:

1. Shut down all connections to the Deployment Server Console and Deployment Server Web

Console.

2. Run the Altiris Product Licensing Utility by selecting Start>Programs>Altiris>Deployment Solution>

Product Licensing Utility.

3. Enter the path to the new license file in the Activation Key File Information field, and then click

Next.

4. Follow the online instructions to apply your licenses, and select Replace all existing license

Activation Keys with this new Activation Key checkbox.

Licensing 6

2 Prerequisites

Network infrastructure requirements

If PXE will be used to perform remote deployment of servers, then DHCP must be installed and accessible on the network prior to the installation.

Deployment Server requirements

• Hardware

○ 2+ processors in ProLiant G3 or G4 server with 2 GB RAM or an equivalent virtual machine ○ The correct date and time

NOTE: A virtual machine should only be used for demonstration or very small environments.

• Microsoft® Windows® operating system:

○ Microsoft Windows Server™ 2003 x86 (SP1, R2, SP2) Standard or Enterprise Editions

NOTE: The server must not be a domain controller.

• Available disk space:

○ 2 GB for the base installation ○ 1 GB for each Windows distribution ○ 1 GB for each VMware ESX distribution ○ 4 GB for each Linux distribution ○ Additional space to store any captured disk images and software packages

• A network connection configured with a static IP address

NOTE: Changing the IP address configuration after installation is difficult, therefore, set the

appropriate IP address before beginning the install.

• To use the Deployment Server Web Console, IIS with ASP.NET must be installed.

• To deploy VMware ESX or Linux, an FTP server must be installed. For information on installing

Microsoft IIS FTP server, see “Appendix C Installing an IIS FTP server.”

For more information about requirements for the Deployment Server, see the Altiris Deployment Solution 6.8 SP2 Deployment and Migration Guide at http://www.hp.com/servers/rdp

Prerequisites 7

3 Installing

Getting started

• The Rapid Deployment Pack cannot be installed through a Terminal Services, remote shell, or

network share connection.

• Obtain a license file (either purchased or evaluation).

• Collect the applicable Windows, VMware ESX, or Linux distribution files.

• Get the applicable Windows product keys.

Before you upgrade

• The Rapid Deployment Pack upgrade must be completed using the Rapid Deployment Pack

autorun utility.

• If you have modified any provided jobs or batch files, verify that you have made backup copies

before upgrading.

• If you are using Deployment Server Console security, disable it before starting the upgrade, and

then re-enable it after the upgrade is complete.

• Shut down all connections to the Deployment Server Console and Deployment Server Web

Console.

Installing

1. Access the Rapid Deployment Pack autorun utility by performing one of the following tasks, and

executing autorun.exe:

a. Insert the physical DVD into the DVD drive. b. Extract the ISO image to the intended Deployment Server. c. Mount the ISO image.

2. Read the terms of the ProLiant Essentials End User License Agreement (EULA), and click Agree.

3. Read the overview information, and click Next.

4. Review the preinstallation step, and click Next.

Installing 8

Verify that the appropriate components are selected for installation, and click Install. If Microsoft .NET Framework and Microsoft SQL Server are not installed on the server, these components are automatically selected. If you plan to use an existing database, clear the

Microsoft SQL Server 2005 Express option.

6. Wait while Microsoft .NET Framework and Microsoft SQL Server are installed.

7. If the Altiris Deployment Server was selected for installation, read the Altiris EULA, and click Yes.

If the Altiris Deployment Server was not selected for installation, proceed to step 24.

8. If the server has multiple network adapters, select the appropriate interface for the Deployment

Server, and click Select IP.

Installing 9

Select the appropriate licensing option, and click Next. For more information about licensing, see the “Licensing” section in this guide.

○ If installing for the first-time, select Free 7 day license, or select License file, and enter the

license file path and name.

○ If upgrading, verify that Upgrade using existing license is selected.

NOTE: When upgrading, you must select Upgrade using existing license to avoid losing

existing licenses.

Installing 10

10.

Enter the service credentials for the Deployment Server, and click Next.

NOTE: Do not install the Deployment Server component to a remote server because it causes

the Integration Module installations to fail.

Installing 11

11.

Select the name of the server instance where you want to install the database, and click Next.

12. If the database is located on a remote server, you might be prompted for credentials. Enter a

username and password with administrative rights.

13. Enter the appropriate database authentication method, and click Next.

Installing 12

14.

If upgrading, click Yes when prompted to retain the data in the existing database.

15. On the Pre-boot Operating Systems screen, click Next.

NOTE: Linux and Windows PE are the only automation environments supported with the Rapid

Deployment Pack 3.00 or later. The MS-DOS preboot environment is no longer supported.

Installing 13

16.

Specify the location where PXE Server is to be installed, and click Next. If you choose not use PXE, then see “Appendix D Creating and using automation boot media.”

17. If DHCP is installed on a separate server, click OK when prompted that DHCP services are

required.

Installing 14

18.

Specify how clients connect to the Deployment Server, and click Next.

Installing 15

19.

Specify the location where the Deployment Server Console is to be installed, and click Next.

Installing 16

20.

Specify if and where the Deployment Server Web Console is to be installed, and click Next.

Installing 17

21.

On the Installation Information screen, click Install.

22. If upgrading, click Yes when prompted to replace the eXpress share.

23. When the installation is complete, click Finish.

24. If ProLiant Integration Module software was selected for installation, on the Prerequisites screen,

click Verify. If ProLiant Integration Module software was not selected, proceed to step 34.

25. When the verification process is complete, click Next.

Installing 18

26.

Select the operating systems that are to be deployed to target servers, and click Next.

Installing 19

27.

Specify the appropriate configuration options, and click Next. If you are not using an IIS FTP server for VMware ESX or Linux installations, clear the Create IIS FTP virtual directory “DSLIB” option. For more information, see “Appendix B Manually modifying configuration settings.”

28. On the Installation and Configuration screen, click Install

29. If upgrading, click OK when prompted to back up and overwrite existing configuration files and

reimport existing jobs.

Installing 20

30.

For each operating system that was selected and that is not present, specify the root directory of the distribution files, and click Copy. If you choose to skip copying any distribution, see “Appendix A Manually installing distribution files.”

31. If you are prompted to reinsert the Rapid Deployment Pack media, reinsert it, and click OK.

32. If you skipped any distributions, click OK when the warning message appears.

33. On the Installation and Configuration screen, click Finish.

Installing 21

34.

If the Integrity Integration Module software was selected for installation, on the Prerequisites screen, click Verify. If Integrity Integration Module software was not selected, proceed to step

44.

35. When the verification process is complete, click Next.

36. Select the operating systems that are to be deployed to target servers, and click Next.

Installing 22

37.

Specify the appropriate configuration options, and click Next. If you are not using an IIS FTP service for Linux installations, clear the Create IIS FTP virtual directory “DSLIB” option. For more information, see “Appendix B Manually modifying configuration settings.”

38. On the Installation and Configuration screen, click Install.

39. If upgrading, click OK when prompted to back up and overwrite existing configuration files and

reimport existing jobs.

40. For each operating system that was selected and that is not present, specify the root directory of

the distribution files, and click Copy. If you choose to skip copying any distribution, see Appendix A Manually installing distribution files.”

41. If you are prompted to reinsert the Rapid Deployment Pack media, reinsert it, and click OK.

42. If you skipped any distribution, click OK when the warning message appears.

43. On the Installation and Configuration screen, click Finish.

Installing 23

44.

On the autorun utility, click Next.

45. Review the post-installation step, and click Finish.

46. Select Yes when prompted to reboot the server.

The installation is complete. For configuration instructions, see chapter 1 of the HP ProLiant Essentials Rapid Deployment Pack User

Guide.

Installing 24

4 HP support and contact information

Online resources

• Information about the Rapid Deployment Pack and the latest updates are available from the

HP ProLiant Essentials Rapid Deployment Pack website at http://www.hp.com/servers/rdp

• Problem-solving information and ideas from other IT professions are available in the IT Resource

Center (ITRC) User Forum “ProLiant Deployment & Provisioning.” This forum is accessible from the Management Software and System Tools link at http://forums.itrc.hp.com

• Information and resources about the Altiris Deployment Solution is available from the Altiris

website at http://www.altiris.com

and at \docs on the product

HP support and contact information 25

HP contact information

For the name of the nearest HP authorized reseller:

• In the United States, see the HP U.S. service locator webpage at

http://www.hp.com/service_locator

• In other locations, see the Contact HP worldwide webpage at

http://welcome.hp.com/country/us/en/wwcontact.html

For HP technical support:

• In the United States, for contact options see the Contact HP United States webpage at

http://welcome.hp.com/country/us/en/contact_us.html

○ Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days

a week. For continuous quality improvement, calls may be recorded or monitored.

• In other locations, see the Contact HP worldwide webpage at

http://welcome.hp.com/country/us/en/wwcontact.html

. To contact HP by phone:

HP support and contact information 26

HP Software Technical Support and Update Service

HP ProLiant Essentials Rapid Deployment Pack now includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP technical resources for help in resolving software implementation or operations problems. The service also provides access to software updates and reference manuals either in electronic form or on physical media, as they are made available from HP.

With this service, HP ProLiant Essentials Rapid Deployment Pack customers benefit from expedited problem resolution and proactive notification and delivery of HP ProLiant Essentials Rapid Deployment Pack software updates.

To activate your HP Software Technical Support and Update Service for HP ProLiant Essentials Rapid Deployment Pack, you must register your software purchase through the HP website at

http://www.hp.com/go/insightcontrolregistration

Failure to register your service will jeopardize service fulfillment.

Your Service Agreement Identifier (SAID) will be delivered to you after registration. After you have received your SAID, you can go to the software update manager (SUM) web page to view your contract and elect electronic delivery (in addition to standard media-based updates). For more information about this service, see http://www.hp.com/services/insight

In addition to the new Software Technical Support and Update Service, HP also offers a number of additional software support services, many of which are provided to our customers at no additional charge.

• Warranty—HP will replace defective delivery media for a period of 90 days from the date of

purchase. This warranty applies to all Insight Control Management, HP Systems Insight Manager, and ProLiant Essentials products.

• Startup technical software support—Phone support is available to help you with basic installation

and setup and standard usage questions. This support is provided by the knowledgeable HP Insight Control Management and Systems Insight Manager specialists’ team and is available for no additional charge up to 90 days from the date of purchase of your server. For support in the U.S., call 1-800-HP-INVENT (1-800-474-6836). (When prompted, say "Insight Manager, P2P, and SMP.") HP Worldwide support numbers for HP SIM, P2P, and SMP are available at

http://www.hp.com/country/us/en/wwcontact.html

• Join the discussion (http://forums.itrc.hp.com)—The HP Support Forum is a community-based,

user-supported tool for HP customers to participate in discussions amongst the customer community about HP products. For discussions related to Insight Control and ProLiant Essentials software, see the “Management Software and System Tools” area.

• Software and Drivers download pages (http://www.hp.com/support)—These pages provide

latest software and drivers for your ProLiant products.

• Management Security (http://www.hp.com/servers/manage/security)—HP is proactive in its

approach to the quality and security of all its management software. Be sure to check this website often for the latest downloadable security updates.

• Obtain the latest SmartStart (http://www.hp.com/servers/smartstart)—The SmartStart,

Management, and Firmware CDs are now freely available for download following a simple registration from the SmartStart web site. If you wish to receive physical kits with each release, order single release kits from the SmartStart website. To receive proactive notification when SmartStart releases are available, subscribe to Subscriber's Choice at

http://www.hp.com/go/subscriberschoice

HP support and contact information 27

Appendix A Manually installing distribution files

If you did not copy the Windows, VMware, or Linux distribution files during the installation, you must manually copy the files for the scripted install jobs to function properly. Manually copying the distribution files produces the same results as copying the files during the installation.

To manually copy the distribution files, copy the entire contents of each distribution CD or DVD to the appropriate .\lib\osdist\yyyy directory, where yyyy indicates the operating system shortcut name.

Table 1 Operating system directory names

Operating system Directory name

Windows 2000 - Advanced Server w50as

Windows 2000 - Server w50s

Windows 2003 - Enterprise Edition w52e

Windows 2003 - Standard Edition w52s

Windows 2003 - Web Edition w52w

Windows 2003 x64 - Enterprise Edition w52e.64

Windows 2003 x64 - Standard Edition w52s.64

Windows 2003 IA64 - Enterprise Edition w52e.ia64

VMware ESX Server 2.5.3 vmesx253

VMware ESX Server 3.0.2 vmesx302

Red Hat Enterprise Linux AS 4 Update 5 for x86 rhas4u5

Red Hat Enterprise Linux ES 4 Update 5 for x86 rhes4u5

Red Hat Enterprise Linux AS 4 Update 5 for AMD64 and Intel® EM64T rhas4u5.64

Red Hat Enterprise Linux ES 4 Update 5 for AMD64 and Intel EM64T rhes4u5.64

Red Hat Enterprise Linux AS 4 Update 5 for Intel Integrity rhas4u5.ia64

Red Hat Enterprise Linux ES 4 Update 5 for Intel Integrity rhes4u5.ia64

Red Hat Enterprise Linux 5 for x86 rhel5

Red Hat Enterprise Linux 5 for AMD64 and Intel EM64T rhel5.64

Red Hat Enterprise Linux 5 for Intel Integrity rhel5.ia64

SUSE Linux Enterprise Server 10 Service Pack 1 for x86 sles10sp1

SUSE Linux Enterprise Server 10 Service Pack 1 for AMD64 and Intel EM64T sles10sp1.64

SUSE Linux Enterprise Server 10 Service Pack 1 for Intel Integrity sles10sp1.ia64

Appendix A Manually installing distribution files 28

Appendix B Manually modifying configuration settings

Synchronize display names with computer names option

The Deployment Server can use a console display name that is different from the actual computer name. However, you can select to have the console always reflect the same name as the computer name.

To manually enable synchronization of the display and computer names:

1. In the Deployment Server Console, select Tools>Options.

2. From the Program Options screen, click the Global tab.

3. Select the Synchronize display names with computer names checkbox.

4. Click OK.

Appendix B Manually modifying configuration settings 29

Primary lookup key option

The Deployment Server uses the primary lookup key to determine if a server is already in the database. HP recommends setting the primary lookup key as the server serial number. Setting the primary lookup key as the server serial number has two benefits:

• It enables servers to be imported by their serial number, rather than keys that are more difficult to

determine, such as the MAC address.

• It prevents duplicate database entries from occurring when servers have two or more NICs.

To manually set the primary lookup key to serial number:

1. In the Deployment Server Console, select Tools>Program Options.

2. From the Program Options window, click the Global tab.

3. From the Primary lookup key dropdown list, select Serial Number.

4. Click OK.

Appendix B Manually modifying configuration settings 30

PXE initial deploy boot timeout option

By default, when a new computer (a computer not listed in the Deployment Server database) performs a PXE boot, the PXE server sends the computer the PXE menu and waits for manual selection of the Initial Deployment option. This process is not practical for servers, especially server blades with no local keyboard, mouse, or display.

To manually change the Initial Deploy boot option:

1. In the Deployment Server Console menu, and select Tools>PXE Configuration.

2. Click the DS tab.

3. Select Use default timeout.

4. Click Save, and then click OK.

Appendix B Manually modifying configuration settings 31

Client/server file transfer port option

For adlagent to properly transfer files under VMware ESX 3.x, the client/server file transfer port must be set to match the value in the supplied ESX kickstart files.

To manually set the client/server file transfer port to 4300:

1. In the Deployment Server Console, select Tools>Program Options.

2. From the Program Options window, click the Global tab.

3. Select the Client/server file transfer port checkbox, and enter 4300.

4. Click OK.

Appendix B Manually modifying configuration settings 32

Creating an IIS FTP virtual directory option

For VMware ESX and Linux scripted installation deployments, a virtual directory must be configured on an FTP server, such as IIS.

If you use an FTP server other than IIS, use the same entry settings. To manually configure IIS FTP:

1. Launch the Internet Information Services (IIS) Manager.

2. Expand the directory in the left pane, and select Default FTP Site or another existing FTP site.

3. Right-click the FTP site, and select New>Virtual Directory.

4. Complete the Virtual Directory wizard, entering the following information when prompted.

Table 2 Virtual directory information

Field Entry

Virtual Directory Alias DSLIB

FTP Site Content Directory

Virtual Directory Access Permissions

This value assumed that the Deployment Server was installed on the C drive.

5. Right-click the FTP site, and select Properties.

6. Click the Security Accounts tab.

7. Select Allow Anonymous Connections, and click OK.

8. If the FTP site name is followed by “(Stopped),” right-click the site name, and select Start.

C:\Program Files\Altiris\eXpress\Deployment

Server\lib

Read

Appendix B Manually modifying configuration settings 33

Windows product keys

For Windows scripted installation deployments, a Windows product key must be provided. To manually configure or reconfigure the Windows product keys:

1. In the Deployment Server Console, select Tools>Integration Module>User Tokens Editor.

2. Add or edit the appropriate entry.

3. Click Save.

Table 3 User Tokens table entries

Name Value

w50productkey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

w52productkey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

w52.64productkey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

w52.ia64productkey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Appendix B Manually modifying configuration settings 34

Appendix C Installing an IIS FTP server

To install an IIS FTP server:

1. Log in to the Deployment Server as a user with administrator rights.

2. Click Start>Control Panel>Add/Remove Programs.

3. Click Add/Remove Windows Components.

4. Select Application Server, and click Details.

5. Select Internet Information Services (IIS), and click Details.

6. Select File Transfer Protocol (FTP) Server, and click OK.

7. Click OK again.

8. Click Next.

Appendix C Installing an IIS FTP server 35

Appendix D Creating and using automation boot media

If you choose not to use PXE in your deployment infrastructure, you must create automation boot media for each automation environment that you will be using. The boot media boots a target server to automation without leaving any files on the server, and can be installed to DVDs, CDs, or USB keys. Using the Boot Disk Creator utility to create boot media is a straightforward process. However, remember:

• On the Create Configuration step, from the OEM Extensions dropdown, select all to include the

latest HP drivers.

• On the Network Adapters step, for WinPE select Auto-detect all network adapters, and click

Next. For LinuxPE, do not select any drivers, just click Next.

• When creating USB keys, select Detect as last disk.

• When creating USB keys for Integrity target servers, insert the key into the server, create an EFI

boot entry for it, and name it Altiris Automation.

Other considerations when using boot media:

• If a job uses multiple automation environments, on the target server, you must swap automation

boot media at the appropriate time during the execution of the job.

• After an upgrade, you must recreate all of your boot media to pick up the latest HP support.

Appendix D Creating and using automation boot media 36

Index

adding licenses, 5 Altiris

Boot Disk Creator, 29 installing, 9

Product Licensing Utility, 5 applying licenses, 5 Applying a license file, 5

boot diskette, creating, 29

client connection, 9 components, 7 configuring

options, 10, 33

Preboot eXecution environment, 35

predeployment, 29 console, installation location, 9 contact information, 30 creating

boot diskette, 29

FTP virtual directory, 11, 37 credentials

database, 9

service, 9

database

credentials, 9

retaining, 10 Deployment Server

client connection, 9

configuration, 33

installing, 9

requirements, 7

setting primary lookup key, 34 Deployment Server Console, installation location, 9 display names, synchronizing, 33 drive mapping, default, 29

evaluation licenses, 4

FTP service

installing, 39, 40 requirements, 7

Getting started, 11

hardware, requirements, 7 HP authorized reseller, 30 HP Software Technical Support and Update Service, 31

installation location

console, 9 PXE server, 10 Web Console, 10

installing

Altiris, 9 Deployment Server, 9 FTP server, 39, 40 jobs, 10 Microsoft .NET Framework, 9 operating system CDs/DVDs, 11, 32 prerequisites, 9 ProLiant Integration Module, 10 software, 9

Installing, 11

jobs

overwriting, 11 selecting, 10

license, 4 licenses

adding, 5 agreement, 9 applying, 5

Index 37

evaluation, 4

obtaining, 4

options, 4, 9

purchased, 5

replacing, 6 Licensing, 4

Microsoft .NET Framework, installing, 9 Microsoft Internet Information Services

creating an FTP virtual directory, 37

installing an FTP server, 39, 40

requirements, 7

network requirements, 7

obtaining licenses, 4 online resources, 29 operating system

installing CDs/DVDs, 11

requirements, 7

selecting deployment jobs, 10 options

configuration, 10, 33

licensing, 4, 9

physical boot diskette, creating, 29 post-installation steps, 29 Preboot eXecution Environment

configuring, 35

installation location, 10

PXE Configuration Utility, 35 predeployment steps, 29 Preinstallation steps, 29 prerequisites

installing, 7, 9

ProLiant Integration Module, 10 primary lookup key, setting, 34 product keys, 11, 38 ProLiant Integration Module

configuring, 10

installing, 10

purchased licenses, 5 PXE. See Preboot eXecution Environment

related documents, 29 replacing licenses, 6 requirements

Deployment Server, 7 installing, 9 network, 7 ProLiant Integration Module, 10

serial number, setting as primary lookup key, 34 service credentials, 9 setting primary lookup key, 10, 34 setting PXE initial deploy boot option, 10, 35 software

components, 7 installing, 9

requirements, 7 SQL Server, accessing, 9 synchronizing display names, 10, 33

troubleshooting, 29

upgrade

before you upgrade, 11 Upgrading, 29

virtual directory, creating, 37 VMware

installing operating system CDs/DVDs, 11, 32

selecting deployment jobs, 10

Web Console, installation location, 10 Windows

entering product keys, 11, 38

installing operating system CDs/DVDs, 11, 32

selecting deployment jobs, 10

synchronizing name, 33

Index 38

Hp ProLiant Essentials Rapid Deployment Pack Installation Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

1 Licensing

Licensing options

Obtaining licenses

Evaluation licenses

Purchased licenses

Applying a license file

Applying license files during a first-time installation

Applying license files during an upgrade installation

Adding licenses to an existing installation

Replacing licenses in an existing installation

2 Prerequisites

Network infrastructure requirements

Deployment Server requirements

3 Installing

Getting started

Before you upgrade

Installing

4 HP support and contact information

Related documents

Online resources

HP contact information

HP Software Technical Support and Update Service

Appendix A Manually installing distribution files

Appendix B Manually modifying configuration settings

Synchronize display names with computer names option

Primary lookup key option

PXE initial deploy boot timeout option

Client/server file transfer port option

Creating an IIS FTP virtual directory option

Windows product keys

Appendix C Installing an IIS FTP server

Appendix D Creating and using automation boot media

Index