Recently, I switched the way an inventory item is linked to the asset and I was under the impression this would take care of a concern of mine.  We reuse machines quite a bit and for good measure, we remove and replace the harddrive before reusing.  Sometimes we have to rename the machine after reinstalling windows and I thought linking the inventory item to the asset (BIOS serial #) was the solution to our problem, apparently I was wrong.  

THE PROBLEM:  After reinstalling windows, renaming, and adding to our domain, a single machine is creating another separate asset with the same name (BIOS Serial #) and also creating another inventory item.

Answer Summary:
0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


set the KUID of the old agent and all is fine.

Answered 07/17/2013 by: Nico_K
Red Belt

  • Thanks for such a quick response! Can you please specify the best way to do this with the end result being a full history report including the machine name change...

    Am I supposed to delete the unconnected amp from inventory and run the reset kuid script or is there a way to retrieve the kuid from the old one and manually set it on the new one???

    I apologize if this has already been covered, I'm just not finding what I'm looking for and I have been short on time anyways due to troubleshooting/fixing broken ampagents.

    Thank you !!!
  • the easiest way is using the set KUID post install task, alternatively you can also modify the amp.conf (c:\programdata\dell\kace\amp.conf) by hand.

    You should also review this article:
Please log in to comment



Typically what you want to do is.


1. Keep the mapping to BIOS for Mapped inventory field and matching asset field as BIOS

2. Reimage device

3. Delete old device name from Inventory( this will orphan the asset record)

4. Install the agent on the newly imaged system (it will then look for the matching BIOS that isn't attached to a record and join it)



Answered 07/17/2013 by: nshah
Red Belt

  • Is there an alternative to re-imaging the PC???? It was kind of a time sensitive job and it went to one of the big wigs of our company, who puts up such a fight when he has to part with his laptop for any amount of time... LOL

    I could probably get away with just removing the "old" inventory device and running the KUID reset script, no???
  • the KUID is a hardware/software so if you are just replacing the HD then you can do what Nico_K indicated but if you are completely reimaging the box, then you can simple delete the old record before installing the agent again on the same device.
Please log in to comment
Answer this question or Comment on this question for clarity
Share SNMP OID and MIB Information
It’s easy to add custom SNMP OID GETs to your Dell KACE K1000 inventory, but where do you find the exact OIDs you need for a specific device? This is the place to share the OIDs and MIBs you have – and to request the ones you need.