hp proliant sccm 2012 integration kit

7/24/2019 HP ProLiant SCCM 2012 Integration Kit

1/23

HP ProLiant SCCM 2012 Integration Kit(v 2012.08.0) User Guide

AbstractThis guide describes the procedures and prerequisites for installing and using the HP ProLiant SCCM 2012 Integration Kit,which provides support for deploying ProLiant servers.

HP Part Number: 707356-001Published: September 2012Edition: 1


2/23

Copyright 2012 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid l icense 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.

Acknowledgments

Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.


3/23

Contents

1 Introduction...............................................................................................42 Support matrix...........................................................................................5

Supported System Center products..............................................................................................5Supported target operating systems.............................................................................................5

Supported target servers............................................................................................................53 Installing and configuring the HP ProLiant SCCM 2012 Integration Kit................6

Considerations.........................................................................................................................6Installation...............................................................................................................................6Configuration...........................................................................................................................8

4 Deploying Windows Server to ProLiant servers...............................................95 Collecting extended inventory data.............................................................116 Reference................................................................................................12

Console ...............................................................................................................................12Scripted install task sequence...................................................................................................13

Hardware configuration tasks...................................................................................................13Post-OS configuration tasks......................................................................................................15Inventory tool data..................................................................................................................16

7 Troubleshooting........................................................................................17The target server boots to WinPE but the task sequence doesnt start.............................................17Updated or new hardware configuration input files were not used ................................................17

After rebooting during the task sequence, the target server reports Invalid system disk or BOOTMGRis missing..............................................................................................................................17The target server fails to join the domain....................................................................................17The inventory tool is installed but does not run............................................................................17The inventory tool runs but data is not collected..........................................................................18

8 Support and other resources......................................................................19Information to collect before contacting HP.................................................................................19How to contact HP..................................................................................................................19Registering for software technical support and update service.......................................................19

How to use your software technical support and update service...............................................19Warranty information.........................................................................................................20

HP authorized resellers............................................................................................................20Related information.................................................................................................................20Typographic conventions.........................................................................................................20

9 Documentation feedback...........................................................................22

Glossary....................................................................................................23

Contents 3


4/23

1 IntroductionThe HP ProLiant SCCM 2012 Integration Kit provides the following for SCCM:

Support for deploying ProLiant servers via the SCCM OSD feature

Extended ProLiant inventory data in the SCCM Resource Explorer via the SCCM HardwareInventory Client Agent

A dynamic collection that represents all HP ProLiant serversThe kit contains:

HP Service Pack for ProLiant Windows Server drivers and smart components

HP Scripting Toolkit WinPE hardware configuration utilities

What's New in this release:

VersionIncluded component

2012.08.0HP Service Pack for ProLiant

9.20HP Scripting Toolkit

4 Introduction


5/23

2 Support matrix

Supported System Center productsThe kit can be installed on the following version of SCCM:

SCCM 2012

Supported target operating systemsThe following operating system can be deployed to the target servers:

Windows Server 2008 R2 x64 (SP and edition agnostic)

Supported target serversThe following servers can be deployed to and maintained:

ProLiant DL385 G7ProLiant BL685c G7ProLiant BL2x220c G7

ProLiant DL385p Gen8ProLiant DL120 G7ProLiant BL420c Gen8

ProLiant DL560 Gen8ProLiant DL160 Gen8ProLiant BL460c G7

ProLiant DL580 G7ProLiant DL320e Gen8ProLiant BL460c Gen8

ProLiant DL585 G7ProLiant DL360 G7ProLiant BL465c G7

ProLiant ML110 G7ProLiant DL360e Gen8ProLiant BL465c Gen8

ProLiant ML310e Gen8ProLiant DL360p Gen8ProLiant BL490c G7

ProLiant ML350e Gen8ProLiant DL380 G7ProLiant BL620c G7

