HP Systems Insight Manager - Manual (Page 129)

NOTE: The new management processor license collection is supported on management processor
and management processor devices. Deployment is supported on management processor and
management processors with newer firmware versions.
In some instances, licenses are managed and controlled by the licensed system (remote licensing).
In this case, License Manager provides the facility to collect and deploy licenses to those systems.
For non-management processor systems, communication used is a Microsoft COM mechanism.
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 API over the COM protocol
to assign licenses to and collect license information from those remote systems. License information
is duplicated in the HP SIM database, but licenses are managed remotely and must be periodically
collected to keep this information correct. Authentication credentials for the specified systems are
needed when licenses are sent to the specified system. If WBEM authentication credentials have
been provided for a specific target, these credentials are used. If specific credentials have not
been provided, each set of WBEM credentials provided as global credentials are used in turn. 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. This mechanism of license management is rare. Those instances where
used, will be clearly stated in product documentation.
NOTE: Automatic collection of management processor licenses is not supported.
NOTE: You do not have support or upgrade options by default. After July 9, 2007, all license
keys are included in one year of 24 x 7 Software Technical Support and Update Service. The
License Manager informs you which license keys are "support and update enabled" and which
license keys require the purchase of future updates and upgrades.
CLI mxlmkeyconfig
The CLI mxlmkeyconfig enables you to combine all the License Manager key files into one file
instead of having to execute multiple files. Combining these files into a single file makes it easier
when adding keys from a file through the License Manager graphical user interface.
The mxlmkeyconfig command takes all the keys and related information and places it in the
resulting key file. The CLI program will not allow duplicates. If there are duplicate <key string>
values, a warning message appears and only the first value is placed in the resulting key file. If
badly formatted files are encountered, warning messages appear.
The key file is created when the CLI mxlmkeyconfig is command is executed. If the resulting key
file already exists, then the previous keys remain and the information from the source key files are
added to the resulting key file.
License types
License Manager displays licenses by product. If a license authorizes multiple products, the number
of seats permitted by the license is applied in full to each authorized product. For example, a
license authorizing five seats and two products authorize five seats for each product.
Table 12 License types
Description License Type
Offers full, unlimited functionality for an unlimited time and
for a specific number of seats purchased, up to 50,000. Flexible Quantity
Offers full, unlimited functionality for an unlimited time.
This license represents an expected upper limit on the
number of seats, up to 50,000. Activation Key Agreement
CLI mxlmkeyconfig 129