KACE SMA (K1000) Inventory Best Practices
Hi all,
I am looking for some info on the best way to setup Device Inventory management. Currently my organization does not have the "Automatically Delete MIA Device's" option turned on which I think is a mistake. Device inventory should be kept clean and devices that do not report in for a month should get deleted. If the device is still in our possession then the asset record will still be active. If the device was returned because the lease ended then the asset record will be archived.
Does this make sense? How do you do it? How would you do it?
The main reason we are looking at implementing this now is because our license cap is about to be reached and our company does not want to purchase more licenses if computers are MIA anyway.
Thanks!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
tramiksim
7 years ago
We have a similar set up but devices are set to delete after six months. Personally I think that is way too long but I got overruled.
Posted by:
scarpent
7 years ago
I have a label Machines Recycled- the machines are labeled with this and then twice a month I export them out and import them into Assets. This way I can clean up the device inventory and keep track of the computers that are no longer in service. Once I import them into assets I delete them out of active device inventory.
We are testing the BETA 8.0 version and there are other asset status now- Active, Recycled, Repaired, Stored etc.
Posted by:
chucksteel
7 years ago
We do not use the device MIA deletion for a couple of reasons.
We have some machines in our inventory which do not have network access. These are mostly computers attached to scientific equipment (higher education environment) that don't meet our network requirements. Mostly really old Windows XP machines and the like.
Occasionally the KACE agent gets broken and machines stop reporting into KACE. I have scheduled reports that inform the technicians when machines don't check in for more than 30 days to catch these cases most of the time.
I also run a scheduled report once a week that shows duplicate machines by name and I go through and clean out the duplicates. This works in our environment because of our naming scheme. Technicians are supposed to delete the old machine record as part of the replacement process, but that doesn't always happen. Either I catch it in the duplicate machine report or they get notification for the machines that haven't checked in for 30 days report.
Comments:
-
@Chucksteel Hello,
Could you please share with us the report you're ruining to clean the duplicates? also the notification for the 30 days no check. Thanks a lot - ds2009dsfn 6 years ago-
Duplicate computer names:
SELECT MACHINE.KUID,MACHINE.NAME AS SYSTEM_NAME,IP,MAC,OS_NAME,
Date_Format(LAST_SYNC, "%Y-%m-%dT%T.%fZ" ) as LAST_SYNC, CLIENT_VERSION
FROM (MACHINE ,( select COUNT(ID) CT, MACHINE.NAME FROM MACHINE GROUP BY MACHINE.NAME )M2 ) LEFT JOIN ASSET ON MAPPED_ID=MACHINE.ID
WHERE M2.CT>1 and MACHINE.NAME=M2.NAME
ORDER BY SYSTEM_NAME
Computers that haven't checked in for 30 days:
SELECT M.NAME, M.IP, M.OS_NAME, M.LAST_SYNC,
concat('https://kace/adminui/machine.php?ID=', M.ID) as LINK
FROM ORG1.MACHINE M
WHERE LAST_SYNC < DATE_SUB(NOW(), INTERVAL 30 DAY)
ORDER BY LAST_SYNC - chucksteel 6 years ago-
Thank you so much - ds2009dsfn 6 years ago