ProLiant ML350p Gen8ProLiant DL380e Gen8ProLiant BL660c Gen8

ProLiant DL380p Gen8ProLiant BL680c G7

Restrictions

Configuring iSCSI and FC HBAs is not supported. They need to be preconfigured.

Performing a correct deployment to servers with multiple storage controllers or multiple disksavailable (either multiple DAS or SAN attach) is not supported by default.

Performing a deployment to servers with iSCSI storage is only supported on HP NC55#controllers.

Performing a PXE-based deployment through HP NC54# network adapters is not supported.

Supported System Center products 5


6/23

3 Installing and configuring the HP ProLiant SCCM 2012Integration Kit

Considerations Do not install HP Insight Control server deployment and SCCM on the same network because

they both contain PXE servers.

When upgrading, HP supplied files and scripts are overwritten. If you have modified thesefiles and scripts, make a backup copy before upgrading.

Installation1. Ensure that the following prerequisites are met:

This is the SCCM primary site server with the console installed.

The logged in user has administrator level privileges.

The version of SCCM is at least 2012 or later.

Microsoft .NET Framework 4.0 is installed.

All local SCCM consoles are closed.

2. On the SCCM primary site server, start the installation from the HP Insight Control for MicrosoftSystem Center image by executingautorun.exe. ClickInstall, then clickHP SCCM 2012Integration Kit.

3. On theLicense Agreementscreen, clickAgree.4. On theVerify Prerequisitesscreen, clickVerify.

If the verification fails, make the necessary corrections and click Verifyagain.

6 Installing and configuring the HP ProLiant SCCM 2012 Integration Kit


7/23

5. When the verification is successful, clickNext.6. On theInstallscreen, clickInstall.

7. When the installation is complete, clickNext.8. On theConfigurescreen, clickConfigure.

Installation 7


8/23

9. On theSummaryscreen, clickClose.

The installation log is namedhpproliantsccm2012kit-install.logand is located in theWindows directory.

ConfigurationThe installer performs the following configuration tasks. If you choose to skip any of the configurationtasks or any of them are unsuccessful, you must manually perform the following actions.

DescriptionTask

Copies the driver packages and boot image to thedistribution point on the site server. Updates the boot image

Distributing driver packages and boot images to the localdistribution point

to the distribution point, which causes the associated driversto be injected.

NOTE:Additionally copies and updates the provided BootImage (x86)to the distribution point on the site server. HPonly provides a WinPE x64 boot image while SCCMrequires both an x86 and x64 image to be available onthe WDS server.

Copies the software packages to the distribution point onthe site server.

Distributing software packages to the local distributionpoint

Configures the hardware inventory agent to collect IDMIFand NOIDMIF files and increases the max custom MIF filesize to 512 KB.Imports the inventory class definitions. Advertises the

inventory tool program to the HP ProLiant Servers collectionon a schedule recurring every Sunday.

Configuring inventory support

NOTE:The inventory tool schedule can be changed later.

8 Installing and configuring the HP ProLiant SCCM 2012 Integration Kit


9/23

4 Deploying Windows Server to ProLiant serversDeploying Windows Server follows the standard SCCM OSD methodologycreate a task sequence,configure the task sequence, and deploy the task sequence to a collection. To simplify the processof deploying to server hardware, HP provides a wizard to help you create a scripted install tasksequence for deploying Windows Server to ProLiant servers.

To perform a Windows Server scripted install to a ProLiant server:

1. Ensure that the following conditions are met:

WDS and SCCM are properly configured for use with OSD and PXE functionality.

A purpose-specific collection exists.

One or more Operating System Install Packages have been added and copied to theappropriate distribution points, and are available via a package share.

The Hardware Inventory Client Agent is scheduled and configured to collect IDMIF andNOIDMIF files.

If you are using SNMP for server management, the SNMP read community string is setin your domain policy.

2. Create a new task sequence.

