HP Rx2620-2 - Integrity - 0 MB RAM User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. Rx2620-2 - Integrity - 0 MB RAM
  6. User manual
HP Rx2620-2 - Integrity - 0 MB RAM User Manual

HP Rx2620-2 - Integrity - 0 MB RAM User Manual

Rapid deployment pack windows edition user guide 3.70
Hide thumbs Also See for Rx2620-2 - Integrity - 0 MB RAM:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Service Manual, User Manual

HP ProLiant Essentials Rapid Deployment Pack

User Guide

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

Advertisement

Table of Contents
loading

Related Manuals for HP Rx2620-2 - Integrity - 0 MB RAM

Summary of Contents for HP Rx2620-2 - Integrity - 0 MB RAM

  • Page 1: Hp Proliant Essentials Rapid Deployment Pack

    HP ProLiant Essentials Rapid Deployment Pack User Guide Part number 315378-402 Eleventh edition August 2007 Product version: 3.70...
  • Page 2 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.

  • Page 3: Table Of Contents

    Contents 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..................
  • Page 4 Index ..............................35 Contents 4...

  • Page 5: Configuring The Rapid Deployment Pack

    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.

  • Page 6: Configuring Image Installs

    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.

  • Page 7: Configuring Scripted Installs

    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.

  • Page 8: Configuring Boot From San Scripted Install Jobs

    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.

  • Page 9: Using The Rapid Deployment Pack

    Using the Rapid Deployment Pack This section provides information about the following topics: Connecting server blades Creating a reference server and image Deploying a captured image to other similar servers Reconfiguring the new servers Maintaining server blades with rip-and-replace Performing a Boot from SAN installation Connecting server blades Connect the enclosure to the network that contains your Deployment Server, and power up the enclosure.
  • Page 10 Select View>Show Physical Devices. NOTE: The Physical Devices view is an additional view available only for BladeSystem servers in the Computers pane. A job can be executed on a server listed in this view. Table 1 lists the server icons displayed in the Physical Devices view of the Deployment Server Console.
  • Page 11 From the Computers pane, right-click on a server blade. Select Power Control>RILOE/iLO – Interface. This action accesses the iLO, iLO 2, or RILOE interface to enable remote viewing of the deployment. Using the Rapid Deployment Pack 11...

  • Page 12: Creating A Reference Server And Image

    Creating a reference server and image The initial server blade must be deployed using a scripted installation job. Subsequent server blades can be deployed by capturing and deploying the image of the initial server blade. In the Jobs pane, select a Windows-scripted installation job in the Server Deployment folder. Drag the job onto the initial server blade in the Computers pane.
  • Page 13 In the Jobs pane, find the Read ProLiant ML/DL/BL System and Array Configuration and Windows Image {WinPE} job in the Server Replication folder. Drag the job onto the initial server blade in the Computers pane. NOTE: The Server Replication jobs provided with the Rapid Deployment Pack create and deploy images using an image name based on the computer model names.

  • Page 14: Deploying A Captured Image To Other Similar Servers

    Deploying a captured image to other similar servers In the Computers pane, select the rest of the server blades. Drag them onto the Write ProLiant ML/DL/BL System and Array Configuration and Windows Image {WinPE} job in the Server Replication folder in the Jobs pane. If you are deploying the image to all server blades in an enclosure, you can select the enclosure from the Physical Devices view.

  • Page 15: Reconfiguring The New Servers

    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. Using the Rapid Deployment Pack 15...
  • Page 16 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. Select Run this job immediately, and click OK. Using the Rapid Deployment Pack 16...

  • Page 17: Maintaining Server Blades With Rip-And-Replace

    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.

  • Page 18: Performing A Boot From San Installation

    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 target server is cabled in a single-path configuration (with only one channel active). You can cable both paths after the operating system installed and the multipathing software is installed.
  • Page 19 BootDeviceWWID=395442c135713a42 BootDeviceLUN=01 Run the appropriate platform Write HBA Configuration job from the Server Deployment Toolbox\1—Hardware Configuration\HBA job folder on the target server. For ProLiant servers, run the Deploy ProLiant BL System Configuration (Boot From SAN) {LinuxPE} or {WinPE} job from the Server Deployment Toolbox\1—Hardware Configuration\System job folder on the target server.

  • Page 20: Understanding The Deployment Server

    Understanding the Deployment Server 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. Jobs The Rapid Deployment Pack adds four root folders into the Jobs pane.

  • Page 21: Job Default Settings

    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...
  • Page 22 The provided VMware scripted install jobs use the default configuration parameters listed in Table 5 VMware default settings Table 5 VMware default settings Component Default setting VMware root password The root password is password. This password is stored as clear text in the kickstart file.
  • Page 23 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 Filename Server Deployment Toolbox > 1 – Hardware Configuration ProLiant ML/DL/BL System Configuration .\lib\hwconfig\system\pl-capture.xml ProLiant ML/DL/BL Array Configuration .\lib\hwconfig\array\pl-capture.ini...

  • Page 24: How A Job Is Run On A Target

    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”...
  • Page 25 When the Deployment Agent connects to the Deployment Server, task 1of the job begins to execute. Table 11 Step 4 Target Server WinPE Managed 32-bit, executing task Task 1—Deploy 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.
  • Page 26 The Deployment Agent begins executing task 6 of the job. Table 16 Step 9 Target Server WinPE 32-bit, executing task Task 6—Distribute 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.
  • Page 27 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.

  • Page 28: Deployment Server Directory Structure

    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 Description .\docs Rapid Deployment Pack and SmartStart Scripting Toolkit documentation in Portable Document Format (.pdf) .\jobs The .bin files for the provided jobs...

  • Page 29: Customizing The Proliant And Integrity Integration Modules

    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.

  • Page 30: Customizing Files

    To export a job or folder: Right-click the job or folder. Select Export. On the Export Selected Job(s)/Folder(s) screen, click Browse to designate a directory and job file, or enter the path and file name in the Export to File Name field. If you want to export the subfolders of a folder, select Export subfolders.

  • Page 31: Vmware Esx Server Kickstart Files

    VMware ESX Server kickstart files Change the default root password HP recommends that you do not modify the VMware ESX Server kickstart file with other modifications. For supported VMware kickstart options, see http://www.vmware.com. Virtual Machine jobs Change the virtual disk size Change the virtual memory size For more information, see the VMware Virtual Infrastructure SDK Reference Guide at https://www.vmware.com/pdf/SDKReferenceGuide.pdf.

  • Page 32: Example 2-Modifying The Windows Unattend Text Files

    Download and extract the support pack to the new directory. For VMware and Linux, copy rdpinstall.sh and rdpinstall.dat from a similar support pack to the new directory. In the Deployment Server Console, copy, rename, and edit the job. For Windows, modify the Install Package task to reference the chosen directory. For VMware or Linux, modify the Copy File to task to reference the chosen directory.

  • Page 33: Hp Support And Contact Information

    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.

  • Page 34: Hp Software Technical Support And Update Service

    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.
  • Page 35 Index imaging, 14, 15 setting change rule, 17 Altiris Deployment Agent for Linux Deployment Server modifying, 32 directory structure, 20 Deployment Server directory structure, 28 bay properties rule configuration, 17 disk partition, configuration, 21 BIOS settings, 21 Boot from SAN installation, 18 editing Boot from SAN scripted install jobs, 8 files, 30...
  • Page 36 initial deployment job, 17 ProLiant Integration Module, customizing, 29 installation settings Red Hat Linux, 23 rack name, 5 Windows, 21 RAID settings, 21 Integrated Administrator, 5 Red Hat Linux Integrated Lights-Out, 5 customizing kickstart files, 31 installation settings, 23 Job default settings, 21 scripted install, 20 jobs redeployment option, 17...
  • Page 37 installation settings, 21 Windows Sysprep images, 6 wait option, 17 Windows Sysprep jobs, 6 Windows customizing unattend text files, 30 Index 37...

This manual is also suitable for:

Proliant essentials rapid deployment pack

Table of Contents