Have been working on a case for over a year and part of this case we discovered that residual data is being left behind by the product at this location \Program Files (x86)\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\sha1 which is causing us to unnecessarily chase issues for Oracle inventory purposes.
This idea is to cleanup after an import OR reset the \Program Files (x86)\BigFix Enterprise\BES Server\UploadManagerData\BufferDir\sha1\(nn)\(id) folder BEFORE any scanning takes place.
This way, there is no stale data left behind by inventory scans that may have run months or years ago.
Lots of residual stale data from previous scans. Imports do not do any cleanup after the data is processed by nightly imports and that has created data issues for Oracle Measurements data files.
Right, just to be clear Inventory may not be the only thing storing scan archives. It’s common for customers to roll up logfiles or other data through custom uploads; and the Unmanaged Asset Importer uploads here as well.
Deletion of uploads for a given computer should happen when that computer is deleted, and the BESAdmin Cleanup tool runs to remove that computer’s upload files.
Old scan files left behind should not, I think, trigger a new detection in BFI; the “last seen” date for a software package should match the date of the old scan uploads I believe. If that’s not correct then I think you might levy a bug report on that.
If the computer has an Inventory scan, then removed the software but never ran a new Inventory scan, then I think the BFI Inventory should continue to report that software as long as the target computer exists in BigFix, Inventory won’t detect the uninstall until a new scan is uploaded & imported, but I think that is expected behavior.
In my case, they will have 7d to get their data off of \sha1 before it gets nuked.
With the case I have open for going on 14mos, old scan files ARE having an impact on Oracle collected data. I have no choice but to do the cleanup on my own that the product fails to do.