To open the wizard, on theSoftware Librarypane, selectOperating SystemsTask Sequencesand then clickCreate HP ProLiant Deployment Task Sequencein the ribbon bar.

9


10/23

3. Optionally, configure the new task sequence.

NOTE: HP recommends setting an Administrator password and joining the domain.

4. Deploy the task sequence to a collection

The following options need to be selected:

On theDeployment Settingsscreen, set Purpose =Requiredand checkMake this tasksequence available to boot media and PXE.

On theSchedulescreen, add a mandatory assignment of As soon as possible.

On theDistribution Pointsscreen, set Deployment options =Access content directly froma distribution point when needed by the running task sequence.

5. Import a target server and assign it to the collection.

IMPORTANT: You must specify both the SMBIOS GUID and the PXE NIC MAC address. TheSMBIOS GUID is necessary in order that the SCCM agent can match the target server in theSCCM database, avoiding the NIC ordering problem. The PXE NIC MAC address is requiredfor the Clear Required PXE Deployment functionality.

6. Power on the target server so that it can connect to SCCM and begin the deployment process.There are two possibilities: PXE and iLO Virtual Media.To use PXE, the target server must be forced to boot PXE the first time. This is because bydefault, on ProLiant servers, PXE is not first in the boot order. When using c-Class blades,Onboard Administrator can be used to force a PXE boot and to power on the blade.

To use iLO Virtual Media, in the SCCM console create task sequence media based upon theappropriate HP ProLiant boot image. Mount the generated ISO file in the target servers iLOvirtual CD/DVD-ROM and then power on the target server.

7. The deployment process installs the HP management agents. When the deployment is complete,the following action may be necessary to have the target server managed by additionalmanagement products.

ActionManagement product

Push the SCOM agent.Systems Center Operations Manager

Perform the Configure & Repair Agents action to pushcredentials.

HP Systems Insight Manager

10 Deploying Windows Server to ProLiant servers


11/23

5 Collecting extended inventory dataThe HP ProLiant Inventory Tool collects extended ProLiant hardware and software information thatcan be used to create enhanced collections and reports. For a listing of the tables and fields, seethe Inventory tool data section(page 16).

The inventory tool is executed as part of the default task sequence to collect initial inventory data.

To run the inventory tool for future hardware or software changes:1. Ensure that the following conditions are met:

The Hardware Inventory Agent is scheduled and configured to collect IDMIF and NOIDMIFfiles.

The inventory class definitions are imported.

The managed servers have the HP Insight Management WBEM Providers installed.

2. Deploy the package to a collection.

To open the wizard, right-click on theHP ProLiant Inventory Toolpackage, selectDeploy, andfollow the prompts.

The following option needs to be selected: On theSchedulingscreen, add a mandatory assignment of a recurring schedule.

NOTE: HP recommends using a recurring schedule so that future hardware and softwarechanges are collected.

To view the inventory data for a managed server:

1. Right-click on the server and selectStartResource Explorer.2. Expand theHardwarenode.3. View the nodes starting withHP.

As an alternative or complement to the inventory tool, the Hardware Inventory Agent can be

configured to collect specific HP WMI classes. To collect HP WMI classes, follow the SCCMdirections for adding additional classes.

The following options need to be selected:

On theConnect to Windows Management Instruction (WMI)dialog, setComputer nameto aserver running the latest HP Insight Management WBEM Providers, set WMI namespacetoroot\hpq, checkRecursive, and if necessary specify credentials.

On theAdd Hardware Inventory Classdialog, select one or more classes. For details regardingthe classes, refer to theHP Insight Management WBEM Providers User Guidelocated athttp://h18004.www1.hp.com/products/servers/management/wbem/documentation.html.

11
http://h18004.www1.hp.com/products/servers/management/wbem/documentation.htmlhttp://h18004.www1.hp.com/products/servers/management/wbem/documentation.htmlhttp://h18004.www1.hp.com/products/servers/management/wbem/documentation.htmlhttp://h18004.www1.hp.com/products/servers/management/wbem/documentation.html


