I have set an asset state to be 'for destruction'. These are Windows assets which are broken or do not have the capacity to be turned on. We do this periodically and they are only set for destruction when cataloged and moved where they cannot be reconnected.
We like to keep the information in Lansweeper until destruction has occurred so when we report on the items removed we have information about the asset before it was in that state for our ISO auditing.
Broken does not do the job for us as broken allows us to decide if it can be repaired or not.
What would be good is for custom states we could also select whether this state should be excluded from scanning or not.
You can create your own custom asset states, however, the only thing custom states do is make sure that the asset is not included in most built-in reports. You can create new assets states in Configuration\Asset Pages.
States can't be used for scanning exclusions, your best options is using IP or Windows Computer exclusion.