KACE Product Support

You are 100% right...

http://www.kace.com/support/resources/kb/article/Understanding-and-Dealing-With-Duplicate-Machines-In-Inventory

I am having issues where one of the IDs on some machine were changing and generated duplicate machines, this solves part of it.

I would definitely check out http://www.kace.com/support/resources/kb/article/Understanding-and-Dealing-With-Duplicate-Machines-In-Inventory since I wrote it :D

Seriously though, I recommend it.  Keep in mind the following things...

Semantics are very important when asking this question.  Are you seeing duplicate machines? or stomping. The article above clarifies the difference but most will call them the same thing.

Also, are you concerned with this problem in machine inventory? or  computer assets?  The first is easy to clean up the latter may not be so easy. 

And then you need to remediate the symptoms but also prevent it from happening again.  The article addresses that as well.  

In my opinion, if you have:

• the "disable duplicate machine detection" AMP option checks (which means disabled)
• an imaging process where the agent is installed (post-install task) AFTER the machine is renamed
• an re-imaging process where the old KUID is sucked out and then put back into that machine (again easy with a K2 in two different ways) 

The sooner you identify the problem the easier to prevent and cleanup. Consider adding the reports from the article as email alerts or daily scheduled reports.

Here's a report that finds duplicate computers via system name:

 SELECT MACHINE.KUID,MACHINE.NAME AS SYSTEM_NAME,IP,MAC,OS_NAME,LAST_SYNC
FROM (MACHINE ,( select COUNT(ID) CT, MACHINE.NAME FROM MACHINE GROUP BY MACHINE.NAME )M2 ) LEFT JOIN ASSET ON MAPPED_ID=MACHINE.ID
WHERE M2.CT>1 and MACHINE.NAME=M2.NAME
ORDER BY SYSTEM_NAME