12/23

6 Reference

Console

The various components of the kit are integrated into the standard SCCM console folders.

ThePackagesfolder contains the following software packages:

DescriptionPackage

The SCCM agent used during the scripted install tasksequence.

HP ProLiant Configuration Manager Client Package

STK utilities and input files.HP ProLiant Hardware Configuration

Inventory tool.HP ProLiant Inventory Tool

Drivers and agents.HP ProLiant Post-OS Configuration

Support for task sequence state management andmultiple reboots.

HP ProLiant Reboot Script

TheDriversfolder contains the latest HP Windows Server drivers. When upgrading, the existingdrivers are replaced with new drivers.

TheDriver Packagesfolder contains HP ProLiant driver packages that reference the HP drivers.After upgrading, the task sequences will not have to be updated.

TheBoot Imagesfolder contains the HP ProLiant WinPE boot image. TheDevice Collectionfolder contains the HP ProLiant Servers dynamic collection.

12 Reference


13/23

Scripted install task sequence

Figure 1 Task sequence

The task sequence is divided into three stepsConfigure Hardware,Prepare Storage, andInstallOperating System. The names of the steps and tasks indicate their function.

NOTE: The tasks that appear in theConfigure Hardwarestep depend on the selections made intheCreate Server Deployment Task Sequencedialog.

A computer variable and conditions on the three steps are used to control the processing of thetask sequence across multiple reboots. TheSet RebootStep Variabletask increments the RebootStepvariable by 1 each time it is executed. If the variable is not present, it is created and set to 0 beforebeing incremented.

During the initial execution of the task sequence, the tasks in the Configure Hardwarestep getexecuted. Upon rebooting and re-executing the task sequence, the Set RebootStep VariabletaskincrementsRebootStepto 2, causing the tasks in the Prepare Storagestep to be executed. Uponrebooting and re-executing the task sequence, the Set RebootStep Variabletask will incrementRebootStepto 3, causing the tasks in the Install Operating Systemstep to be executed.

TheReset RebootStep Variabletask now resetsRebootStepback to 0 so that the final reboottask causes the machine to reboot to the newly deployed production operating system.

To rerun a task sequence on a target server, you must clear the PXE advertisement and clear orreset the RebootStep variable as follows:

1. Right-click on the target server and selectClear Required PXE Deployments.

2. Right-click on the target server and selectProperties.3. Click theVariablestab.4. Either delete theRebootStepvariable or set its value to 0.

Hardware configuration tasksThe hardware configuration tasks provided are listed inTable 1 (page 14).

Scripted install task sequence 13


14/23

Table 1 Hardware configuration tasks

Underlying STK utilityDescriptionTask

setbootorder.exeSets the system boot order. Setting PXE first in the boot order isrequired.

Boot Order

conrep.exeorhprcu.exe

Sets the system BIOS configuration.BIOS

hpacuscripting.exeSets the Smart Array RAID configuration.Smart Array

hponcfg.exeSets the iLO 2 or later configuration.iLO

The tasks are designed to set/write a configuration, not get/read/capture a configuration.

The Smart Array configuration task is designed to configure only internal controllers and disks,not network-based storage.

NOTE: TheSet BIOS Configurationtask supports all ProLiant generations. If you use a customconreporhprcuinput file, the task sequence will become ProLiant generation specific. Forexample, if you specify a custom conrep input file, the task sequence will fail on ProLiant Gen8 orlater target servers.

There is a custom task editor for each task. For example:

Thefile / parameterscombo box allows selecting one of the provided filenames/parameters ortyping in a custom filename/parameters. The pre-supplied files are located in .\OSD\Lib\Packages\Deployment\HP\ProLiant\HWConfig. The files provided are listed inTable 2(page 14).

Table 2 Pre-supplied files

