Loading
Why is Software Install Date More Recent in SCCM than in SNOW?

We are using SNOW to locate unused software where the software has been installed at least 90 days.  Then we use SCCM to remove the unused software.  We are seeing in SCCM that the software install date is different than what SNOW is reporting.  i.e. - we recommend removal of software A as SNOW shows it was installed in Nov 2017 and never used, but SCCM shows it was installed in Jun 2017 (and in some cases is being used).

What would cause the difference in install date detection?

Thanks, Matthew


  • Shawn Cardamon (Flexera Software)

    Hello Matthew, Good catch first off!  So Craig is absolutely right, as of late 2016 Microsoft (and a handful of other vendors) began updating installed date within the registry stack which primarily identifies a piece of software as installed within the OS.  When this happened, tools like Snow were thrown for a loop as this was the baseline which advised when software was initially installed.  We identified this and took care of the issue rather rapidly of course. While in SCCM you would see the date changed after a software update (which makes that date incorrect/invalid from a licensing perspective), Snow leverages our technology to capture the first time we identify an installation as being installed, capture that date within SLM, and ensure its persistence to support that installation's licensing position. Hope this helps and please let me know if you have any other questions, thank you for reaching out!
    Expand Post
  • Community Manager (Flexera Software)

    Depending on the deployment method, we have seen that SCCM will over-write an install date on product updates, even if the product has never been launched or run.  Hope this helps. Adding ? to provide additional context.
    • Thanks Craig!  Interested to see if ‌ has any other insights into this issue. Best, Matthew

Loading
Why is Software Install Date More Recent in SCCM than in SNOW?