- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2018 01:46 PM
Hello,
I have a big list of discovered software products that is no longer being discovered and in some case the servers has been retired and removed from the network. How do we remove or retire these products from our CMDB?
Eddie
Solved! Go to Solution.
- Labels:
-
Blacklisted Software Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-05-2018 04:09 PM
Hi Eddie,
Starting in the ServiceNow London Release, the Reconciliation Engine does not count Software Installation records related to CI's in a state of Retired. For releases prior to London it is recommended you create a Business Rule to remove Software Installation records upon install_status change to Retired. You may also want to create a Business Rule to remove Device Allocations under the same circumstances.
Regards,
Daniel W. Slocum
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2018 03:07 PM
Daniel,
Thank you, I'm testing in both versions (Jakarta and London) with the goal of going live with London.
How about software products that are stale or no longer being discovered? Do we have to set up Staleness in CMDB health?
Eddie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2018 03:23 PM
Great question Eddie,
First, you'll find London so much more robust. We've made significant improvements across the entirety of SAM Professional since the initial Jakarta release. The Software Entitlement import feature is reason enough to uptake London. It will save you a tremendous amount of effort.
For understanding if a CI is stale, yes you'd want to use Staleness in the CMDB Health.
Here is something you might also want to consider. If you are confident in the data within your SCCM instance and have only a small percentage of computers which don't regularly get scanned, you may want to wipe the Software Installation and Discovery Model tables in your instance prior to going live with SAMP. Then do a full import. I've seen several customers do this with great success.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2018 12:24 PM
Daniel,
We have considered that option but one of the concerns we have is, how do we tell if the process is working correctly and if we have the rules set up to address most scenarios? Also, we only use SCCM for desktop and ServiceNow Discovery for everything else.
I have two other questions and can submit another request if you like.
Do the content pack also contain end of life information about the software products and if so where can I find it?
Also, for software teaching do we just create new Discovery Models and how would we know if we made a mistake? Will a new content pack point out this errors once available or is there another method?
Thank you for all your help.
Regards,
Eddie
