KACE Product Support

Ahhh, there is someone else.... I thought I'm the only one. I get 10 to 40 dupl. machines every day and that for over a year. I also marked DDMD with no effect. Support is working on it....... In my case the dupl. machine comes up, after a few minutes it leaves the old machine name and takes another machine name, which will be detected as a dupl. machine. An so, it jumps through 10 to 40 machines every night.

Duplicate Machine Detection is designed to reduce this issue; I wouldn't recommend disabling it to solve duplicate machines. If anything disabling it would most likely increase the amount of dupes.
anthonyw please open a support ticket on this. The more scenarios we see the better we can address it in future releases.

I admit, this is a very confusing option. You have to check it to disable it, or as some would say you have "enable it to disable it".

I digress, IMO, this option should be checked on all kboxes by default. Please read this faq which will help to clarify what situation you actually have an how to resolve it:
http://www.kace.com/support/kb/index.php?action=artikel&cat=3&id=673&artlang=en

What duplicate machine detection was designed for, as I understand it, was to avoid a situation where multiple physical machines try to use the same KUID. Most common cause would be if you installed the KBOX Agent on a machine, and then turned that machine into a source image, and imaged a bunch more machines with it. In that case, they would all have the same KUID. So when the KBOX detects a duplicate KUID connecting, it generates a new KUID for whichever one connected second. But if you're not imaging with the Agent baked in, you don't need Duplicate Machine Detection turned on.

I have this problem too - even with Duplicate Machine Detection off, I still get dupes. I think what the users are doing is switching from wired to wireless on the fly. Or, it's possible that they have their wired and wireless networks connected simultaneously. Disabling DMD helped, but did not completely resolve the problem.

But if you're not imaging with the Agent baked in, you don't need Duplicate Machine Detection turned on.
I think that all customers including those above should have Disable Duplicate Machine Detection option checked. Those that are imaging are only susceptible to the duplicate KUID problem (which I would like to rename "inventory stomping" to avoid confusion) if they have a poorly designed imaging process. A poorly designed imaging process is one that has:

1. neither followed http://www.kace.com/support/kb/index.php?action=artikel&cat=2&id=565&artlang=en
2. nor setup the agent install as a post-install task

http://www.kace.com/support/kb/index.php?action=artikel&cat=54&id=851&artlang=en

TJSmithICQ, also you may be confusing duplicate machines with duplicate KUIDs. But I can't be sure because when you say Duplicate Machine Detection off what does that mean? Does that mean the the option titled Disable Duplicate Machine Detection is unchecked (some would say that unchecking a box is disabling the option-- i.e. unchecked? or Is the checkbox checked meaning it is disabled?

I think if users follow faq 673 that their situation will become clear and how to address it. If people continue to see problems after following that then please open a ticket and we'll address that and update that document.