Summary
When using automated cleanup options, the term “not seen” does not refer to a single timestamp, such as Last successful scan. Instead, Lansweeper evaluates multiple activity timestamps to determine whether an asset is eligible for cleanup.
Problem Statement
You have enabled the cleanup option “Permanently delete assets not seen in the last 60 days”, but assets older than 60 days are still present in Lansweeper. Why does this happen, and is there an additional setting required to fully remove these assets?
Explanation
The cleanup option “Permanently delete assets not seen in the last XX days” uses a composite definition of “not seen.” An asset is only considered not seen if all relevant activity timestamps are older than the configured threshold.
How Lansweeper determines “Not seen”
If the cleanup interval is set to 60 days, an asset must meet all of the following conditions to be deleted:
1. No successful asset scan
- Condition: The asset has not been successfully scanned in the last 60 days
- Field: Last successful scan
- Database field:
tblAssets.Lastseen
2. No recent Active Directory activity
- Condition: The asset has not reported to a domain controller in the last 60 days
- Field: Last on-premises AD Domain scan
- Database field:
tblAssets.LastActiveScan
3. No recent IP Range scan detection
- Condition: The asset has not been detected by IP Range Scanning in the last 60 days. Lansweeper has not seen the same hostname/IP combination with open ports during network scans
- Field: Last IP Range Scan
- Database field:
tblAssets.LastIPScan
If any one of these timestamps is newer than 60 days, the asset is still considered seen and will not be deleted.
How to verify asset eligibility
- Use the built-in report: Asset: Last scan times. This report displays all relevant timestamps, allowing you to quickly determine which scan method is keeping an asset marked as “seen.”
- Alternatively, you can check the "Scan Time" tab of your assets to see all the timestamps as well.
