How do we add a computer with an existing Asset record to the Inventory without it creating a duplicate Asset record?

When we purchase computers, we put them in Kace as Assets.  Then, when we go to image them and install the Kace Agent on them, it creates a duplicate Asset record.  How can we sync the initial Asset record that was created when we manually entered them with the Inventory record when we image them?


0 Comments   [ + ] Show comments

Answers (1)

Posted by: Hobbsy 1 month ago
Red Belt

Your issue is that you do not have the link set between inventory and asset correctly.

In your Device Asset type, create a serial number field and then link the Inventory to the Asset like this image:


What you also have to ensure is that when you create your new assets, on delivery, the serial number field must be populated, that way KACE does not create any duplicates.

The easiest way to do that at goods in is to barcode scan values in.

You may also like to be aware there are some settings that affect duplication of assets, if you look in Settings>Provisioning>Communication settings you will see this at the bottom of the screen.


I would only recommend the BIOS Serial number setting, as relying on any of the other scan cause you issues.

Finally also make sure that if you are using MIA settings in inventory, never use the auto archive, this has the capability to screw your asset records up beyond belief.



If you would like to know anything more from my decade plus times managing assets with KACE, just get in touch and we can set up a call.

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