→ 🚀What's New? Explore Lansweeper's Fall 2024 Updates! Fall Launch Blog !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
zblack
Engaged Sweeper III
Would like the ability to mark Assets (State) as 'Retired or Disposed Of', removing the asset license from it and removing it from any and all reports except one that lists all Retired or Disposed Of assets for auditing, but keeps the data (record) for historical reference (can't be updated, can't be scanned, etc. unless marked active again, thus taking up a license and can't be changed again for X days or something to prevent abuse). We require this for audits from time to time.

Maybe have a time limit option on how long an asset is set to Retired or Disposed Of so that it automatically purges after X months or X years.
8 REPLIES 8
rader
Champion Sweeper III

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...

rader
Champion Sweeper III

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.

NickTot
Engaged Sweeper

We are in the same boat. We want to keep the asset in the databse but not take up a license. 

JamesM
Engaged Sweeper
+1 for this also.
Within our previously used system, certain asset states did not count towards your license count. This was very handy for those assets which had been stolen / lost / disposed of etc. At the point we switched over to Lansweeper we had 8000+ assets which were these states, and we would've liked to import this data into Lansweeper to retain the history.

Instead, moving forward with Lansweeper our plan is to have scheduled "offloading" of assets, where we will export assets marked as disposed to excel, and delete them from Lansweeper. Otherwise you will have an ever increasing Lansweeper license asset count, whilst your company has the same amount of "in use" devices. Very bad for larger environments where assets are archived, replaced, and disposed of on a daily basis.

It is a real drawback of the system, and seems to be a real step back from Lansweepers typical attitude of a "single source of truth".
mhammond
Champion Sweeper
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.
zblack
Engaged Sweeper III
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.


Yeah, that would work great if you have no interested in recouping the license for the asset. We don't want to pay for a license for an asset that is no longer in use though.
dshu
Engaged Sweeper III
+1 for this, would be fantastic. We have devices that have been stolen/retired/disposed of that would fit into a new archive area perfectly.
n_klug
Engaged Sweeper II
I agree. It would be great to be able to archive Assets so they don't cout towards the Asset limit, while still having the asset information available as read-only.
I might also be helpful to have the date of and the user doing the archiving saved. Maybe along with a comment.
That way you could have a report for the archived Assets, something like:

Assetname | Archived on | By user | Comment

I have achieved something similar, by setting the Assets to 'Non-active' and adding a regular comment. I then created a custom Report which displays all non-active Assets along with the last comment, date and the comment-author.
This kind of works, however the Assets still count towards the Asset limit and the comment is easily overwritten. A safer way would be to use custom fields, but this would mean more manual work (adding the username and date).

Hope this gets implemented.