HP ProLiant Essentials Rapid Deployment Pack

User Guide

Part number 315378-402 Eleventh edition August 2007 Product version: 3.70
Legal notices Copyright 2001, 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 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. Product version: 3.70

Contents

1 Configuring the Rapid Deployment Pack... 5
Configuring BladeSystem enclosures.... 5 Configuring image installs.... 6 Configuring imaging jobs.... 6 Configuring Windows Sysprep jobs.... 6 Configuring scripted installs..... 7 Configuring scripted install jobs... 7 Configuring SAN-attached scripted install jobs... 7 Configuring Boot from SAN scripted install jobs... 8 Connecting server blades.... 9 Creating a reference server and image.... 12 Deploying a captured image to other similar servers... 14 Reconfiguring the new servers..... 15 Maintaining server blades with rip-and-replace... 17 Performing a Boot from SAN installation.... 18 Jobs...... 20 Job default settings.... 21 Hardware configuration settings.... 21 Operating system scripted install settings.... 21 How a job is run on a target.... 24 Deployment Server directory structure... 28
Using the Rapid Deployment Pack... 9
Understanding the Deployment Server... 20
Getting started..... 29 Customizing jobs.... 29 Customizing files.... 30 Reasons to customize the Integration Modules.... 30 All operating systems.... 30 Windows unattend text files.... 30 VMware ESX Server kickstart files.... 31 Virtual Machine jobs.... 31 Red Hat Linux kickstart files.... 31 SUSE Linux control files..... 31 Customization examples.... 31 Example 1Using a specific ProLiant Support Pack version... 31 Example 2Modifying the Windows unattend text files... 32 Example 3Modifying the Red Hat Linux kickstart files... 32 Example 4Modifying the Altiris Deployment Agent for Linux... 32 Example 5Modifying a Create Virtual Machine job for custom virtual values... 32 Related documents.... 33 Online resources.... 33 HP contact information..... 33 HP Software Technical Support and Update Service... 34
Customizing the ProLiant and Integrity Integration Modules.. 29
HP support and contact information.... 33

Index..... 35

Configuring the Rapid Deployment Pack
The following sections detail the configuration steps necessary to deploy an operating system to a server.
Configuring BladeSystem enclosures
The Physical Devices view in the Deployment Server Console displays the physical relationship between the racks, enclosures, and server blades using the rack name and enclosure name for each HP BladeSystem server. The display name for a new server blade is a combination of the rack name, enclosure name, and bay number. Before you connect the first server in an enclosure to the Deployment Server, assign the rack and enclosure with unique names to prevent conflicting database entries. If the BladeSystem servers are powered up before the rack name and enclosure name have been changed, the names are recorded in the Deployment Server database and appear in the Deployment Server Console. If the names are changed after being recorded in the Deployment Server database, then the servers must be rebooted for the new rack name and enclosure name to be discovered. In addition, the original default rack names and the default enclosure names must be manually deleted from the console. To change the rack name and enclosure name, follow the procedure specific to each server type:

ProLiant BL p-Class serversPlace at least one server blade in each enclosure, and before powering up the server blade, change the rack and enclosure information using the Integrated Lights-Out (iLO) interface. For details about accessing iLO to change the rack name and enclosure name, see the documentation shipped with your server blade. HP BladeSystem c-Class serversTo access the Onboard Administrator and change the rack name and the enclosure name, see the server documentation.
Configuring image installs
IMPORTANT: By default, the Create Disk Image and Distribute Disk Image tasks operate on the first disk. The disks are enumerated using a proprietary algorithm. The first disk might not be the system boot disk. The Altiris showdisk utility can be used to generate human-readable disk enumeration output. This utility is called in the provided Read Hardware Configuration job. For more information on reading the showdisk output, see the Rapid Deployment Pack Knowledge Base at http://www.hp.com/servers/rdp/kb.

Configuring imaging jobs

When capturing or deploying an image to a server with multiple disks, either DAS or SAN, you might have to specify the system boot disk in the job. To specify a particular disk:

1. 2. 3.

In the Deployment Server Console, copy, rename, and edit the job. Modify the Create Disk Image or Distribute Disk Image task. In the Additional Parameteres box, add the -dx switch, where x is an integer that represents the appropriate disk number. When deploying Red Hat Enterprise Linux with LVM, x must be a comma-separated list of integers representing all of the disk numbers that the LVM volume will span. For example, to deploy an LVM image that spans the first three disks, use -d1, 2, 3.
Configuring Windows Sysprep jobs
In addition to the steps in the Configuring imaging jobs section, the Windows Sysprep jobs require a product key and cannot use the product keys entered during the Integration Module installation. For each Capture Windows Sysprep Image job:

