Does servicenow maintains End of Life, End of Support and End of Extended support dates for (Host, OS, SI, Storage Device, Virtual Machine) in CMDB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 11:32 AM
Hello,
I am trying to search in ServiceNow documentation for to figure out how ServiceNow is storing the End of Life, End of Support and End of Extended support dates for Host, OS, SI, Storage Device, Virtual Machine (Support Details) in CMDB. So far no luck with documentation. Can anyone point me in the right direction like which tables & columns they use to store the support details information.
Thank you,
Rajesh
- Labels:
-
Service Mapping
- 4,679 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 11:44 AM
There's no out of box way to store this on the CI itself. If you subscribe to Application Portfolio Management and use Technology Portfolio Management, you can define those against your applications and supporting tech stack. TPM is where you can see the tech lifecycle as a gant.
There are 3rd party solutions that add this functionality to SN. See the store for more details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 12:51 PM
Hi John,
Thanks for your response. But my question is specifically regarding the Hardware support and its immediate software support details information. For example, if you take Windows 2007 support is ending on January 14, 2020. And coming to SQL Server 2017 on Windows(all editions) are set to end their support by 10/12/2027 from Microsoft.
Is serviceNow giving any out-of-box tables to store these kind of information. Because most of the discovery tools are capturing these type of information and we are lookign for a placeholders in servicenow for to maintain them in CMDB.
Thank you,
Rajesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-26-2019 06:16 AM
There's nothing OOB on the CI to store this data. You could extend one or more CI classes to hold the data, but the only way to do this OOB is by adding the APM subscription, which adds that capability.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-25-2019 12:00 PM
I did a BDNA (add-on) implementation a few years back to track this sort of information at the Product Model level. I had to tinker with the integration but they have the information which seems to be the hard part.