ITOM License is calculating the server and related VM count even though the relationship exist. - Known Error

ITOM License is calculating the server and related VM count even though the relationship exist. Description When Server CI is discovered for first time by a discovery source which is not licensable, we create an entry in cmdb table with the discovery_source. Afterwards, if the same CI again gets discovered by a licensable discovery source, we do not update the cmdb table but make an entry in sys_object_source table with latest discovery source.

When this process repeats, sys_object_source has multiple entries for the CI with all discovery source it got discovered from, but cmdb table is not updated and has discovery_source of the first time it got discovered.

In License Exclusion code we were checking for discovery_source from cmdb table, therefore weren't excluding any related VM.

Example:

sys_object_source

Name TargetSysID ServiceNow VM-1 SG-SCCM VM-1 cmdb_ci_server

Name discovery_source VM-1 SG-SCCM

1. Scheduled Job : ITOM Exclusion Tables Update Store Script Include : PopulateExclusionTablesStore Uses : parent.discovery_source ( discovery_source of the server CI in cmdb_ci_server table)

As SG-SCCM is not a licensable discovery source , it is excluded from exclusion , So the VM-1 is not added to exclusion table.

2. Scheduled Job: ITOM Licensing Visibility CI Listing Store Script Include : ITOMVisibilityLicenseCounterStore Uses : sys_object_source.name (discovery_source of the server CI in sys_object_source table)

As ServiceNow is valid discovery source , it adds the VM-1 (Server) and VM-1 (VM Instance) [this is not added to exclusion table because of above 1 ] to the Licensable Server CI

Steps to Reproduce

Run Report ITOM LIcensable CI ---> Populate CI Check both Server and Related VM are added to the count , instead of excluding the VM.

Workaround While excluding CIs, we are now doing a join with sys_object_source to exclude CIs based on conditions we have so that we get latest discovery_source.

1. Download and Import the update set attached to this KB article sys_remote_update_set_f059d0e7879ee510641a52c73cbb35d3.xml 2. Navigate to All > Retrieved Update Set and check for PRB1658849 - Exclude CIs from Licensing Count. 3. Commit Update Set and the count should be generated correctly from next run.