DescriptionFile

Does not set anythingconrep-d.xml

Does not set anythinghprcu-d.xml

Creates a default configurationacu-rd.ini

Creates one array with RAID 0acu-r0.ini

Creates one array with RAID 1 (requires two drives)acu-r1.ini

Creates one array with RAID 5 (requires three or more drives)acu-r5.ini

Does not set anythinghponcfg-d.xml

14 Reference


15/23

Table 2 Pre-supplied files(continued)

DescriptionFile

Enables Remote Desktop pass-throughhponcfg-rdpassthrough.xml

Enables agentless management on iLO4-based servers. This file may requireediting before being used.

hponcfg-agentless.xml

To use a custom configuration file:

1. Browse to .\OSD\Lib\Packages\Deployment\HP\ProLiant\HWConfig.2. Create a new file by copying and editing an existing file, starting with a blank file, or using

an existing file.

NOTE:

HP recommends not editing any of the pre-supplied files since they are overwritten duringan upgrade.

Refer to the STK documentation for details about the file contents.

3. In the task editor, in thefilebox, specify the new filename.4. Update theHP ProLiant Hardware Configurationpackage to the appropriate distribution

points.

Post-OS configuration tasksTheCopy HP ProLiant Post-OS Configuration task is tied to theHP ProLiant Post-OS Configurationpackage. When executed it copies the contents of the package to c:\$oem$. This is necessary toget the files onto the local server before the operating system is installed in case there is no networkconnectivity after the operating system is installed.

ThePerform HP ProLiant Post-OS Configurationtask executesc:\$oem$\configure.cmd. Thescript performs the following tasks:

Installs various drivers such as networking and iLO.

Installs the SNMP feature.

Installs the HP System Management Homepage, HP Insight Management Agents, HP InsightManagement WBEM Providers, and on ProLiant Gen8 servers the HP ProLiant AgentlessManagement Service.

To customize thePerform HP ProLiant Post-OS Configurationtask:

1. Browse to.\OSD\Lib\Packages\Deployment\HP\ProLiant\PostOSConfig.2. Editconfigure.cmd as needed.

NOTE: HP recommends not removing commands already present, and to keep a backupcopy of any customizations as this file is overwritten during an upgrade.

3. If necessary, copy any additional files referenced inconfigure.cmdto this folder.4. Update theHP ProLiant Post-OS Configuration package to appropriate distribution points.

NOTE: To change which agents are installed by default, editinstall.cmd in the agents'subfolder. However, disabling agent installation may result in a loss of functionality.

Post-OS configuration tasks 15


16/23

Inventory tool dataThe inventory tool is a command-line utility. When executed, it generatesHP#.miffiles in theNOIDMIF directory. The information in these files is collected by the Hardware Inventory Client

Agent, populated into the SCCM database, and viewable in the Resource Explorer.

Table 3 HP ProLiant location

Value (example data)Name

Enc001Enclosure

5Bay

Table 4 HP ProLiant system summary

Value (example data)Name

ProLiant BL465c G7Model

AQQ1620FJ3Serial Number

9032393F-3000-0000-ABCD-303D30A652BBGUID

AMD Opteron(TM) Processor Family 2.3 GHz (x64 Family 16 Model 9 Stepping 1)

Processor in socket 1

CPU1

8.00 GB Physical Memory Module 1 on Processor Board 1DIMM1

Integrated Lights Out 3 (iLO3)Management Processor 1

Smart Array P410i in Slot 0Smart Array Controller1

68.37 GB Port:1I Box:1 Bay:1Smart Array Disk 1

HP NC551i Dual Port FlexFabric 10Gb Converged Network AdapterNetwork Adapter 1

1 Item can be repeated

Table 5 HP ProLiant version control

Version (example data)Component (example data)Type

2012.02.0.51proliantfwBundle1

9.0.24.0HP ProLiant Array Configuration Utility for Windows (cpqacuxe.exe)Software1

