Software Installation data from cmdb_sam_sw_install table missing after x days
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2013 07:09 AM
We are testing Software Asset Management in Berlin. After running a discovery, the Software Installations table (cmdb_sam_sw_installs) will fill with data and we are able to add licenses, etc. However, it seems that if a discovery is not run on a machine in 'X' number of days (it looks like X=7 from what I can tell), the data disappears. If I go to the computer in the CMDB, it shows as active and the software is listed there, so it appears to be that association. If I run another discovery, the data is repopulated. I am assuming that this is a setting somewhere, but being very new to ServiceNow, I am unable to locate it. Any help would be appreciated.
- Labels:
-
Enterprise Asset Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2013 07:18 AM
This is the scheduled job "SAM License Counters"
We had ServiceNow disable part of the job in order to keep the software installation records.
I'm currently working on a amendment to the job to only delete items that have been retired for x number of days.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-07-2014 06:25 PM
I am not able to find any job by name "SAM License Counters". Please share how can we edit the number of days in Dublin release. In Eureka we have a system property to edit the number of days but in Dublin there is no property to edit the number of days.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-08-2014 05:20 AM
The job is under System Scheduler under Scheduled Jobs called SAM License Counters. Make sure you are looking under there and not under System Definition. The second line of the script is where we set it at 30 days.
var gdt = new GlideDateTime().getDate();
gdt.addDays(-30);
That seems to work, though I won't say 100% that's the best way to do it. However, we are now in Eureka and I'm wondering if the system property to edit the # of days is something that you set up or if it is out of the box. I've not gone back to investigate and this might be a better way for me to accomplish this...other than having people report machines that are no longer in use.