Asset not set to non active if not seen longer than 45 days

[AG]

We enabled the functionality that all assets which are not seen for 45 days are set to non active. Now we have some devices where this automatism does not work. The last seen date is june 2015, but the asset is still active. I'm supried that the time stamp "last active scan" shows a date this year. But as the last seen is so old it was not successful. Why is it still active?

Regards,

alex

[Jeremy_D · Accepted solution]

Could you update to the latest Lansweeper release first, by following the instructions in this knowledge base article, and restart the Lansweeper Server service to see if the issue persists. We fixed some bugs in the database cleanup options recently.

Keep in mind though that the "not seen in XX days" option does not just look at an asset's last seen date to determine whether or not the asset needs to be set to non-active. If the asset is detected in your network, even if it cannot be successfully scanned, it will not be set to non-active by the aforementioned cleanup option. If Active Scanning is enabled for instance, Lansweeper will attempt to scan Windows computers as they report to a domain controller. If a computer reports to a domain controller, you know it's in the network, even if it cannot be successfully scanned, and the machine will not be set to non-active. We wouldn't expect non-Windows assets to be scanned by Active Scanning though. This is a Windows computer scanning method.