1. 2. 3. 4. 5. 6.

Select the Create Disk Image task. Click Modify. In the Sysprep settings box, select Add new from the Operating System list. On the OS Product Key screen, select the appropriate operating system. Click Add to enter a new product key. Enter the product key in the Product Key box, and click OK>Finish.
For each Deploy Windows Sysprep Image job:

1. 2. 3. 4.

Select the Distribute Disk Image task. Click Modify. In the Sysprep settings box, select the appropriate operating system from the Operating System list. Select the appropriate product key from the Product key list, and click Finish.
Configuring scripted installs
Configuring scripted install jobs
The scripted install jobs use a small image to partition and format the disk. When deploying to a server with multiple disks, either DAS or SAN, you might have to specify the system boot disk in the job for the NTFS.img or GRUB.img images. For more information, see the Configuring image installs section. To specify a particular disk:
In the Deployment Server Console, copy, rename, and edit the job. Modify the Distribute Disk Image task. In the Additional Parameteres box, add the -dx switch, where x is an integer that represents the appropriate disk number.
Additionally, for Red Hat Linux in a multiple disk scenario, the kickstart file must specify the system boot disk.
On the Deployment Server, copy and rename the kickstart file. Modify the new kickstart file by replacing the autopart command with separate part command lines and adding the ---ondisk=XXX option to each where XXX is the device label. Example for non-LVM: part /boot --size 75 --ondisk=cciss/c0d0 part swap size=1000 --ondisk=cciss/c0d0 part / --size 5120 -grow --ondisk=cciss/c0d0 Example for LVM: part /boot --size 100 --fstype=ext3 --ondisk=cciss/c0d0 part pv.01 --size=100 --grow --ondisk=cciss/c0d0 volgroup VolGroup00 -pesize=32768 pv.01
In the Deployment Server Console, copy, rename, and edit the job. Edit the Run Script Create Boot Environment task in the new job to use the new kickstart file created in step 2.
Configuring SAN-attached scripted install jobs
In addition to the steps in the Configuring scripted install jobs section, some further steps might be necessary. For VMware ESX Server 3.0.x: Disconnect the SAN. After the operating system install is complete, reconnect the SAN and create a VMFS datastore on it.

For VMware ESX 2.5.3:

On the Deployment Server, copy, rename, and edit the job. Modify the Run Script Create Boot Environment task in the new job by changing the default.cfg file reference in the # replacetokens statement to sanattach.cfg. Execute the new job. After the operating system installation is complete, using the MUI: Create the core dump partition.

Select Run this job immediately, and click OK.
Reconfiguring the new servers
In the Computers pane, select all the server blades, and then right-click the selection, and select Configure.
Click Microsoft Networking, and then enter a new workgroup or domain name (if applicable), and click Define Range. Enter the fixed portion of the new server names, and click OK.
Click TCP/IP, enter the IP information for the first server blade, and click OK. Subsequent server blades are assigned the same information, except that the IP address increases incrementally for each server blade.
Maintaining server blades with rip-and-replace
When a failed server blade is replaced, the Deployment Server can automatically replay the job history of the failed server blade on the new server blade. This feature is available only for BladeSystem servers. NOTE: The new server blade requires a new license. The existing license cannot be transferred to the new server blade. To enable rip-and-replace, perform the following steps for each server blade:
In the Computers pane, right-click a single server, and select Properties. Scroll down, and click Bay. Select Re-Deploy Computer from the Server change rule list, and click OK.
The following server change rule options are available:
Re-Deploy ComputerTakes the job history of the previous server blade and replays it on the new server blade. The replay starts from the last deployment type job. This option is available only after the server blade is deployed or a virtual bay has been created. Run Predefined JobProcesses any job specified by the user, including the Initial Deployment job. Wait for User InteractionPerforms no job. The Deployment Agent on the server blade is instructed to wait and the icon in the console is changed to reflect a waiting server. Ignore the ChangeIgnores the new server blade, meaning that no jobs are initiated. If the new server blade existed in a previous bay, the history and parameters for the server are moved or associated with the new bay. If the server blade is not listed in the database, its properties are associated with the bay, and the normal process defined for new servers (if any) is followed.
Performing a Boot from SAN installation
A Boot from SAN (BFS) installation requires several manual steps before starting the operation system installation. Be sure the following prerequisites are met:

