About licenses – HP Systems Insight Manager User Manual

Page 319

Management Pack (PMP), all license information for HP SIM plug-ins is maintained by License Manager in
the HP SIM database. For some products, the license is stored in a licensing structure in the Windows registry
on the licensed system. License Manager employs Microsoft's remote registry Application Programming
Interfaces (API) over the Microsoft Distributed COM (DCOM) protocol to assign licenses to and collect license
information from those remote systems. License information is duplicated in the HP SIM database, but the
licenses are managed remotely, and must be periodically collected to keep this information current.

Authentication credentials for the specified systems are needed only in those situations in which licenses are
sent to the specified system. If WBEM authentication credentials have been provided for a specific target,
these credentials are used. See

“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. See

“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 run on candidate target systems for key collection or assignment.

License Manager does not permanently bind (or apply) a product license to a system. Users can assign and
un-assign licenses as needed. Once a product executes a licensed operation on a system, the license is
bound (locked) to that system. License Manager can no longer move a license that has been applied or
locked. Assigning a license to a system is a way for the user to ensure that a particular type of license
(permanent vs. trial) will be automatically consumed by the product when it is run on that system. For remote
systems, licenses are deployed to those systems but not applied or locked. Running the product on a target
system locks or applies the license. Assigning and deploying are not the same as binding. For a remote
system, a deployed license remains on the system, but is not consumed until the associated product is used.
If multiple keys and corresponding licenses are deployed to a target, only the required number of licenses
are consumed. The remainder are left unused.

Generally, when a license is applied as part of the product operation, the license is bound (locked) and can
no longer be un-assigned and used elsewhere. A license deploy to a remote target cannot be recalled.

License Manager can be used to review license usage for all classes of systems, including plug-ins, remote
managed, and management processors.

To access License Manager, select Deploy

→License Manager. The following information is displayed for

each licensed product:

•

Product

. The name of the product.

•

Licensed Systems

. The number of systems licensed to use the product.

•

Licenses (Select 'Manage Licenses' for detail)