Currently when receive new inventory, we create an asset as we tag it and place it into storage. Once we deploy a pc, Kace creates the device in inventory and another asset which is linked to the device in inventory. We would like for that original asset that we create to link to the device in inventory rather than it creating a duplicate. Will changing the Mapped Inventory Field to use Bios Serial number and the Matching Asset Field to Serial Number accomplish this(as long as the 2 values are the same)?
Also, will changing this mapping cause anything to "break" or lose the link between our currently linked assets and devices?
You need to make sure that the link between Inventory and Asset is matched up with the data that you use for creating the initial Asset record. As an example we recommend that following, that the Asset name is the Serial number from Inventory, this is set in the device asset type.
This means that when our BarKode scanning customers receive equipment at Goods in, they can scan the serial number barcode on the box, this creates the asset with a name of the Serial Number. This means that when the machine is provisioned and checks into inventory it should then match the Serial number field from the inventory record with the asset name.
As another example if you want the Asset tag to be the name of the asset, then create a serial number field within your Device asset and set the Device Asset type to map the Serial number from Inventory into that field. You will need to make sure that the serial number value is correct within the asset field, again our BarKode customer can scan the serial tag in as an additional data item, which reduces "finger trouble".
Again once the machine is provisioned it should then match the serial number from inventory into the Asset field and just link the two records.
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
efforts, please visit