05-31-2019 08:16 PM
08-22-2022 05:56 PM
Side note: I was testing mhammond's scanning exclusion with a Retired asset type created under Asset States, but that new state wasn't showing up in the list of assets to choose from. The scanning exclusion list is populated from the Asset Mapping / Asset Type page. The more you know...
08-22-2022 05:39 PM - edited 08-22-2022 05:40 PM
Combine mhammond's scanning exclusion with changing the asset type to "monitor" to release the license count may help with the license issue. Also removing the asset's IP address to ensure it won't be scanned during an IP scan should keep it from being modified by Lansweeper.
08-22-2022 04:27 PM
We are in the same boat. We want to keep the asset in the databse but not take up a license.
05-28-2021 04:11 PM
05-26-2021 06:17 PM
05-28-2021 07:53 PM
Cripple.Zero wrote:
For each asset you're retiring, couldn't you just go to:
SCANNING >
SCANNING TARGETS >
...then scroll down to "scanning exclusions" and add that asset with the reason of "this will put the license over its limit" ?
That's what we do. Not sure how to 'protect it' as read-only or archive the info, but it's easy enough to report on.
Oh and don't forget to edit the asset's properties so the box is checkmarked "Not affected by cleanup options" to retain the info.
Otherwise, you may have to get fancy with SQL coding outside of the system.
07-17-2019 04:01 PM
07-17-2019 10:22 AM
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now