KACE Product Support Question

Why is my K1 renaming computers in inventory to another machine's name and then removing the inventory entry?

02/09/2015 1319 views
I had some machines in a lab that weren't showing up in our inventory.  After installing/upgrading the agents on those missing machines and then verifying that the agents were indeed running I deleted all of the machines for that lab from the asset list and the inventory (in hopes that they would be rediscovered).  When they didn't all show up the next day I searched the asset history and saw this:

Report by agent        computer        CL-10        Modification        Name        'Name' changed from 'CL-Instructor' to 'CL-10'

Shortly after that entry CL-10 was renamed to CL-20.

So now my inventory no longer has the Instructor machine or the CL-10 machine.  CL-20 is there (verified the MAC address to make sure it was the right one).  Any thoughts on why this is happening?  Thanks in advance.
Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author

check the machines to see if you have duplicate KUID's in the registry.
Answered 02/09/2015 by: SMal.tmcc
Red Belt

All Answers

Also check your link between Inventory and Asset, we find having your Asset name linked to the Service Tag in inventory means that a single Asset record will maintain the link to a machine even if it is rebuilt and renamed
Answered 02/09/2015 by: Hobbsy
Red Belt

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