Removed software still appears to require reconciliation.

[Jen Wenrick1]

We are using ServiceNow Discovery and SAM Pro.  I have some software that was de-installed from LINUX OS systems about 1 month ago.  Since then discovery has run multiple times, reconciliation has run multiple times and this software package continues to show up on these systems in the license workbench.  How does this work with Discovery and ServiceNow with regard to software that is de-installed, what should I expect to see?  Looking for more details on how this is supposed to work so that I can further troubleshoot please.  I also have the same questions about SCCM & JAMF integrations, but the immediate need/concern the LINUX server situation mentioned above. THANKS!!

[Joe Ryder]

That's exactly right. I'd post the code here (I understand it's not super complicated) but I don't have direct access myself and I'd need to see if I can post it publicly. But basically, it just looks at the date, makes an age calculation, and deletes the record if the age is more than 90 days.

Those scenario-handling logic bits are something we're exploring as we continue to refine discovery overall. Generally, if the server is having any other issues with discovery, we'll see that as credential errors or other errors in system logs, so we can actually monitor that separately. We didn't need it in the logic in this script because we just wanted to focus on an extended "oldest date" this operational data would live. We do flat-filed reporting on individual targets that need installs over time, but the base functionality is set up to just monitor near-current license consumption.

I'll admit we might reassess our data age strategy as we get more mature. We might want those old installs to stick around for a year to get falloff trends, especially for enterprise and "ULA" agreements where we need to see the real performance of contracts against shelfware trends.

[Jen Wenrick1]

Outstanding - thanks !