I'm following the Admin Guide and setting up the Assets side of things.

We would like to track our machines based on the Service Tag of the machine (we use Dell machines exclusively).

I think I've set everything up correctly, however if I rebuild a machine using a different name, a new asset record is created rather than using the old record as I was expecting.

See screenshots for the setup.



Where am I going wrong?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


My guess is that you still have the old machine in inventory so the asset you desire to re-use is in use.

You should either inject the old KUID into the registry (guessing windows) of the new machine before it hits the network with the agent OR
delete the obsolete inventory record (but not the asset) before the new machine's agent hits the network
Answered 06/06/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
actually, this is the same issue everyone is having - due to the primary key not being changeable. You will continue to have duplicates ; it will not update the current records and it will create a new one, regardless that you already have a similar item in your asset list.

Good news ; I've been waiting over one year to have this issue corrected and according to the user voice (an multiple tickets with Kace) it will be fixed in 5.3 server update... which I'm still waiting patiently for...

you aren't the only one having this issue.

I also hope they allow you to edit / change multiple assets at one time, like every other product on the market, instead of doing one at a time.

Answered 06/06/2011 by: isolinear
Orange Belt

  • We've been using 5.3 for some time now and I'm still seeing this as an issue.

    I can only assume this is due to how we roll out the Agent.

    At the moment we're using Scripted Installs and adding the Agent as a Post Install Task (as below).

    START /WAIT msiexec /qn /i ampagent-5.3.53177-x86.msi HOST=kbox1000
Please log in to comment
Any idea when 5.3 is due?
Answered 06/07/2011 by: Arcolite
Senior Purple Belt

Please log in to comment
Lets hope before the end of June. The agent itself is only... hmm 4 months behind what they said at the kace conference 2010 so probably some time in August haha.

Answered 06/19/2011 by: isolinear
Orange Belt

Please log in to comment