HP Systems Insight Manager - Manual (Page 94)

I. Target system is not running Microsoft Windows as required.
J. Keys cannot be collected from a system of this type.
NOTE: This displays if the system is of a different type such as; a switch, a printer, a cluster, a
complex, or a system not running a Windows OS.
K. Cannot collect keys stored on this node. Systems Insight Manager host
and specified system must be running Microsoft Windows.
NOTE: This happens when, for example CMS or a remote system is not running a Windows
variant operating system.
L. License Manager does not know how to assign licenses for this product.
License Manager has no information about this product. Install the HP
Systems Insight Manager plug-in that uses this license or collect
license information from a system running this product first.
Assigning and Unassigning licenses
Systems Insight Manager enables you to assign and Un assign product licenses for plug-ins, if applicable
for that plug-in, and to assign licenses to remote target systems when licenses are managed remotely.
Remember that management processor licenses must be applied directly to the management processor and
NOT its host server. For plug-ins, when assigning licenses, note the following for non-management processor
targets:
•
When a license is assigned to a system, it is not locked or consumed until the product operates on that
system.
•
A system can be licensed with a demo key just once. If the license expires, the only option to continue
to use the system with that product is to purchase a license. A system licensed by a demo key can be
relicensed at any time with a paid license.
•
An assigned license can be unassigned from one system and assigned to another system, as long as
the product enabled by the license has not consumed the license. When a product has been used on
a system, the license is locked to that system permanently. Licenses delivered directly to a target system
that manages its own licenses cannot be unassigned (product will provide details on when a license
must be sent to a remote server). There is no penalty for having these licenses remain on those systems
because they are consumed on an as-needed basis. The remaining licenses can be used elsewhere.
•
A DLL can be assigned to a system a multiple number of times. When the licensed product consumes
a license and that license subsequently expires, a new license will be consumed and removed from the
stack of assigned licenses (if there are any and using the same license key). For example, if seven
product licenses based on the same DLL key are assigned, the license remains valid for seven times the
time interval specified in the corresponding DLL license. Any number of the assigned licenses still
assigned may be unassigned at any time.
Some products limit the use of the License Manager interface. Consequently, Manage Licenses may be
selected, however Apply or Assign/Un-assign might be disabled.
Apply Licenses
A license applied to a system is irreversible. Licenses applied to management processors are managed by
each management processor and so the policy is set by the management processor. The license is locked
to the specified system.
For management processor targets:
•
When a license is assigned to a management processor, a license record is created and stored in the
License Manager database.
•
If the selected management processor is already licensed, you cannot replace that license with a new
license from License Manager. You must first delete the existing license at the management processor
console and then insert the new license (directly or using License Manger). However, Integrity MP does
94 License Manager