Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Software license management

Log in to subscribe to topics and get notified when content changes.

Software license management

You can set up software entitlements that are used during reconciliation to compare software rights owned to software installed, including those for named users, devices, and cores.

Software licenses are based on models that you create to organize software licenses in meaningful ways. Different license metric calculations determine how software is counted.

Software licenses can also be associated with a contract which enables a company to cover software licenses for multiple assets or users. You can manage and track software contracts using the Contract Management application.

Features include:
  • Publisher part number lookup from the Software Product Definitions list of predefined software lets you easily connect purchased software entitlements to discovered software installations.
  • Predefined suites mean suite components can be automatically created for known suite parent software models. Discovery maps indicate whether a suite is defined for the product.
  • Blacklisting identifies software that should not be installed in your environment (inappropriate software, or software with vulnerabilities, for example). A scheduled job runs nightly that automatically creates removal candidates for blacklisted software.
  • Software rights can be applied according to the conditions set in the software discovery map to filter out specific software installations that do not require a license. For example, production server installations versus failover server installations.
  • Software lifecycle phases can be input for use with the Technology Portfolio Management feature of Application Portfolio Management to help manage the lifecycle of software that supports business applications.

Software entitlements

Software asset managers can allocate one or more rights to a user or device to use certain software.

For example, say a company purchases a software entitlement for 100 rights. From the software entitlement, 100 employee or machine allocations are created that are rightfully assigned a license. If Discovery finds the software installed on 200 machines, the software asset manager must identify the employees or machines that have the software installed without a license, and remediate the situation.

Built-in rules are used to help prevent allocating more rights than have been purchased. Asset tags can be used to track and identify specific software entitlements.

You can also import software entitlements from a list on a Microsoft Excel spreadsheet, and view the entitlement import error results to fix them.

Benefits of using software entitlements:
  • If the overall license allotment is exceeded, the software asset manager can rapidly address the problem and return to compliant status by either removing unauthorized software or ordering more licenses.
  • If the license allotment is not being used completely, the software asset manager can respond by lowering the number of licenses purchased in the future.

License Change Projection

When Change Management is integrated with Software Asset Management, the impact of software license costs is automatically calculated when a change (to CPU count or CPU core count) is proposed. License projections let you analyze license information before and after the proposed change.
Note: The Change management – License Change Projections (com.sn_samp_change) plugin must be installed to view the License Change Projection section on the Change Request form.

License information is provided on the Change Request form in the License Change Projections related list and summary graph.

SAM change projection
License change projections are calculated for these license metrics when a proposed change is made on CPU count or CPU core count on at least one affected CI.
Note: The add-on Microsoft publisher pack ( plugin must be installed for Microsoft license metrics. The add-on Oracle publisher pack ( plugin must be installed for Oracle license metrics.
  • Common

    Per Processor, Per Core

  • Microsoft

    Per Core (Physical, Virtual OSE, with CAL), Per Processor

  • Oracle

    Named User Plus, Per Processor

Reconciliation must be completed at least once to show projections. If the reconciliation process is running, projections are calculated on the next job run.