Lansweeper will attempt to scan these assets, but will quickly move on once the ping timeout has been reached, unless you're talking about a great number of assets here the impact of these timeouts on your scanning queue should be minimal. It's unfortunately currently not possible to exclude assets from scanning based on asset state.
Your current options for excluding these assets from scanning if you wish are:
- An IP Range or IP Address exclusion, this will only be useable if the IP addresses of these assets are not being reused. Alternatively you could manually edit the IP addresses of these assets to an IP address outside of any ranges you are scanning, though this lowers the historical value of the assets.
- If they're Windows computers, a Windows computer exclusion should do the trick if you're not reusing the computer name. This requires individual entry though.
- Asset Type exclusion, if these assets are non-Windows computers, you could add a "Destroyed" Asset type under Configuration\Asset Mapping. Afterwards you can go to the Assets tab, filter for destroyed under state, click the select all checkbox and click Mass Edit Assets (the top one) in the left hand pane. Afterwards you can set up an asset type exclusion for destroyed.
We've added "Scanning exclusions based on asset state" to our customer wishlist, for now though we aren't able to provide you with an estimated release date for this feature. At this moment the main use of asset states is with cleanup options under Configuration\Server Options and to be filtered out of built-in and custom reports with tblAssetCustom.State = 1 (active).