View calculations for your licenses in workspace

Evaluate the license compliance of software applications by viewing the details for all required licenses through the Software Asset Workspace License usage view.

Before you begin

Role required: sam_admin and sam_user

Procedure

1. Navigate to All > Software asset > Software Asset Workspace > License usage.

2. View the summary of a software model by selecting a publisher from the left pane.

3. View the number of licenses purchased and required by selecting the License Metric Results tab.

   For more information about the fields in the License Metric Results tab, see the License metric results table in License usage publisher fields in workspace.

4. View the details about the required licenses by selecting a value for a configuration item under the License required column.

1. View all the downgrades being used by the license.

   This related list only appears if the specified license is used by a downgrade version of the software. If a downgrade is not using any rights, that downgrade doesn't appear in this related list.

   Field	Description
   Software model	Name of the software model.
   Rights used	Number of rights used by the license.
   Install count	The number of installations being used for the software model for the specified license.

2. In the Licenses Required By related list, view the details of required licenses by selecting the value for a device under the License required column.

1. View the infrastructure of a configuration item and the metric attributes applied by selecting the License consumption breakdown tab.

   For more information on the license calculation for CrowdStrike products, see License usage breakdown for CrowdStrike products.

|Fields|Description|
|------|-----------|
|Required by|Name of the configuration item that consumes the rights.|
|Processors|Number of processors on this configuration item.|
|Cores|Numbers of cores in this processor.|
|Licensable cores|Number of core licenses required to license this configuration item.|
|Licenses required|Number of licenses required to license this configuration item.|
|Metric attributes applied|Software products from publishers such as Microsoft require a minimum number of licenses to be assigned. For example, Microsoft SQL Server requires a minimum of 4 core licenses for each processor on a server. Metric attributes auto-assign these licenses.|

1. View the details of the installations covered by licensing related to the configuration item by selecting Software installs licensing details.

|Field|Description|
|-----|-----------|
|Normalized display name|The normalized display name of a software product.|
|Discovery model|Normalizes the software you own by analyzing and classifying models to reduce duplication.|
|Installed on|Configuration item on which the software is installed.|
|Assigned to|Name of the user assigned to this configuration item.|
|Unlicensed install|Indicates whether the install is licensed or unlicensed.|

1.  View the licensing status of an install on various hosts within a cluster by selecting a normalized display name for Per Core and Per Core \(with CAL\) license metrics.

1. Check the accuracy of the license consumption and view the host affinity rules configured for a cluster by selecting the Host affinity rules tab.

   Host affinity rules can be configured for SQL Server and Windows Server Standard while determining license consumption. This helps to optimize the number of licenses required and significantly minimizes the number of licenses required resulting in cost savings.

|Field|Description|
|-----|-----------|
|Name|Name of the rule configured for the cluster.|
|Active|Indicates whether the configured rule is active or inactive.|
|Cluster|Name of the cluster where the host affinity rule is configured.|
|VM Group|Name of the group of virtual machines.|
|Host Group|Name of the group of hosts.|
|Mandatory|Indicates whether the configured rule is required.|
|Affinity|Indicates whether the virtual machines live on a host group.|

1. View the suite components for the software model.

   This tab appears only if the software model is a suite.

   Field	Description
   Suite parent	The parent suites to which the software is assigned. For example, the parent suite for several common Microsoft products is a version of Microsoft Office.
   Suite child	The child product or products of the suite.For example, For example, Microsoft Word and Microsoft Excel are child products of Microsoft Office.
   Mandatory	Requirement of a suite component. A suite component can be Optional, Always Mandatory, or Mandatory Group.

Parent Topic:Using Software Asset Workspace