The Rapid Deployment Pack populates the Deployment Server Console with jobs and the Deployment Server directory with tools, scripts, configuration files, software drivers, and documentation files. This section explains these provided jobs and files, and the directory structure.
The Rapid Deployment Pack adds four root folders into the Jobs pane.
Table 2 Job folders Folder

Server Deployment

Description
The jobs in this folder perform a complete server deployment. They deploy a default hardware configuration, execute a scripted operating system installation, and install the appropriate ProLiant or Integrity Support Pack.
Server Deployment Toolbox The jobs in this folder provide more granular control over the server deployment process. By providing jobs that perform only hardware configuration, operating system installation, and value-add software installation, you can easily combine various jobs together to suit your needs. Server Replication The jobs in this folder perform replication from a reference server to a target server that is of the same server model with the same hardware configuration.
Virtual Machine Deployment The jobs in this folder provide the ability to create a VMware ESX virtual machine Toolbox and to deploy an operating system to a virtual machine.
Understanding the Deployment Server 20

Job default settings

Unless otherwise indicated in the job name, the job uses the following default settings. For details about how to customize these default settings, see the Customizing the ProLiant and Integrity Integration Modules section in this guide.
Hardware configuration settings
Table 3 Hardware default settings Component
System ROM Smart Array iLO SAN HBA

Default setting

Factory defaults Based on the number of attached drives Not configured in the standard jobs Not configured in the standard jobs
Operating system scripted install settings
The provided Windows scripted install jobs use the default configuration parameters listed in Table 4 Windows default settings. Table 4 Windows default settings Component

Windows administrator password
The administrator password is password. This password is stored as clear text in the unattend answer file. HP recommends changing the default administrator password within the unattend answer file located in the.\lib\osconfig\yyyy directory on the Deployment Server, where yyyy is the operating system shortcut name. A single partition is created automatically that expands to the full drive size. The Windows computer name uses the 15 right-most characters of the display name shown in the Deployment Server Console.
Drive configuration Computer name
Understanding the Deployment Server 21
The provided VMware scripted install jobs use the default configuration parameters listed in Table 5 VMware default settings. Table 5 VMware default settings Component

VMware root password

The root password is password. This password is stored as clear text in the kickstart file. HP recommends that you change the root password to your own password and in encrypted form within the kickstart file located in the.\lib\osconfig\yyyy directory on the Deployment Server where yyyy is the operating system shortcut name. When configuring the disk partition for a scripted operating system installation, various VMware ESX Server specific partitions are created. These are the default settings and must not be changed. The VMware ESX Server host name uses the display name that appears in the Deployment Server Console. VMware ESX Server specific packages are installed. Do not change this setting. Firewall settings are disabled.

Drive configuration

Host name Packages Firewall
The provided Red Hat Linux and SUSE Linux scripted install jobs use the default configuration parameters listed in Table 6 Linux default settings. Table 6 Linux default settings Component

Linux root password

The root password is password. This password is stored as clear text in the kickstart/control file. HP recommends that you change the root password to your own password and in encrypted form within the kickstart/control file located in the.\lib\osconfig\yyyy directory on the Deployment Server where yyyy is the operating system shortcut name. The disk space is partitioned according to Red Hat or SUSE Linux default specifications. Red Hat Enterprise Linux installs Logical Volume Manager (LVM) by default. The Linux host name uses the display name that appears in the Deployment Server Console. Basic Linux server packages are installed. Firewall settings are disabled.

Understanding the Deployment Server 22

Read/Write job filenames

The provided Read (Capture)/Write jobs use the default input/output filenames listed in Table 7 Default Read (Capture)/Write jobs. Table 7 Default Read (Capture)/Write jobs Read(Capture)/Write Job Pair
Server Deployment Toolbox > 1 Hardware Configuration ProLiant ML/DL/BL System Configuration ProLiant ML/DL/BL Array Configuration ProLiant ML/DL/BL HBA Configuration [server specific] Integrity RX/BL System Configuration Integrity RX/BL Array Configuration.\lib\hwconfig\system\pl-capture.xml.\lib\hwconfig\array\pl-capture.ini.\lib\hwconfig\hba\ID.ini where ID is the server ID number as given by Deployment Server.\lib\hwconfig\system\i-capture.xml.\lib\hwconfig\array\i-capture.ini

