How to remove KACE Smart Labels from devices no longer connected
I'm managing a cloud instance of the K1000 that we use for asset mgmt, patch/SW deployment, etc. We originally had the MIA actions set up to delete devices/assets that have not checked in for X amount of days. However, our help desk team requested that we move it to Archive instead (so we can retain a record of the asset). From what I've seen, the archiving has not been successful (assets stuck in pending) and I believe that had to do with how our Smart Labels were initially configured. Therefore, I adjusted to exclude devices/assets that were not checked in that specific time period. Unfortunately, I know that the older devices will not be removed from those labels since it is processed during check-in/inventory, which will not happen for those devices (since they are offline, disposed of, etc).
I've been trying to figure out how to manually remove those devices from the labels, and clicking on the "Remove Labels" action only produces a blank window for those devices. I also came across an older thread from a few years ago which mentioned that this can be handled through a "custom ticket rule", but I have no idea how to implement that. At the moment, the ticketing system inside KACE is not even being utilized by our Help Desk team (we use a separate product for tickets). So, there is no one in our organization that has knowledge of it.
Any help on this would be greatly appreciated as I am trying to keep our KACE licensing under its limit. Thanks.
By default, the KACE SMA will set the "Archive Pending Threshold at 3 Days", which allows the admin to revert the Device from being marked from Archiving if needed.
Have you wanted the expected amount of time?
I struggle to see why you have your MIA setting set to Archive the Assets, simply deleting the Inventory record leaves the Asset record fully in place so you have visibility.
If you archive the asset there is a danger that if a device that has been removed reappears, not only will it recreate the inventory record, but it will also recreate a duplicate asset record, only for you to archive again should it go MIA. All you end up with is a bloated, useless Archive Asset table.