HP ProLiant SCCM 2012 Integration Kit

(v 2012.08.0) User Guide

Abstract
This 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-001

Published: September 2012
Edition: 1

 Copyright 2012 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.
Acknowledgments
Microsoft, Windows, Windows XP, and Windows NT are U.S. registered trademarks of Microsoft Corporation.

Contents
1 Introduction...............................................................................................4
2 Support matrix...........................................................................................5
Supported System Center products..............................................................................................5
Supported target operating systems.............................................................................................5
Supported target servers............................................................................................................5

3 Installing and configuring the HP ProLiant SCCM 2012 Integration Kit................6

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

4 Deploying Windows Server to ProLiant servers...............................................9

5 Collecting extended inventory data.............................................................11
6 Reference................................................................................................12
Console ...............................................................................................................................12
Scripted install task sequence...................................................................................................13
Hardware configuration tasks...................................................................................................13
Post-OS configuration tasks......................................................................................................15
Inventory tool data..................................................................................................................16

7 Troubleshooting........................................................................................17
The target server boots to WinPE but the task sequence doesnt start.............................................17
Updated or new hardware configuration input files were not used ................................................17
After rebooting during the task sequence, the target server reports Invalid system disk or BOOTMGR
is missing..............................................................................................................................17
The target server fails to join the domain....................................................................................17
The inventory tool is installed but does not run............................................................................17
The inventory tool runs but data is not collected..........................................................................18

8 Support and other resources......................................................................19

Information to collect before contacting HP.................................................................................19
How to contact HP..................................................................................................................19
Registering for software technical support and update service.......................................................19
How to use your software technical support and update service...............................................19
Warranty information.........................................................................................................20
HP authorized resellers............................................................................................................20
Related information.................................................................................................................20
Typographic conventions.........................................................................................................20

9 Documentation feedback...........................................................................22
Glossary....................................................................................................23

Contents

1 Introduction
The 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 Hardware
Inventory Client Agent

A dynamic collection that represents all HP ProLiant servers

The 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:

Included component

Version

HP Service Pack for ProLiant

2012.08.0

HP Scripting Toolkit

9.20

Introduction

2 Support matrix
Supported System Center products
The kit can be installed on the following version of SCCM:
SCCM 2012

Supported target operating systems

The following operating system can be deployed to the target servers:
Windows Server 2008 R2 x64 (SP and edition agnostic)

Supported target servers

The following servers can be deployed to and maintained:
ProLiant BL2x220c G7

ProLiant BL685c G7

ProLiant DL385 G7

ProLiant BL420c Gen8

ProLiant DL120 G7

ProLiant DL385p Gen8

ProLiant BL460c G7

ProLiant DL160 Gen8

ProLiant DL560 Gen8

ProLiant BL460c Gen8

ProLiant DL320e Gen8

ProLiant DL580 G7

ProLiant BL465c G7

ProLiant DL360 G7

ProLiant DL585 G7

ProLiant BL465c Gen8

ProLiant DL360e Gen8

ProLiant ML110 G7

ProLiant BL490c G7

ProLiant DL360p Gen8

ProLiant ML310e Gen8

ProLiant BL620c G7

ProLiant DL380 G7

ProLiant ML350e Gen8

ProLiant BL660c Gen8

ProLiant DL380e Gen8

ProLiant ML350p Gen8

ProLiant BL680c G7