Filename

Server Deployment Toolbox > 2A OS Installation (Imaged) Windows Image Linux Image.\lib\images\capture-windows.img.\lib\images\capture-linux.img
Server Deployment Toolbox > 2C OS Installation (SysPrep) Windows xxxx Sysprep Image Server Replication ProLiant ML/DL/BL System and Array Configuration and Windows Image.\lib\hwconfig\system\yyyy-windows.xml.\lib\hwconfig\array\yyyy-windows.ini.\lib\images\yyyy-windows.img Where yyyy is the computer model name, for example ProLiant DL360 G4. ProLiant ML/DL/BL System and Array Configuration and Linux Image.\lib\hwconfig\system\yyyy-linux.xml.\lib\hwconfig\array\yyyy-linux.ini.\lib\images\yyyy-linux.img Where yyyy is the computer model name, for example ProLiant DL360 G4. Integrity RX/BL System and Array Configuration and Linux Image.\lib\hwconfig\system\yyyy-linux.xml.\lib\hwconfig\array\yyyy-linux.ini.\lib\images\yyyy-linux.img Where yyyy is the computer model name, for example ProLiant DL360 G4.\lib\images\xxxx-sysprep.img where xxxx is the operating system name and shortcut name
Understanding the Deployment Server 23
How a job is run on a target
This section provides a walkthrough of how a job is executed on a target server. The table within each step lists the state of the target server and the job action during that execution step. The term automation environment is used throughout this section. It is an operating system in which scripts can be run on the target independent of the targets production operating system or the Deployment Server operating system. The target can boot the automation environment either from a CD-ROM, USB key, or through PXE. The Rapid Deployment Pack supports the following automation environments: Linux x86 and ia64 (hereafter LinuxPE) and WinPE 1.6 x86 and x64. Each automation environment consists of the necessary base files, additional HP drivers, and the appropriate Altiris Deployment Agent. NOTE: A CD-ROM or USB key can only hold one automation environment. Many of the jobs use multiple automation environments. This means that as the job progresses, the boot media must be swapped accordingly. The Run Script, Create Disk Image, and Distribute Disk Image tasks enable the user to specify which automation environment to run in. The Rapid Deployment Pack jobs specify a specific automation environment to avoid ambiguity and to ensure that the utilities run in the correct and tested environment.

Power up the bare-metal target server. Since the target does not have a bootable hard drive, the boot order attempts a PXE boot. The PXE Server sends it the Initial Deploy boot option image. By default, this is Linux Managed (auto-select). The Deployment Agent connects to the Deployment Server. Since this is the initial connection and no pending job exists, the Deployment Server directs the Deployment Agent to wait. Table 8 Step 1
Target Server LinuxPE, waiting
Schedule the "Deploy ProLiant ML/DL/BL + Windows 2003 x64 Enterprise + PSP" job on the target. Table 9 Step 2
Target Server Job LinuxPE, waiting Task 1Deploy System Configuration {WinPE 32-bit}, pending
The Deployment Server determines that the target is in the incorrect automation environment. It directs the Deployment Agent to set the one-time boot EV to PXE and then reboot. When the target reboots to PXE, the PXE Server sends it the WinPE 32-bit image. Table 10 Step 3
Target Server Job Rebooting to WinPE Managed 32-bit Task 1 Deploy System Configuration {WinPE 32-bit}, pending
Understanding the Deployment Server 24
When the Deployment Agent connects to the Deployment Server, task 1of the job begins to execute. Table 11 Step 4
Target Server Job WinPE Managed 32-bit, executing task Task 1Deploy System Configuration {WinPE 32-bit} set inputfile=pl.xml call %altiris_share%\lib\bin32\winpe\conrep.cmd l %inputfile%
Task 2 in the job is a Reboot. By looking ahead at task 3, the Deployment Server directs the Deployment Agent to set the One-Time Boot EV to PXE and then reboot. When the target reboots to PXE, the PXE Server sends it the WinPE Managed 32-bit image. This reboot is necessary in case any Smart Array controllers are disabled in the conrep file. Table 12 Step 5
Target Server Job Rebooting to WinPE 32-bit Task 2Reboot
When the Deployment Agent connects to the Deployment Server, the task 3 of the job begins to execute. Table 13 Step 6
Target Server Job WinPE 32-bit, executing task Task 3Deploy Array Configuration {WinPE 32-bit} set inputfile=pl-acu--d.ini call %altiris_share%\lib\bin32\winpe\acu.cmd I %inputfile%
Task 4 in the job is a Reboot. By looking ahead at task 5, the Deployment Server directs the Deployment Agent to set the One-Time Boot EV to PXE and then reboot. When the target reboots to PXE, the PXE Server sends it the WinPE Managed 32-bit image. This reboot is mandatory so that the subsequent imaging task is able to see the new hard drive. Table 14 Step 7
Target Server Job Rebooting to WinPE 32-bit Task 4Reboot
When the Deployment Agent connects to the Deployment Server, task 5 of the job begins to execute. Table 15 Step 8

