1 of 1 people found this helpful
This is a state management problem, and it is being worked on for a future product.
In the meantime, you can delete the record, or you can flag the record. See this page for flagging option: http://www.droppedpackets.org/misc/external-unmodeled-data/
When the machine is being serviced(re-imaged) are steps being taken to keep the Device ID that identifies the system in LANDesk? If they are then i suggest you take a look at iRecall as it allows you to temporarily archive a system to a queryable database with an audit trail and a location code (http://www.networkd.com/iv_iRecall.html). You can set a machine live again when ready or detect systems that were archived but have now become live again.
If you aren't keeping the ID then the system will appear as a different machine to LANDesk and there is very little point in keeping the inventory records.
The process so far is if the inventory record see the same Device ID and MAC address then it is assumed it's the same machine and the information, history etc is restored. That is not too important to me, I just wanted to keep track of the physical machine. If we searched through the database we will be able to determine where the physical machine is. We are currently using another product to keep track of the machines, I'm just forward thinking incase we decide to drop that package and use LANDesk instead.