Software Install Creation and deletion mechanism
Auto Creation of software installation records
- ServiceNow discovery discovers the running process for the specific software application such as Microsoft SQL Server and creates a record on the CMDB process table (cmdb_running_process) table.
- Based on the running process a record is created on the CMDB application table(cmdb_ci_appl) with install status set as “in use”
- This automatically triggers creation of software installation record on the CMDB software install table (cmdb_sam_sw_install)
Auto Deletion of software installation records
The process for deleting the software installation is also automated. This is hugely important, as correct software license compliance should be calculated on “true” number of existing software records in the environment
- ServiceNow discovery discovers that the running process for the specific software application such as SQL Server is no longer present and thereby removes the record on the CMDB process table (cmdb_running_process) table.
- Based on the removed running process record, the existing record on the CMDB application table(cmdb_ci_appl) is set with install status as “absent”
- This automatically triggers a business rule to remove the corresponding software installation record on the CMDB software install table (cmdb_sam_sw_install)
Important to know
ServiceNow SAM Pro determines license compliance of software deployed on hardware CIs such as virtual machines, desktop etc. Best practice setup and management of retirement process of these hardware CIs from the CMDB is crucial for deterministic software license compliance calculation on SAM PRO.
ServiceNow discovery would automatically discover the CI record and create the software install records.
While “removing” or “deprovisioning” the hardware CIs the below steps need to be followed:
- The SAM Manager/CMDB Manager is tasked with manually marking the asset state as retired, leading to the automatic classification of the Configuration Item (CI) state as retired. This, in turn, triggers the automatic removal of software installation records linked to the CI.
- Collaborating with the infrastructure administrator, the SAM Manager ensures the proper elimination of CIs from the environment or network, effectively deprovisioning the CI/asset.
- In subsequent ServiceNow discovery runs, the CI record remains undiscovered, and its historical software installation records are removed. This process guarantees a precise assessment of the license compliance position. *
*Failure to remove the asset/CI from the network while the discovery process persists will result in the CI being rediscovered and consequently utilizing licenses. Therefore, it is advised to adhere to best practices by removing the CI from the network to prevent unwarranted license compliance complications.
7 Comments
