Looking for a best practice approach for Software CIs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2023 12:27 PM
OOB ServiceNow doesn’t create a Software CI from the Software Model. While you would track the software with models, licenses and the installations in SAM Pro in order to reconcile the licensing. How do you make sure there is a CI? What is the best practice approach for this because it is needed for Incident, Change and Problem Management?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2023 09:57 PM
I guess the question seems a little weird because CI's are created usually from Discovery or manually created entries of instances of Software (maybe you have the mother of all excel sheets). I included the screenshot from the ServiceNow SAM design guide. As you can see CMDB and Discovery EUC happens first prior to model creation. https://www.servicenow.com/success/playbook/optimize-processes-design-guides.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2023 09:29 AM
The question is not 100% clear to me but it seems you are trying to ensure if the software installations are associated with a valid CI or not.
The Discovery brings the CIs and it's installed software. In the software installations table (cmdb_sam_sw_install) you can check the software installation records for each CIs. The field "Installed on" in the Software Installation table stores the reference of the CI where the software is installed on.
Hope this will clear your doubt. If any additional information is required feel free to reply in this comment.
