Allowing Duplicate Machines in K1000 v7.2
Hi,
We're now creating development environments by cloning our production virtual servers. The problem with this is that KACE detects these clones as being the original box just with a new IP address (as the KUID, system name etc. are all the same).
In KACE v6.4 we had Duplication Detection rolled back to pre-version 5.5 which got us around this issue. Support have advised that fix can no longer be applied.
Is there a way we can stop KACE merging these servers whilst continuing to detect duplicate DHCP devices?
Thanks.
Ryan
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Channeler
6 years ago
100% NOT recommended, but here you go:
https://support.quest.com/technical-documents/kace-sma/7.2/administrator-guide/14#TOPIC-733335
Look for "Disable Duplicate Device Detection"
Do it at your own risk.
https://support.quest.com/technical-documents/kace-sma/7.2/administrator-guide/14#TOPIC-733335
Look for "Disable Duplicate Device Detection"
Do it at your own risk.
Posted by:
chucksteel
6 years ago
Check out this KB article, too.
Comments:
-
Thank you, the Rest KUID script does not exist on our box - do you have a copy of that? It think resetting the KUID on the newly provisioned servers may be the way to go for us. Is there a limit to the amount of times KUID can be reset? - RHowe 6 years ago
-
My KBox doesn't have that script, either. I'm fairly certain that the KUID is just stored in the kuid.txt file of the data directory, so stopping the agent, deleting that file, then starting the agent should generate a new key. That should be easy enough to check. It might also be stored in the registry, depending on client version. - chucksteel 6 years ago
-
I have the Reset KUID script and have created a PDF showing the details: https://www.dropbox.com/s/40ztvicdy07o4tc/Reset-KUID-Script.pdf - RichB 6 years ago
