Hello,
Sorry this caught you off guard. The product doesn't take into account the install_status of the Configuration Item when computing a license position. Many customers add or edit the status values, or they interpret them differently. Hardcoding a status to exclude from reconciliation could cause issues with some customers. Also, we have also seen where a device may be retired, however software is still being discovered. Customers would want to be aware of devices where statuses are incorrect and still consuming software licenses. Technically, if software is discoverable on a device, regardless of the status, we would want to make the customer aware that the software is present and potentially consuming licenses.
To help preclude issues, I believe starting in London, the product shipped with Business Rules on the Asset and CI Computer tables that trigger deletion of software installation records when the status or state/substate changes to Retired or Lost/Stolen. This will preclude software from being counted during reconciliation.
There is also an On-Demand job that can be run “SAM – Remove Installations for retired or stolen configuration items” that will delete software installations from retired/stolen CI’s. This can be used as a cleanup exercise or when activating SAM for the first time.
A final tactic you can employ is to utilize Software Install Conditions on the SW Model to preclude reconciliation from counting software installations linked to a CI which matches the condition set on the SW Model. You can choose any value on cmdb_ci_computer or a table dot walkable from that table.
