HP Systems Insight Manager Technical Reference Guide

English


Tools that Extend Management \| License Manager

License Manager


»	Table of Contents
»	Index


»	Notices
»	Introduction
»	Product Overview
»	Getting Started
»	Discovery and Identification
»	Users and Authorizations
»	Networking and Security
»	Monitoring Systems, Clusters, and Events
»	Storage Integration
»	Managing with Tasks
»	Tools that Extend Management
	»	Cluster Monitor
	»	Command Line Tools
	»	Creating New Command Line Tools
	»	Custom Commands
	»	Configuring DMI Access
	»	Configuring SNMP Access
	»	Device Ping
	»	Disk Thresholds
		License Manager
		»	About Keys
		»	Collecting Keys
		»	Collect Keys Results
		»	Deploying Keys
		»	Selecting Keys
		»	Deploy Key Results
		»	Managing Keys
		»	Viewing Key Database Contents
		»	Adding Keys From a File
		»	Adding Key Individually
		»	Viewing Key Details
		»	System License Information Reporting
		»	Licensing with ProLiant Essentials Applications
	»	Management Processor Tools
	»	Managing MIBs
	»	Installing OpenSSH
	»	PMP Tools
	»	Removing and Restoring Tools
	»	Replicate Agent Settings
	»	RPM Package Manager
	»	Server Migration Pack
	»	System Management Homepage
	»	System Page
	»	Version Control
	»	Virtual Machine Management Pack
	»	WBEM Based Tools
	»	Available MSA Tools
»	Partner Applications
»	Reporting
»	Administering Systems and Events
»	Troubleshooting
»	Reference Information


»	Printable version


»	Glossary
»	Using Help

» Related Procedures

» Related Topics

License Manager provides support for ProLiant Essentials based licensing. This support includes license key distribution, reconciliation, and reporting.


Note:


	To run License Manager, a user must be given full-configuration-rights on the central management server (CMS) (to set, select OptionsSecurityUsers and AuthorizationsUser) and the All Tools toolbox (to set, select OptionsSecurityUsers and AuthorizationsAuthorizations). Refer to Users and Authorizations - Users and User Groups and Users and Authorizations - Toolboxes for more information.

License keys can be collected and deployed to and from specified target systems known to HP Systems Insight Manager (HP SIM). For some products, the keys are sent to the specified system, while for other products, the licensing information is simply updated in the License Manager database. The license key database can be reviewed. New keys can be added individually or added in bulk from a file. License Manager also displays license information on Integrated Lights-Out (iLO) systems, which is collected automatically. License Manager cannot deploy keys to an iLO. Keys deployed to the iLO host machine are not recognized by the iLO.

The Licensing menu provides you with the following options:

Managing Keys. Select DeployLicense ManagerManage Keys. This action displays the license keys and their assignments as known to License Manager and offers the facility to add keys, individually or in bulk, and view details on the use of a specific key.
Collecting Keys. Select DeployLicense ManagerCollect Keys. Selects one or more target systems from which to collect keys. Refer to Managing with Tasks - Creating a Task for more information on selecting targets.
Deploying Keys. Select DeployLicense ManagerDeploy Keys. Selects one or more target systems to receive keys, and one or more license keys from the License Manager database to deploy. Refer to Managing with Tasks - Creating a Task for more information on selecting targets. Select one or more keys to deploy. iLO keys are not included because there is no mechanism to deliver the key to the iLO.

License Manager Deploy Key and Collect key functions operate directly on the License Manager database or in the Windows registry on the target system depending on the product. Apart from early versions of HP ProLiant Essentials Performance Management Pack (PMP), all key information for HP SIM plug-ins is maintained by License Manager in the HP SIM database. For some products, the key must be kept in a licensing structure in the Windows registry on the licensed system. License Manager employs DCOM to deploy keys to and collect keys from those remote systems. Current versions of PMP require the keys to in the Windows registry of the CMS. Keys for PMP must always be deployed or collected from the CMS system ONLY.

Authentication credentials for the specified systems are needed only in those situations where keys are being sent to the specified system. If WBEM authentication credentials have been provided for a specific target, these credentials are used. Refer to Protocols - Setting Protocols for a System or Groups of Systems for more information. If specific credentials have not been provided, each set of Web-Based Enterprise Services (WBEM) credentials provided as global credentials are used in turn. Refer to Protocols - Setting Global Protocols for more information. If no credentials are provided, the connection is attempted using the default credentials of the HP SIM server. The remote registry service must be started and running on candidate target systems for key collection or deployment.

Related Procedures

» License Manager - Collecting Keys

» License Manager - Deploying Keys

» License Manager - Managing Keys

» Discovery and Identification - Configuring Automatic Discovery