Hi All.
I have been publishing articles on Discovery and software normalization. Please refer to the following link:
Discovery and Software Normalization
In this article, I am going to talk about reconciliation process.
What is License Reconciliation
License reconciliation keeps license positions accurate and up-to-date. Reconciliation runs weekly or on demand.
Reconciliation is a scheduled job that is run at a specified frequency (default is weekly). It can also be run on demand for specific or all publishers, groups, and subgroups.
Group and subgroup values include country, department, company, region, or cost center. Default group and subgroup properties that apply to the weekly reconciliation run can be set in .
When reconciliation runs, a list of reconciliation results is created that shows the compliance status of software products concerning discovery and entitlements. Users with the sam_user role can view reconciliation results.
In addition to creating a purchase order for new software licenses, additional remediation options are available in software model results. Use the results to automatically create and remove allocations, remove unallocated installs, and remove unlicensed installs.
Review reconciliation results in a simplified License Workbench view, and use the License Position report to see compliance details for each software model in a single list.
What is Software Entitlement
A software entitlement is the right to use a software. You can create an entitlement by going to software asset>software entitlement
Reconciliation Example
As I previously stated, reconciliation is a true-up between discovered software and entitlements. In this example, I will show that reconciliation calls a product unlicensed if no entitlements is found and tags it as compliant if an entitlement is found.
Step 1 - Run reconciliation as stated above, for all groups and subgroups. In this example given that there is no entitlement created for CentOS publisher reconciliation marks it as unlicensed.
Step 2: Create an entitlement model
Step 3 - Run Reconciliation again
Step 4- Software should now be compliant
Overall flow of reconciliation is:
1.Software Discovery
2.Comparison with Software Model
3. Update of Software Installations
4. Reconciliation Run
5. Comparison of installed software with entitlements
6. Compliance / Non Compliance Report
Please mark help or comment if this article helps.