Target Server Job WinPE 32-bit, executing task Task 5Deploy System Configuration {WinPE 32-bit} set inputfile=pl-win.xml call %altiris_share%\lib\bin32\winpe\conrep.cmd l %inputfile%
Understanding the Deployment Server 25
The Deployment Agent begins executing task 6 of the job. Table 16 Step 9
Target Server Job WinPE 32-bit, executing task Task 6Distribute Disk Image {WinPE 32-bit}.\lib\images\NTFS.IMG
Task 7 in the job is a Reboot. By looking ahead at task 8, the Deployment Server directs the Deployment Agent to set the one-time boot EV to PXE and then reboot. When the targets reboot to PXE, the PXE Server sends it the WinPE 64-bit image. This reboot is mandatory so that the subsequent file copy tasks are able to use the new hard drive. Table 17 Step 10
Target Server Job Rebooting to WinPE 64-bit Task 7Reboot
When the Deployment Agent connects to the Deployment Server, task 8 of the job begins to execute. Since tasks 8 through 12 all run in WinPE 64-bit without a Reboot task, they execute sequentially while in WinPE 64-bit. Table 18 Step 11
Target Server Job WinPE 64-bit, executing tasks Task 8Copy ProLiant Files {WinPE 64-bit} set oem=proliant.zzz\w52.64 call %altiris_share%\lib\bin64\winpe\osoem1.cmd Task 9Copy Altiris Files {WinPE 64-bit} rem replacetokens.\lib\osoem\altiris\aclient.txt.\lib\osoem\altiris\%ID%.inp set configfile=%ID%.inp call %altiris_share%\lib\bin64\winpe\osoem2.cmd Task 10Copy Unattend.txt {WinPE 64-bit} rem replacetokens.\lib\osconfig\w52e.64\default.txt.\lib\osconfig\w52e.64\%ID%.txt set unattendfile=w52e.64\%ID%.txt call %ALTIRIS_SHARE%\lib\bin64\winpe\osconfig1.cmd Task 11Copy Distribution Files {WinPE 64-bit} set dist=w52e.64 call %altiris_share%\lib\bin64\winpe\osdist1.cmd Task 12Start Install {WinPE 64-bit} set HD=c for %%i in (c d e f g h i j k l m) do if exist %%i:\rdpimage set HD=%%i %HD%:\amd64\winnt32.exe /s:%HD%:\amd64 /unattend:%HD%:\unattend.txt /syspart:%HD%: /tempdrive:%HD%:
Understanding the Deployment Server 26
After completing task 12, the Deployment Server looks ahead at task 13. Task 13 runs in Windows production. Therefore, the Deployment Server directs the Deployment Agent to reboot. When the target reboots, it boots to the hard drive because it is before PXE in the default boot order. Table 19 Step 12
Target Server Job Executing Windows-scripted install Task 13Install Package {Windows}, pending
The Deployment Agent for Windows is installed as part of the Windows-scripted install. The Deployment Agent loads upon the first real Windows production boot. When it connects to the Deployment Server, task 13 of the job begins to execute. Table 20 Step 13
Target Server Job Windows, executing task Task 13Install Package {Windows}.\lib\software\ProLiant Support Pack Z.ZZ for Windows 2003 x64\setupex.exe
The last task in the job is a Reboot. The Deployment Server tells the Deployment Agent to reboot. This reboot is mandatory so that the new and updated drivers installed by the ProLiant Support Pack get loaded properly. Table 21 Step 14

Target Server Job Rebooting to Windows Task 14Reboot
Understanding the Deployment Server 27
Deployment Server directory structure
The following table provides an overview of the Deployment Server directory as populated by the Rapid Deployment Pack. Table 22 Deployment Server directory structure Directory

.\docs.\jobs.\lib\bin32