ProLiant DL380p Gen8

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 disks
available (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

3 Installing and configuring the HP ProLiant SCCM 2012

Integration 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 these
files and scripts, make a backup copy before upgrading.

Installation
1.

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 Microsoft
System Center image by executing [Link]. Click Install, then click HP SCCM 2012
Integration Kit.

3.
4.

On the License Agreement screen, click Agree.

On the Verify Prerequisites screen, click Verify.
If the verification fails, make the necessary corrections and click Verify again.

Installing and configuring the HP ProLiant SCCM 2012 Integration Kit

5.
6.

When the verification is successful, click Next.

On the Install screen, click Install.

7.
8.

When the installation is complete, click Next.

On the Configure screen, click Configure.

Installation

9.

On the Summary screen, click Close.

The installation log is named [Link] and is located in the

Windows directory.

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

Description

Distributing driver packages and boot images to the local Copies the driver packages and boot image to the
distribution point
distribution point on the site server. Updates the boot image
to the distribution point, which causes the associated drivers
to be injected.
NOTE: Additionally copies and updates the provided Boot
Image (x86) to the distribution point on the site server. HP
only provides a WinPE x64 boot image while SCCM
requires both an x86 and x64 image to be available on
the WDS server.
Distributing software packages to the local distribution
point

Copies the software packages to the distribution point on

the site server.

Configuring inventory support

Configures the hardware inventory agent to collect IDMIF

and NOIDMIF files and increases the max custom MIF file
size to 512 KB.
Imports the inventory class definitions. Advertises the
inventory tool program to the HP ProLiant Servers collection
on a schedule recurring every Sunday.
NOTE: The inventory tool schedule can be changed later.

Installing and configuring the HP ProLiant SCCM 2012 Integration Kit

4 Deploying Windows Server to ProLiant servers

Deploying 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 process
of deploying to server hardware, HP provides a wizard to help you create a scripted install task
sequence 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:

2.

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 the
appropriate distribution points, and are available via a package share.

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

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

Create a new task sequence.

To open the wizard, on the Software Library pane, select Operating SystemsTask Sequences
and then click Create HP ProLiant Deployment Task Sequence in the ribbon bar.

3.

Optionally, configure the new task sequence.

NOTE:

4.

HP recommends setting an Administrator password and joining the domain.

Deploy the task sequence to a collection

The following options need to be selected:

5.

On the Deployment Settings screen, set Purpose = Required and check Make this task
sequence available to boot media and PXE.

On the Schedule screen, add a mandatory assignment of As soon as possible.

On the Distribution Points screen, set Deployment options = Access content directly from
a distribution point when needed by the running task sequence.

Import a target server and assign it to the collection.

IMPORTANT: You must specify both the SMBIOS GUID and the PXE NIC MAC address. The
SMBIOS GUID is necessary in order that the SCCM agent can match the target server in the
SCCM database, avoiding the NIC ordering problem. The PXE NIC MAC address is required
for 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 by
default, 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 the
appropriate HP ProLiant boot image. Mount the generated ISO file in the target servers iLO
virtual CD/DVD-ROM and then power on the target server.

7.

10

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 additional
management products.
Management product

Action

Systems Center Operations Manager

Push the SCOM agent.

HP Systems Insight Manager

Perform the Configure & Repair Agents action to push

credentials.

Deploying Windows Server to ProLiant servers

5 Collecting extended inventory data

The HP ProLiant Inventory Tool collects extended ProLiant hardware and software information that
can be used to create enhanced collections and reports. For a listing of the tables and fields, see
the 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:

2.

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

The inventory class definitions are imported.

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

Deploy the package to a collection.

To open the wizard, right-click on the HP ProLiant Inventory Tool package, select Deploy, and
follow the prompts.
The following option needs to be selected:

On the Scheduling screen, add a mandatory assignment of a recurring schedule.

NOTE: HP recommends using a recurring schedule so that future hardware and software
changes are collected.
To view the inventory data for a managed server:
1. Right-click on the server and select StartResource Explorer.
2. Expand the Hardware node.
3. View the nodes starting with HP.
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 SCCM
directions for adding additional classes.
The following options need to be selected:

On the Connect to Windows Management Instruction (WMI) dialog, set Computer name to a
server running the latest HP Insight Management WBEM Providers, set WMI namespace to
root\hpq, check Recursive, and if necessary specify credentials.

On the Add Hardware Inventory Class dialog, select one or more classes. For details regarding
the classes, refer to the HP Insight Management WBEM Providers User Guide located at http://
[Link]/products/servers/management/wbem/[Link].

11

6 Reference
Console

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

12

The Packages folder contains the following software packages:

Package

Description

HP ProLiant Configuration Manager Client Package

The SCCM agent used during the scripted install task

sequence.

HP ProLiant Hardware Configuration

STK utilities and input files.

HP ProLiant Inventory Tool

Inventory tool.

HP ProLiant Post-OS Configuration

Drivers and agents.

HP ProLiant Reboot Script

Support for task sequence state management and

multiple reboots.

The Drivers folder contains the latest HP Windows Server drivers. When upgrading, the existing
drivers are replaced with new drivers.

The Driver Packages folder contains HP ProLiant driver packages that reference the HP drivers.
After upgrading, the task sequences will not have to be updated.

The Boot Images folder contains the HP ProLiant WinPE boot image.

The Device Collection folder contains the HP ProLiant Servers dynamic collection.

Reference

Scripted install task sequence

Figure 1 Task sequence

The task sequence is divided into three stepsConfigure Hardware, Prepare Storage, and Install
Operating System. The names of the steps and tasks indicate their function.
NOTE: The tasks that appear in the Configure Hardware step depend on the selections made in
the Create Server Deployment Task Sequence dialog.
A computer variable and conditions on the three steps are used to control the processing of the
task sequence across multiple reboots. The Set RebootStep Variable task increments the RebootStep
variable by 1 each time it is executed. If the variable is not present, it is created and set to 0 before
being incremented.
During the initial execution of the task sequence, the tasks in the Configure Hardware step get
executed. Upon rebooting and re-executing the task sequence, the Set RebootStep Variable task
increments RebootStep to 2, causing the tasks in the Prepare Storage step to be executed. Upon
rebooting and re-executing the task sequence, the Set RebootStep Variable task will increment
RebootStep to 3, causing the tasks in the Install Operating System step to be executed.
The Reset RebootStep Variable task now resets RebootStep back to 0 so that the final reboot
task 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 or
reset the RebootStep variable as follows:
1. Right-click on the target server and select Clear Required PXE Deployments.
2. Right-click on the target server and select Properties.
3. Click the Variables tab.
4. Either delete the RebootStep variable or set its value to 0.

Hardware configuration tasks

The hardware configuration tasks provided are listed in Table 1 (page 14).

Scripted install task sequence

13

Table 1 Hardware configuration tasks

Task

Description

Underlying STK utility

Boot Order

Sets the system boot order. Setting PXE first in the boot order is
required.

[Link]

BIOS

Sets the system BIOS configuration.

[Link] or
[Link]

Smart Array

Sets the Smart Array RAID configuration.

[Link]

iLO

Sets the iLO 2 or later configuration.

[Link]

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: The Set BIOS Configuration task supports all ProLiant generations. If you use a custom
conrep or hprcu input file, the task sequence will become ProLiant generation specific. For
example, if you specify a custom conrep input file, the task sequence will fail on ProLiant Gen8 or
later target servers.
There is a custom task editor for each task. For example:

The file / parameters combo box allows selecting one of the provided filenames/parameters or
typing in a custom filename/parameters. The pre-supplied files are located in .\OSD\Lib\
Packages\Deployment\HP\ProLiant\HWConfig. The files provided are listed in Table 2
(page 14).
Table 2 Pre-supplied files

14

File

Description

[Link]

Does not set anything

[Link]

Does not set anything

[Link]

Creates a default configuration

[Link]

Creates one array with RAID 0

[Link]

Creates one array with RAID 1 (requires two drives)

[Link]

Creates one array with RAID 5 (requires three or more drives)

[Link]

Does not set anything

Reference

Table 2 Pre-supplied files (continued)

File

Description

[Link]

Enables Remote Desktop pass-through

[Link]

Enables agentless management on iLO4-based servers. This file may require

editing before being used.

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:

3.
4.

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

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

In the task editor, in the file box, specify the new filename.
Update the HP ProLiant Hardware Configuration package to the appropriate distribution
points.

Post-OS configuration tasks

The Copy HP ProLiant Post-OS Configuration task is tied to the HP ProLiant Post-OS Configuration
package. When executed it copies the contents of the package to c:\$oem$. This is necessary to
get the files onto the local server before the operating system is installed in case there is no network
connectivity after the operating system is installed.
The Perform HP ProLiant Post-OS Configuration task executes c:\$oem$\[Link]. The
script 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 Insight

Management WBEM Providers, and on ProLiant Gen8 servers the HP ProLiant Agentless
Management Service.

To customize the Perform HP ProLiant Post-OS Configuration task:

1. Browse to .\OSD\Lib\Packages\Deployment\HP\ProLiant\PostOSConfig.
2. Edit [Link] as needed.
NOTE: HP recommends not removing commands already present, and to keep a backup
copy of any customizations as this file is overwritten during an upgrade.
3.
4.

If necessary, copy any additional files referenced in [Link] to this folder.

Update the HP ProLiant Post-OS Configuration package to appropriate distribution points.

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

Post-OS configuration tasks

15

Inventory tool data

The inventory tool is a command-line utility. When executed, it generates HP#.mif files in the
NOIDMIF 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
Name

Value (example data)

Enclosure

Enc001

Bay

Table 4 HP ProLiant system summary

Name

Value (example data)

Model

ProLiant BL465c G7

Serial Number

AQQ1620FJ3

GUID

9032393F-3000-0000-ABCD-303D30A652BB

CPU1

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

DIMM1

8.00 GB Physical Memory Module 1 on Processor Board 1

Management Processor

Smart Array Controller1

Integrated Lights Out 3 (iLO3)

Smart Array P410i in Slot 0

Smart Array Disk

68.37 GB Port:1I Box:1 Bay:1

Network Adapter

HP NC551i Dual Port FlexFabric 10Gb Converged Network Adapter

Item can be repeated

Table 5 HP ProLiant version control

Type

Component (example data)

Version (example data)

Bundle

proliantfw

2012.02.0.51

Software1

HP ProLiant Array Configuration Utility for Windows ([Link]) [Link]

Software1

HP ProLiant Integrated Lights-Out Management Interface Driver for

Windows Server 2003/2008 x64 Editions ([Link])

[Link]

Firmware

BladeSystem c3000 Enclosure

3.50

Firmware

A19 (Active)

2011.12.28

Firmware

A19 (Redundant)

2011.12.10

Firmware

PIC

1.6

Firmware1

Integrated Lights Out 3 (iLO3) (Active)

1.28

Firmware1

Smart Array P410i in Slot 0

5.14

Firmware1

Disk EH0146FAWJB Port:1I Box:1 Bay:1

HPDH

Firmware1

HP NC551i Dual Port FlexFabric 10Gb Converged Network Adapter [Link]

(Boot Code)

16

Item type and component can be repeated

Reference

7 Troubleshooting
The target server boots to WinPE but the task sequence doesnt start
There 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 network
driver

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 used

To resolve this issue, update the HP ProLiant Hardware Configuration package to the appropriate
distribution points

After rebooting during the task sequence, the target server reports Invalid
system disk or BOOTMGR is missing
There are several possible causes:

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

An error occurred during the Install Operating System step

To resolve this issue:

Ensure that PXE is first in the boot order.

Resolve the error that occurred in the Install Operating System step.

The target server fails to join the domain

When performing a Windows deployment to some servers with Broadcom network adapters, the
deployment is successful but the target server fails to join the domain.
To resolve this issue:

Manually join the domain on the target server.

Add a Join Domain or Workgroup task before the Reset Reboot Variable task. Configure the
new task to be identical to the Apply Network Settings task.

The inventory tool is installed but does not run

To resolve this issue, copy the package to a distribution point and advertise it, on a schedule, to
a collection.

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

17

The inventory tool runs but data is not collected

To resolve this issue, ensure that the Hardware Inventory Client Agent is scheduled to run and
configured to collect IDMIF and NOIDMIF files, and ensure that the HP Insight Management WBEM
Providers are installed on the target server.

18

Troubleshooting

8 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:

See the Contact HP worldwide website:

[Link]

Use the Contact HP link on the HP Support Center website:

[Link]

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

Registering for software technical support and update service

Insight 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 software
implementation or operations problems.
The service also provides access to software updates and reference manuals in electronic form as
they are made available from HP. Customers who purchase an electronic license are eligible for
electronic updates.
With this service, Insight Management customers benefit from expedited problem resolution as
well as proactive notification and delivery of software updates. For more information about this
service, see the following website:
[Link]
Registration for this service takes place following online redemption of the license certificate.

How to use your software technical support and update service

As HP releases updates to software, the latest versions of the software and documentation are
made 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:
[Link]
After creating your profile and linking your support agreements to your profile, see the Software
Updates and Licensing portal at [Link] to obtain
software, documentation, and license updates.

Information to collect before contacting HP

19

Warranty information
HP will replace defective delivery media for a period of 90 days from the date of purchase. This
warranty applies to all Insight Management products.

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

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

[Link]

In other locations, see the Contact HP worldwide website:

[Link]

Related information

HP Insight Control for Microsoft System Center documentation website:

[Link]

HP Insight Management WBEM Providers documentation

HP Insight Management Agents documentation

HP ProLiant servers:
[Link]

Typographic conventions
This document uses the following typographical conventions:
Book title
The title of a book. On the web, this can be a hyperlink to the
book itself.

20

Command

A command name or command phrase, for example ls -a.

Computer output

Information displayed by the computer.

Ctrl+x or Ctrl-x

A key sequence that indicates you must hold down the keyboard
key labeled Ctrl while you press the letter x.

ENVIRONMENT VARIABLE

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

Key

The name of a keyboard key. Return and Enter both refer to the
same 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 required

content.

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

...

Indicates that the preceding element can be repeated one or more

times.

WARNING

An alert that calls attention to important information that, if not

understood or followed, results in personal injury.

Support and other resources

CAUTION

An alert that calls attention to important information that, if not

understood or followed, results in data loss, data corruption, or
damage 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

9 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@[Link]). Include the document title and part number, version number, or the URL
when submitting your feedback.

22

Documentation feedback

Glossary
CDM

Custom Data Manager

DMC

Device Monitor Console

DMS

Device Monitor Service

OSD

Operating System Deployment

PSP

HP ProLiant Support Pack

SCCM

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

23