Tracking End-Of-Life (EOL) for software without using SAM/SAM Pro, is it possible OOB?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-27-2020 11:18 AM
We need to track mostly our OS software end of life cycle and take action when it hits a threshold, but today there's not any place to add this data, at least not within the normal tables within the CMDB.
Our thought was to extend the "Software" table (cmdb_ci_spkg) and add a date field for EOL, since this could be gathered from our scans and managed with this one record (potentially).
I have read other ideas, about using the [cmdb_ci_business_app] table, but that is within the App portfolio module and we only have ITBM except that piece. I believe we can still use the table, but I don't see the relationship between it and the server/workstation CI.
Any ideas/suggestions, who else has created a solution to track this, again, without SAM/SAM Pro. Considering most of our company runs on only a few versions of Windows 10 or a few versions of Windows server, it wouldn't be that bad to manually maintain.
In advance, thanks for the advice or sharing your story.
Alex
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2020 04:27 AM
Hi,
Yes but with some flows and manual work.
Few things which i need to understand from you is:
1) How do you maintain this software in servicenow. Using discovery? SCCM?
2) Which metric on that software is used to decide the EOL?
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-16-2021 06:57 AM