Description Rapid Deployment Pack and SmartStart Scripting Toolkit documentation in Portable

Document Format (.pdf)

The.bin files for the provided jobs Various Windows x86 and Linux x86 tools and scripts Windows SmartStart Scripting Toolkit Linux SmartStart Scripting Toolkit Various Windows x64 tools and scripts Various Windows ia64 and Linux ia64 tools and scripts Smart Setup Scripting Toolkit for Integrity Presupplied and captured hardware configuration files. Presupplied and captured image files. Operating system scripted install answer files separated into subdirectories per OS. Operating system distribution files separated into subdirectories per OS. Each
subdirectory contains the entire contents of the source DVD or CD-ROM(s). ProLiant Drivers for Windows Scripted Installs Integrity Drivers for Windows Scripted Installs Altiris Deployment Agents Integrity Support Packs The proliant.xxx or integrity.xxx subdirectories are either a specific version number, such as 7.70 or Z.ZZ which is a copy of the latest version subfolder. The Z.ZZ subfolder is used by the provided scripted install jobs.

.\lib\bin64.\lib\binia64

.\lib\hwconfig.\lib\images.\lib\osconfig.\lib\osdist.\lib\osoem
.\lib\ossysprep.\lib\software
Operating system sysprep imaging answer files.
ProLiant Support Packs ProLiant Firmware Updates Integrity Support Packs The Support Pack x.xx subdirectories are either a specific version number such as 7.70 or Z.ZZ which is a copy of the latest version subfolder. The Z.ZZ subfolder is used by the provided scripted install jobs.
Understanding the Deployment Server 28
Customizing the ProLiant and Integrity Integration Modules

Getting started

Before modifying the provided jobs, folders, and files, make a copy of the job, files, or both and use this copy for your custom work. Keeping the original job and files ensures that a working version exists. If you encounter a problem or if you select to overwrite the jobs or files during an upgrade or reinstallation of the Rapid Deployment Pack, your customized job or file is not overwritten.

Customizing jobs

This section explains how to copy, paste, rename, and edit a job in the Deployment Server Console Jobs pane. For more information about the customization features of the Deployment Server Console, see the Altiris Deployment Solution 6.8 Deployment and Migration Guide at http://www.hp.com/servers/rdp. NOTE: The jobs in the Rapid Deployment Pack use long names to be descriptive. When attempting to copy these jobs to the same directory as the original job, the name might be truncated by Altiris because it places Copy of in front of the job causing it to exceed the 128-character limit of the Deployment Server Console. To copy, paste, rename, and edit a job:

Copy the adlagent.conf file from a working target server to the Deployment Server in the.\lib\osoem\altiris directory. Rename the file to adlagent.conf.custom. Modify the file for your specific settings.
Example 5Modifying a Create Virtual Machine job for custom virtual values
To change the Create Virtual Machine job to use different virtual-disk-size or virtual-memory-size values:
In the Deployment Server Console, copy, rename, and edit a Create Virtual Machine job. Modify the Run Script Create and power on Virtual Machine task, remove the comment and change the VMDISKSIZE= or VMMEMSIZE= values to new values. Some possible values are listed in the comments of this task. For more information, see the VMware Virtual Infrastructure SDK Reference Guide at https://www.vmware.com/pdf/SDKReferenceGuide.pdf.
Customizing the ProLiant and Integrity Integration Modules 32
HP support and contact information

Related documents

HP recommends reviewing the following documentation before reading this guide: HP ProLiant Essentials Rapid Deployment Pack Planning Guide HP ProLiant Essentials Rapid Deployment Pack Installation Guide HP ProLiant Essentials Rapid Deployment Pack Knowledge Base at http://www.hp.com/servers/rdp/kb which includes the latest Deployment Support article.
All PDF documents can be found at http://www.hp.com/servers/rdp and at \docs on the product DVD.

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 professionals are available in the IT Resource Center (ITRC) User Forum ProLiant Deployment & Provisioning. You can access this forum from the Management Software and System Tools link at http://forums.itrc.hp.com. Information and resources about the Altiris Deployment Solution are available from the Altiris website at http://www.altiris.com.

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. 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. To contact HP by phone:
For HP technical support:
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.
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 to help you resolve software implementation or operations problems. The service also provides access to software updates and reference manuals either in electronic format 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.
WarrantyHP 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 supportPhone support is available to help you with basic installation and setup and 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, click Management software and system tools. 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 available for free download by following a simple registration from the SmartStart website. 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.