1.15.0.0HP ProLiant Integrated Lights-Out Management Interface Driver forWindows Server 2003/2008 x64 Editions (CpqCiDrv.sys)

Software1

3.50BladeSystem c3000 EnclosureFirmware

2011.12.28A19 (Active)Firmware

2011.12.10A19 (Redundant)Firmware

1.6PICFirmware1

1.28Integrated Lights Out 3 (iLO3) (Active)Firmware1

5.14Smart Array P410i in Slot 0Firmware1

HPDHDisk EH0146FAWJB Port:1I Box:1 Bay:1Firmware1

4.0.493.0HP NC551i Dual Port FlexFabric 10Gb Converged Network Adapter(Boot Code)

Firmware1

1 Item type and component can be repeated

16 Reference


17/23

7 Troubleshooting

The target server boots to WinPE but the task sequence doesnt startThere are several possible causes:

There is no network connection because the network adapter is unsupported

There is no network connection because the boot image does not contain the necessary networkdriver

SCCM doesnt recognize the target server

One or more of the packages referenced by the task sequence are not available

To resolve this issue:

Install a supported network adapter and set it as the PXE NIC.

Use the appropriate HP ProLiant boot image.

Ensure that the target server was imported with the correct identification information.

Ensure that all referenced packages have been copied to a distribution point.

Updated or new hardware configuration input files were not usedTo resolve this issue, update the HP ProLiant Hardware Configuration package to the appropriatedistribution points

After rebooting during the task sequence, the target server reports Invalidsystem diskorBOOTMGR is missing

There are several possible causes:

The boot order was not set properly and causes the machine to boot to the hard drive insteadof PXE/USB to continue the task sequence

An error occurred during theInstall Operating Systemstep


Ensure that PXE is first in the boot order.

Resolve the error that occurred in theInstall Operating Systemstep.

The target server fails to join the domainWhen performing a Windows deployment to some servers with Broadcom network adapters, thedeployment is successful but the target server fails to join the domain.


Manually join the domain on the target server.

Add aJoin Domain or Workgrouptask before theReset Reboot Variabletask. Configure thenew task to be identical to the Apply Network Settingstask.

The inventory tool is installed but does not runTo resolve this issue, copy the package to a distribution point and advertise it, on a schedule, toa collection.

The target server boots to WinPE but the task sequence doesnt start 17


18/23

The inventory tool runs but data is not collectedTo resolve this issue, ensure that the Hardware Inventory Client Agent is scheduled to run andconfigured to collect IDMIF and NOIDMIF files, and ensure that the HP Insight Management WBEMProviders are installed on the target server.

18 Troubleshooting


19/23

8 Support and other resources

Information to collect before contacting HPBe 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 HPUse the following methods to contact HP technical support:

See the Contact HP worldwide website:

http://www.hp.com/go/assistance Use the Contact HP link on the HP Support Center website:

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

In the United States, call +1 800 334 5144 to contact HP by telephone. This service is available24 hours a day, 7 days a week. For continuous quality improvement, conversations might berecorded or monitored.

Registering for software technical support and update serviceInsight Management includes one year of 24 x 7 HP Software Technical Support and Update

Service. This service provides access to HP technical resources for assistance in resolving softwareimplementation or operations problems.

The service also provides access to software updates and reference manuals in electronic form asthey are made available from HP. Customers who purchase an electronic license are eligible forelectronic updates.

With this service, Insight Management customers benefit from expedited problem resolution aswell as proactive notification and delivery of software updates. For more information about thisservice, see the following website:

http://www.hp.com/services/insight

Registration for this service takes place following online redemption of the license certificate.

How to use your software technical support and update serviceAs HP releases updates to software, the latest versions of the software and documentation aremade available to you. The Software Updates and Licensing portal gives you access to software,documentation, and license updates for products on your HP software support agreement.

