HP ProLiant DL320e User Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Software
  5. ProLiant DL320e
  6. User manual

HP ProLiant DL320e User Manual

Hp scripting toolkit 9.30 for windows user guide
Hide thumbs Also See for ProLiant DL320e:
Table of Contents

Advertisement

Quick Links

See also: Reference Manual , User Manual
HP Scripting Toolkit for Windows User
Guide
Abstract
This document provides information about the Scripting Toolkit for Windows utilities and how best to use the Scripting Toolkit
for Windows to configure HP ProLiant servers and BladeSystem infrastructure in a Windows environment. This document is
intended for IT experts with experience in scripting operating system installations and configuring HP ProLiant server hardware.
HP Part Number: 415598-409
Published: October 2012
Edition: 18

Advertisement

Table of Contents
loading

Related Manuals for HP ProLiant DL320e

Summary of Contents for HP ProLiant DL320e

  • Page 1 HP Scripting Toolkit for Windows User Guide Abstract This document provides information about the Scripting Toolkit for Windows utilities and how best to use the Scripting Toolkit for Windows to configure HP ProLiant servers and BladeSystem infrastructure in a Windows environment. This document is intended for IT experts with experience in scripting operating system installations and configuring HP ProLiant server hardware.
  • Page 2 Notices © Copyright 2005, 2012 Hewlett-Packard Development Company, L.P. 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.

  • Page 3: Table Of Contents

    Contents 1 Introduction....................6 Scripting Toolkit for Windows.....................6 Microsoft Windows Preinstallation Environment................6 Minimum requirements......................6 2 Deployment using the Scripting Toolkit for Windows........7 Deployment overview........................7 Sample deployment procedure....................7 Creating a network share......................8 Adding drivers to Windows PE 3.0..................8 Adding drivers to Windows PE 4.0..................9 Capturing a reference configuration from the source server............10 Configuring the target server and installing the operating system ..........11 3 Advanced topics..................12...
  • Page 4 IFHW command-line syntax....................21 IFHW command-line arguments...................21 IFHW return codes......................21 IFHW command line examples....................22 Expression operators and terms...................22 Expression examples......................22 Using HWQUERY........................23 HWQUERY command-line syntax..................23 HWQUERY command line arguments...................23 HWQUERY return codes.....................23 HWQUERY command-line examples..................23 Using CONREP........................24 CONREP command-line syntax....................24 CONREP command line arguments..................25 CONREP return codes......................25 CONREP screen output.......................25 CONREP -s (Store to Data file) Example usage for HP ProLiant servers not using the Oxx ROM...
  • Page 5 LogicalDriveSSPState....................38 ParityGroups......................39 PreferredPath......................39 RAID........................39 Sectors........................39 Size........................39 SSPAdaptersWithAccess....................40 StripeSize........................40 HBA category.......................40 ConnectionName.....................40 HBA_WW_ID......................41 HostMode.......................41 ACU scripting error messages....................41 Using HPLPCFG........................45 HPLPCFG command-line syntax....................45 HPLPCFG command-line arguments..................45 HPLPCFG return codes......................45 HPLPCFG command-line examples..................46 Using LO100CFG........................46 LO100CFG command-line syntax..................46 LO100CFG command-line arguments...................47 LO100CFG return codes.....................47 LO100CFG command-file contents..................47 Using HPQLAREP........................48 HPQLAREP command-line syntax..................48...

  • Page 6: Introduction

    1 Introduction Scripting Toolkit for Windows The Scripting Toolkit for Windows is a server deployment product that delivers an unattended automated installation for high-volume HP ProLiant server and BladeSystem infrastructure deployments. This document describes how to best use the Scripting Toolkit to configure HP ProLiant servers and BladeSystem infrastructure.

  • Page 7: Deployment Using The Scripting Toolkit For Windows

    2 Deployment using the Scripting Toolkit for Windows Deployment overview The Scripting Toolkit includes a set of utilities for configuring and deploying servers in a customized, predictable, and unattended manner. These utilities enable you to duplicate the configuration of a source server on target servers with minimal user interaction. IMPORTANT: HP ProLiant 100-Series servers previous to Gen8 do not support all Scripting Toolkit commands, and those that are supported might not work as expected.

  • Page 8: Creating A Network Share

    Creating a network share To create a network share: Download the appropriate Scripting Toolkit SoftPaq from the Scripting Toolkit website at http://www.hp.com/go/ProLiantSTK. Install the Scripting Toolkit SoftPaq on a common server that resides on the same network as the servers to be deployed. Share the folder in which you installed the Scripting Toolkit.

  • Page 9: Adding Drivers To Windows Pe 4.0

    is installed and the STK IO driver (hpsstkio.sys) is copied to the windows\system32\ drivers directory. To add drivers offline: Mount the base image to a local directory by using dism. For example: dism /Mount-Wim /WimFile:C:\winpe_x86\winpe.wim /index:1 MountDir:C:\STK.TMP Add the .inf file to the base image by using the dism /Add-Driver command. For example: dism /image:C:\SSSTK.TMP /Add-Driver /driver:C:\ssstk\drivers\example.inf For each additional device driver repeat steps 1 and 2.

  • Page 10: Capturing A Reference Configuration From The Source Server

    For each additional device driver repeat steps 1 and 2. When you finish customizing the image, prepare the image for deployment by using the peimg /prep command. NOTE: If the appropriate iLO driver is not installed, some utilities do not work correctly. For more information, see the README.txt file located with the drivers.

  • Page 11: Configuring The Target Server And Installing The Operating System

    Configuring the target server and installing the operating system Boot the media (CD/DVD, USB drive key, or PXE) that contains the customized Windows PE image on the target server. Run CONREP to configure the target server with the captured settings: Change to the directory where CONREP resides.

  • Page 12: Advanced Topics

    3 Advanced topics Overview The advanced topics addressed in this section cover some of the most common deployment tasks that can be automated using the Scripting Toolkit. IMPORTANT: The script files and script segments in this section are provided only as examples. You must modify the scripts for your environment.

  • Page 13: Querying The Hpdiscovery File To Determine The Presence Of A Card Family

    .\ACU\bin\hpacuscripting.exe -i .\ArraySettings\SA6iArray.ini :NEXT2 \ifhw .\hpdiscovery.xml allboards.xml PCI:"Smart Array 5312" if errorlevel 1 GOTO NEXT3 .\ACU\bin\hpacuscripting.exe -i .\ArraySettings\SA5312Array.ini :NEXT3 Querying the HPDISCOVERY file to determine the presence of a card family IFHW and HWQUERY can perform queries based on partial name information, enabling you to verify the presence of a whole family of cards by using a partial query such as Smart Array.
  • Page 14 System\ifhw hpdiscovery.xml System\allboards.xml HWQ:SystemName eq "ProLiant DL380 G2" if errorlevel 1 goto NEXT1 REM ---- REM This section performs the System ROM Flash. Online Flash components REM are kept in a directory called Roms REM ---- Roms\cp004648.exe /INSTPATH:S:\ROMScratcharea REM ---- REM Check the error code returned to determine Success or Failure REM ---- if errorlevel 3 goto HWNOTFOUND...

  • Page 15: Erasing Array Configurations

    NEXT3: REM ---- REM DONE REM ---- REBOOTREQUIRED: System\reboot PXE HWNOTFOUND: End: For more information about Online ROM Flash Smart Components, see the HP Online ROM Flash User Guide on the HP Software and Driver Downloads website at http://www.hp.com/support. Erasing array configurations Before beginning the deployment process, you might want to erase the current array configuration.

  • Page 16: Scripting Toolkit Utilities

    4 Scripting Toolkit utilities Syntax conventions Syntax refers to the way a command and parameters must be entered. Unless specified otherwise, enter commands, parameters, and switches in all uppercase or all lowercase letters. Sample syntax line: SAMPLE[/R|-R][DRIVE:][PATH]FILENAME[...] Command element Meaning Specifies the name of the command.

  • Page 17: Using Reboot

    The Scripting Toolkit utilities include: REBOOT SETBOOTORDER (Limited functionality for HP ProLiant 100 series servers) STATEMGR (Utility is not supported on 100 series servers) RBSURESET HPDISCOVERY IFHW HWQUERY CONREP HPRCU HPACUSCRIPTING HPLPCFG LO100CFG (Utility only supports HP ProLiant 100 series servers) HPQLAREP HPONCFG (Not supported on HP ProLiant 100 series servers using the Oxx ROM family) Using REBOOT...

  • Page 18: Using Setbootorder

    Using SETBOOTORDER SETBOOTORDER enables you to set the order in which devices are booted, including diskette drives, CD-ROM or DVD drives, hard drives, PXE, and USB devices. This utility sets the boot order only for devices that exist for a server. The devices can be set to boot in any order. SETBOOTORDER cannot be used to set the storage controller order.

  • Page 19: Statemgr Command-Line Arguments

    STATEMGR command-line arguments Command-line argument Description This argument reads the state of the environment variable /R or defined by [EVNAME]. The value of the environment variable is returned as a return code. This argument writes the state defined by [VALUE] to an /W or -W environment variable defined by [EVNAME].

  • Page 20: Rbsureset Return Codes

    RBSURESET return codes Value Meaning The BIOS settings have been successfully reset to the factory default. The BIOS settings have not been reset. Using HPDISCOVERY HPDISCOVERY provides an inventory of the server being configured and must run on each deployed server.

  • Page 21: Hpdiscovery Return Codes

    HPDISCOVERY return codes Value Meaning The command was completed successfully. A usage message might appear. An error has occurred. See error message for details. 1..255 HPDISCOVERY command line examples NOTE: Before running HPDISCOVERY, you must install WMI. For more information on installing extra packages in Windows PE, see the Windows PE documentation.

  • Page 22: Ifhw Command Line Examples

    IFHW command line examples Command-line argument Description This command returns the following error levels: ifhw hpdiscovery.xml allboards.xml "PCI:Smart Array 5i" ERRORLEVEL 0 (True) if the Smart Array 5i is present ERRORLEVEL 1 (False) if the device is not present ERRORLEVEL 2 (Error) if the expression could not be understood Expression operators and terms Operator or term...

  • Page 23: Using Hwquery

    Expression input Result True if the system is a ProLiant DL380 G2 with a Smart HWQ:SystemName eq Array 5i Controller present and a ROM date of "ProLiant DL380 G2" and "PCI:Smart Array 1 1/12/2004 5i" and HWQ:ROMDate eq "11/12/2004" True if the system contains a Smart Array 5i Controller or "PCI:Smart Array 5i"...

  • Page 24: Using Conrep

    Command-line argument Description MY_SYS_RAM=768 For a hpdiscovery.xml file that indicates a Smart Array hwquery hpdiscovery.xml allboards.xml "TEST=Smart Array" 5i Controller is present, HWQUERY produces the following: TEST=Smart Array 5i Controller For a hpdiscovery.xml file that contains hwquery hpdiscovery.xml allboards.xml MYRAM=TotalRAM MYROMDATE=ROMDate <TotalRAM>768</TotalRAM>...

  • Page 25: Conrep Command Line Arguments

    CONREP screen output A typical screen output generated by CONREP is similar to the following: conrep 3.00 - Scripting Toolkit Configuration Replication Program Copyright (c) 2007-2012 Hewlett-Packard Development Company, L.P. System Type: ProLiant DL360 G4 ROM Date: 08/16/2005 ROM Family: P52 XML System Configuration: conrep.xml...

  • Page 26: Conrep -S (Store To Data File) Example Usage For Hp Proliant Servers Not Using The Oxx Rom Family

    To extract the BIOS settings from an SL160z G6 server and save the configuration to an sl160zconrep.dat data file: conrep -s -xconrepSL160zg6_20090728.xml -fsl160zconrep.dat conrep 3.00 - Scripting Toolkit Configuration Replication Program Copyright (c) 2007-2012 Hewlett-Packard Development Company, L.P. System Type: ProLiant SL160z G6 ROM Date : 07/28/2009 ROM Family : O33 Processor Manufacturer : Intel XML System Configuration : conrep_SL160zg6_20090728.xml...

  • Page 27: Conrep Command File Contents

    <Slot1>00 </Slot1> <BusDev1>00 78 </BusDev1> <Rest1>c1 </Rest1> </Section> <Section name="Language">ENGUSAus </Section> <Section name="System_WOL">Disabled</Section> <Section name="System_APIC">Auto Set</Section> <Section name="System_COMA">COM1</Section> <Section name="System_COMA_IRQ">IRQ4</Section> <Section name="System_COMB">Disabled</Section> <Section name="System_COMB_IRQ">Undefined</Section> <Section name="System_LPT">LPT1</Section> <Section name="System_LPT_IRQ">IRQ7</Section> <Section name="Diskette_Write_Control">Writes_Enabled</Section> <Section name="NMI_Debug_Button">Disabled</Section> <Section name="ACPI_Power_Button">Disabled</Section> <Section name="ASR">Disabled</Section> <Section name="ASR_Timeout">10 Minutes</Section> <Section name="Thermal_Shutdown">Enabled</Section> <Section name="RBSU_Language">01</Section>...

  • Page 28: Using Hprcu

    <Index1>01 </Index1> <Index2>03 </Index2> <Index3>02 </Index3> <Index4>04 </Index4> <Index5>ff </Index5> <Index6>ff </Index6> <Index7>ff </Index7> </Section> <Section name="PCI_Devices" helptext= "Lists of PCI devices and their interrupts-not displayed if default" >EMPTY_DELETE</Section> <Section name="Controller_Order" helptext= "Lists the current boot controller ordering"> <Id0>80 86 25 a3 </Id0> <Slot0>00 </Slot0>...

  • Page 29: Hprcu Return Codes

    Command line argument Description Name of the input or output file. If not specified, the XML -f{file.xml} configuration defaults to hprcu.xml. This argument displays program usage. Outputs the help and warning text for each feature. Only valid with the -s option. HPRCU return codes Command line argument Description...

  • Page 30: Capturing A Configuration

    For more information, see the Configuring Arrays on HP Smart Array Controllers Reference Guide on the HP website at http://www.hp.com/support/CASAC_RG_en. Users familiar with the previous versions of ACU Scripting must now install the ACU CLI application to obtain the scripting executable. The new ACU scripting executable (hpacuscripting) replaces the former executable (cpqacuxe) in all scripts.

  • Page 31: Creating An Acu Script File

    Creating an ACU script file To create a valid ACU script file, use one of the following methods: Modify the sample custom input script (page 31). Create a Capture file for capturing a configuration (page 30). You can create a capture file from any server that has ACU loaded, and then modify the values of options in the file as necessary for the target system.

  • Page 32: Script File Options

    PreferredPathMode = Auto|Manual ; COMMENT: the following five entries are used to optimize the controller performance for video MNPDelay = 0|1|2|...|60 ; units are minutes, zero indicates disabled IRPEnable = Yes|No DPOEnable = Yes|No ElevatorSortEnable = Yes|No QueueDepth = 2|4|8|16|32|Auto Array = A|B|C|D|E|F|G|...Z|a|b|c|d|e|f OnlineSpare = None | N | Port:ID,Port:ID...

  • Page 33: Control Category

    The options for each category are listed in the following table and described in more detail in the remainder of this section. Category Options Description Control Action Use these options to define the overall behavior of ACU when it processes scripts and creates configurations.

  • Page 34: Action Mode

    Action mode You must specify an Action mode: In Configure mode, you can create new arrays, but you cannot modify existing arrays. The controller must be connected to unassigned physical drives for this mode to be available. In Reconfigure mode, you can modify existing arrays. For example, you can set up an array expansion, a logical drive extension, or a migration.

  • Page 35: Chassisname

    ChassisName Enter the user-defined character string that identifies the controller. You can use any of the following characters in the string: a–z, A–Z, 0–9, !, @, #, *, (, ), ,, -, _, +, :, ., /, [space] You do not need to use quotation marks around the string, but doing so allows the string to begin with a space character.

  • Page 36: Rebuildpriority, Expandpriority

    Read:write ratio RA4x00 with 16MB RA4x00 with 48MB All other controllers All other controllers cache cache with battery-backed without write cache battery-backed write cache 70:30 – – 60:40 – – 50:50 – 40:60 – – – 30:70 – – – 25:75 –...

  • Page 37: Array Category

    Array category The Array category has the following options: “Array” (page 37) “Drive” (page 37) “DriveType” (page 37) “OnlineSpare” (page 38) Array Enter a letter or pair of letters to identify the array you are creating or reconfiguring, and observe these additional limitations: In Configure mode, ACU creates a new array.

  • Page 38: Onlinespare

    OnlineSpare The value for this option determines whether the array specified previously in the script will be configured with spare drives. Method mode Possible values Default value Custom To specify exactly which drives to use as spares, In Configure action mode: None. use the applicable convention (port:ID, box:bay, In Reconfigure action mode, ACU ignores any or port:box:bay).

  • Page 39: Paritygroups

    The following defaults apply: For new logical drives, the default value is Disabled. For existing logical drives, the default value is the current logical drive setting. ParityGroups When you create a RAID 50 or RAID 60 configuration, you must also set the number of parity groups.

  • Page 40: Sspadapterswithaccess

    array, as long as the operating system supports logical drive extension. You cannot reduce the size of the logical drive. CAUTION: Back up all data before extending a logical drive. SSPAdaptersWithAccess Enter values here to identify the SSP adapters that you want to have access to a logical drive. The values are processed only if either SSPState or LogicalDriveSSPState is set to Enable.

  • Page 41: Hba_Ww_Id

    The string can consist of the following: A maximum of 16 characters Embedded space characters but cannot end with a space character Any of the following characters: a–z, A–Z, 0–9, !, @, #, *, (, ), -, _, +, :, ., /, and [space] HBA_WW_ID This option specifies which HBA, based on its assigned WWN, is modified by the configuration changes.
  • Page 42 Error code Error message Comment or clarification between operations. Limit the number of such configuration changes in the script. 1091 Controller does not support SSP. — 1093 Controller requires physical drives to set — license keys. 1 102 Slot information is not available. You cannot run a script in Input mode on internal controllers that do not have slot information online.
  • Page 43 Error code Error message Comment or clarification 2831 Cannot change array spare. This error message appears if you try to change the number of spares in an array when the configuration does not support the addition or subtraction of spares. 2832 Invalid physical drive.
  • Page 44 Error code Error message Comment or clarification 2851 Invalid RAID Array ID. The scripted RAID Array ID is invalid. Use characters from the set a–z, A–Z, 0–9, !, @, #, *, (, ), ,, -, _, +, :, ., /, and [space].

  • Page 45: Using Hplpcfg

    Error code Error message Comment or clarification 2882 Invalid value for MNPDelay. Valid range — is 0 (disabled) to 60 minutes. 2883 Invalid controller configuration value. — Expecting Yes or No. 2884 Invalid value for QueueDepth. Valid range — is from 2 to 32, or Auto. Using HPLPCFG You must edit the text file to insert the WWID of the boot volume and the LUN number that the WWID boots from.

  • Page 46: Hplpcfg Command-Line Examples

    Value Meaning There was no adapter or Emulex HBA found on this host. There was an error retrieving the I/O address. The WWID was invalid because of one of the following: An invalid value for WWID and BootDeviceWWID, and not a hex value The WWID specified for HBA in the .ini file does not match any HBAs found on the host (for the /l option only) The LUN was invalid.

  • Page 47: Lo100Cfg Command-Line Arguments

    LO100CFG command-line arguments Command-line argument Description This argument displays example XML to perform configuration. This argument outputs the current copyright and version information and then exits. This argument captures the current status and outputs it to the console. The argument lists basic command line arguments and supported XML tags.

  • Page 48: Using Hpqlarep

    <serial_port mode="dedicated" /> <nic mode="dhcp"> <ipv4 address="10.10.10.18" mask="255.255.252.0" gateway="10.10.10.1" /> <firewall http_active="yes" ping_active="yes" telnet_active="yes" /> </nic> <users> <user id="1" name="" privilege_level="user" /> <user id="2" name="operator" privilege_level="operator" /> <user id="3" name="admin" privilege_level="admin" /> <user id="4" name="oem" privilege_level="oem" /> </users> </lo100cfg> To disable the shared NIC configuration and make the Lights-Out 100 NIC dedicated, enter the following in your data file: <lo100cfg>...

  • Page 49: Hpqlarep Return Codes

    HPQLAREP return codes Value Meaning The command was completed successfully. There was an invalid command line option. There was a file open error. There was an NVRAM checksum error. There was an NVRAM data error. There was no adapter found on this host. There was an error retrieving the I/O address.

  • Page 50: Using Hponcfg

    You must then invoke the tool to load the contents of hba.ini input to the HBA NVRAM: hpqlarep /l hba.ini. Using HPONCFG HP offers support for the iLO features available on HP ProLiant servers with the HPONCFG utility. HPONCFG is an online configuration tool used to set up and reconfigure iLO without requiring a reboot of the server operating system.

  • Page 51: Hponcfg Return Codes

    HPONCFG return codes Value Meaning The script was sent successfully to the device. The script could not be sent to the device. If the script itself fails, errors are reported in the log file created by HPONCFG. HPONCFG command file contents HPONCFG can be used to perform the following tasks: Obtain an entire configuration Obtain a specific configuration...

  • Page 52: Obtaining A Specific Configuration

    <DHCP_STATIC_ROUTE VALUE = "Y"/> <DHCP_WINS_SERVER VALUE = "Y"/> <REG_WINS_SERVER VALUE = "Y"/> <PRIM_WINS_SERVER value = "16.16.6.161"/> <STATIC_ROUTE_1 DEST = "0.0.0.0" GATEWAY = "0.0.0.0"/> <STATIC_ROUTE_2 DEST = "0.0.0.0" GATEWAY = "0.0.0.0"/> <STATIC_ROUTE_3 DEST = "0.0.0.0" GATEWAY = "0.0.0.0"/> </MOD_NETWORK_SETTINGS> <ADD_USER USER_NAME = "Administrator" USER_LOGIN = "Administrator"...

  • Page 53: Setting A Configuration

    <REMOTE_CONSOLE_PORT VALUE="23"/> <TERMINAL_SERVICES_PORT VALUE="3389"/> <VIRTUAL_MEDIA_PORT VALUE="17988"/> <MIN_PASSWORD VALUE="4"/> </GET_GLOBAL_SETTINGS> Setting a configuration A specific configuration can be sent to the iLO by using the command format: HPONCFG /f add_user.xml /l log.txt In this example, the input file has the following contents: <!-- Add user with minimal privileges to test default setting of assigned privileges to 'N' -->...

  • Page 54: Troubleshooting

    5 Troubleshooting Troubleshooting table Issue Troubleshooting Data loss in STK Improper use of the Scripting Toolkit utilities and modification of the CONREP data files can result in loss of critical data. Because of the potential data-loss risk, only experienced individuals should use the Scripting Toolkit utilities.

  • Page 55: Support And Other Resources

    6 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: Software product name Hardware product model number Operating system type and version Applicable error message Third-party hardware or software Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support:...

  • Page 56: Typographic Conventions

    Typographic conventions Table 1 Document conventions Convention Element Blue text: Table 1 (page 56) Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.com Website addresses Bold text Keys that are pressed Text typed into a GUI element, such as a box GUI elements that are clicked or selected, such as menu and list items, buttons, tabs, and check boxes Italic text...
  • Page 57 environment through HP Insight Online, and is also the recommended version for HP Proactive Care Service. HP Insight Remote Support Advanced supports medium-sized to large environments with up to 3,500 devices. It can be installed on a Windows ProLiant hosting device or a Windows ESXi Virtual Machine and requires HP Systems Insight Manager.

  • Page 58: Documentation Feedback

    7 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.

  • Page 59: Acronyms And Abbreviations

    Acronyms and abbreviations Array Configuration Utility Advanced Data Guarding (also known as RAID 6) application program interface BIOS Basic Input/Output System CONREP Configuration Replication utility CPQACUXE Array Configuration Utility XE CPQLOCFG Lights-Out Configuration Utility DHCP Dynamic Host Configuration Protocol disk operating system graphical user interface host bus adapter HPDISCOVERY...
  • Page 60 Wake-on LAN WWID World Wide ID World Wide Name WWPN worldwide port name extensible markup language Acronyms and abbreviations...

  • Page 61: Index

    Index control category, controller category, acronyms and abbreviations, HBA category, ACU script file, logical drive category, array configurations HPDISCOVERY, erasing, arguments, command-line examples, command-line syntax, clearing a configuration, customizing deployment scripts, configuration queries, 12, capturing, return codes, target server, HPLPCFG, configurations arguments, capturing,...
  • Page 62 command-line syntax, return codes, video performance optimization, logical drive capacity extension, websites, MaxBoot setting, Windows Preinstallation Environment, adding drivers to version 3.0, adding drivers to version 4.0, network share creating, online help, Online ROM Flash Component Utility, operating system installation, operators and terms, RBSURESET, arguments,...

This manual is also suitable for:

Proliant ml310eProliant sl4540Proliant sl4545Scripting toolkit for windows

Table of Contents