HP ProLiant SCCM 2012 Integration Kit (v 2014.02.0) User Guide nl 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.
© Copyright 2014 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.
Contents 1 Introduction...............................................................................................4 2 Support matrix...........................................................................................5 Supported System Center products and target operating systems.....................................................5 Supported target servers............................................................................................................5 3 Installing and configuring....
1 Introduction The HP ProLiant SCCM 2012 Integration Kit provides the following for SCCM: • Drivers and driver packages for deploying ProLiant servers • Tool for collecting extended inventory data about ProLiant servers This release contains: • SCCM 2012 R2 support • Microsoft Windows Server 2012 R2 x64 / WinPE 5.0 x64 support • HP Service Pack for ProLiant 2014.02.0 Windows Server drivers This version of the kit introduces a new, more flexible design.
2 Support matrix Supported System Center products and target operating systems The kit can be installed on the following versions of SCCM and can deploy the following operating systems: Host OS \ SCCM SCCM 2012 SP1 CU1 or later SCCM 2012 R2 Windows Server 2008 R2 Windows Server 2008 R2 SP12 Windows Server 2008 R2 SP12 Windows Server 2012 1 Windows Server 2012 Windows Server 2012 R2 Windows Server 2012 Windows Server 2008 R2 SP12 Windows Server 2008 R2 SP12 Windows Server 2012 Windows Server 201
Restrictions: 6 • Hardware configuration is not supported by default. • 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 PXE-based deployment through the HP NC540-series and NC530SFP+ network adapters is not supported.
3 Installing and configuring Installing 1. 2. Ensure that the following prerequisites are met: • The server meets the requirements detailed in the Support Matrix. • The logged in user has administrator level privileges. 3. On the SCCM primary site server, start the installation from the HP Insight Control for Microsoft System Center image by executing autorun.exe. Click Install, then click HP SCCM 2012 Integration Kit. Click Accept. 4. Optionally, specify a directory to extract the package to.
7. Execute .\hpproliantsccmkit-install.ps1. The install script removes existing drivers (if necessary), copies the new drivers, imports the new drivers with useful names and rich categories, creates driver packages, copies the inventory tool, creates a software package for the tool, and copies the uninstall script. The installation log is named hpproliantsccmkit.log and is located in the Windows directory. IMPORTANT: Modification of the install script is not supported. Configuring 1.
5. Configure the Hardware Inventory Agent. a. On the Client Settings node, double-click Default Client Settings. b. In the left-hand pane, select Hardware Inventory. c. Set Maximum custom MIF file size (KB) = 512. d. Set Collect MIF file = Collect IDMIF and NOIDMIF files. e. Click Set Classes... f. For each of the .mof files in the \OSD\Lib\Packages\HP\ ProLiant\InventoryTool folder, click Import..., select the file, click Open, and then click Import.
4 Deploying Windows Server to ProLiant servers Deploying Windows Server follows the standard SCCM OSD methodology—create a task sequence, configure the task sequence, and deploy the task sequence to a collection. To deploy Windows Server to a ProLiant server: 1. Ensure that the following condition is met: 2. • All steps from the Configuring section have been successfully completed. • A purpose-specific collection exists. Create a new task sequence.
5 Deploying ProLiant firmware and software updates The ProLiant Updates Catalog provides the latest firmware and software from the SPP. The catalog can be used with SCUP and the SCCM Software Updates functionality to keep ProLiant servers up to date. For more details, see HP ProLiant Updates Catalog User Guide.
6 Collecting extended inventory data The HP ProLiant Inventory Tool is a command-line utility. When executed, it gathers data from the HP Insight Management WBEM Providers and generates HP#.mif mif files in the NOIDMIFS 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. To collect extended inventory data: 1. Ensure that the following conditions are met: 2.
Table 3 HP ProLiant version control (continued) Type Component (example data) Version (example data) Firmware BladeSystem c3000 Enclosure 3.50 Firmware A19 (Active) 2011.12.28 Firmware A19 (Redundant) 2011.12.28 Firmware1 PIC 1.6 Firmware 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 (Boot Code) 4.0.493.
7 Troubleshooting Some drivers fail to be injected into the boot image One of the reasons this might occur is that a driver is signed with a newer driver signing method than what DISM and the operating system support. In that case, the driver is treated as an unsigned driver and is not injected into the boot image. For example, when running SCCM 2012 SP1 on Windows Server 2008 R2, some Windows Server 2012 drivers cannot be injected into an x64 boot image.
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: http://www.hp.
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: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website: http://www.hp.
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.
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@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
A Hardware Configuration Hardware configuration, prior to operating system deployment, may not be necessary. Hardware configuration can also be accomplished via other methods, such as ROM-Based Setup Utility (RBSU) and Option ROM Configuration for Arrays (ORCA). IMPORTANT: Since hardware configuration is performed with the HP Scripting Toolkit for Windows and with SPP drivers in WinPE, it is susceptible to STK, driver, and WinPE issues. Check for any advisories before using them.
7. Edit the task sequence. a. b. Create a new, first group named “Configure ProLiant Hardware”. Copy the first three steps from the Install Operating System group into the new group. IMPORTANT: The partitioning tasks are required when deploying to bare metal servers. On a bare metal server, the Smart Array auto-configures itself, but the drive must be partitioned and formatted to allow the Run Command Line to download its reference package and the Restart Computer task to cache its state information. c.
• If you are performing Smart Array configuration, it must be the last utility step in the group followed by the Install Operating System group and its partitioning tasks. Configuring the Smart Array causes C: to disappear and thus subsequent Run Command Line tasks that reference a package will fail. Do not execute hpssascripting.exe in a batch file for the same reason.
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 22 Glossary