You can access this portal from the HP Support Center:

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

After creating your profile and linking your support agreements to your profile, see the SoftwareUpdates and Licensing portal at http://www.hp.com/go/hpsoftwareupdatesupportto obtainsoftware, documentation, and license updates.

Information to collect before contacting HP 19
http://www.hp.com/go/assistancehttp://www.hp.com/go/hpschttp://www.hp.com/services/insighthttp://www.hp.com/go/hpschttp://www.hp.com/go/hpsoftwareupdatesupporthttp://www.hp.com/go/hpsoftwareupdatesupporthttp://www.hp.com/go/hpschttp://www.hp.com/services/insighthttp://www.hp.com/go/hpschttp://www.hp.com/go/assistance


20/23

Warranty informationHP will replace defective delivery media for a period of 90 days from the date of purchase. Thiswarranty applies to all Insight Management products.

HP authorized resellersFor the name of the nearest HP authorized reseller, see the following sources:

In the United States, see the HP U.S. service locator website:

http://www.hp.com/service_locator

In other locations, see the Contact HP worldwide website:

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

Related information HP Insight Control for Microsoft System Center documentation website:

http://www.hp.com/go/icsc/docs

HP Insight Management WBEM Providers documentation

HP Insight Management Agents documentation

HP ProLiant servers:

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

Typographic conventionsThis document uses the following typographical conventions:

Book title The title of a book. On the web, this can be a hyperlink to thebook itself.

Command A command name or command phrase, for examplels -a.

Computer output Information displayed by the computer.Ctrl+xor Ctrl-x A key sequence that indicates you must hold down the keyboard

key labeledCtrlwhile you press the letterx.

ENVIRONMENT VARIABLE The name of an environment variable, for example,PATH.

Key The name of a keyboard key.Returnand Enterboth refer to thesame key.

Term A term or phrase that is defined in the body text of the document,not in a glossary.

User input Indicates commands and text that you type exactly as shown.

Replaceable The name of a placeholder that you replace with an actual value.[ ] In command syntax statements, these characters enclose optional

content.

{ } In command syntax statements, these characters enclose requiredcontent.

| The character that separates items in a linear list of choices.

... Indicates that the preceding element can be repeated one or moretimes.

WARNING An alert that calls attention to important information that, if notunderstood or followed, results in personal injury.

20 Support and other resources
http://www.hp.com/service_locatorhttp://www.hp.com/go/assistancehttp://www.hp.com/go/icsc/docshttp://h18013.www1.hp.com/products/servers/management/wbem/documentation.htmlhttp://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=3923526http://www.hp.com/go/prolianthttp://www.hp.com/go/prolianthttp://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=3923526http://h18013.www1.hp.com/products/servers/management/wbem/documentation.htmlhttp://www.hp.com/go/icsc/docshttp://www.hp.com/go/assistancehttp://www.hp.com/service_locator


21/23

CAUTION An alert that calls attention to important information that, if notunderstood or followed, results in data loss, data corruption, ordamage to hardware or software.

IMPORTANT An alert that calls attention to essential information.

NOTE An alert that contains additional or supplementary information.

TIP An alert that provides helpful information.

Typographic conventions 21


22/23

9 Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback([email protected]). Include the document title and part number, version number, or the URLwhen submitting your feedback.

22 Documentation feedback
mailto:[email protected]:[email protected]


23/23

GlossaryCDM Custom Data Manager

DMC Device Monitor Console

DMS Device Monitor Service

OSD Operating System Deployment

PSP HP ProLiant Support PackSCCM System Center Configuration Manager

SCOM System Center Operations Manager

SCUP System Center Updates Publisher

SCVMM System Center Virtual Machine Manager

SPP HP Service Pack for ProLiant

STK HP Scripting Toolkit

SUM HP Smart Update Manager

WSUS Windows Server Update Services

hp proliant sccm 2012 integration kit

Documents