Allow custom selection of criteria for duplicate machine detection algorithm
The duplicate machine detection alogirithm is not very good and is certainly NOT once-size-fits-all even though it attempts to be.
Different items are unique in different customers environments. please provide a way for us to choose which inventory fields drive what is a primary Key in our environment. ps. it would be BIOS Serial number for us, although i know that doesn't work for everyone.
Fortunately, this is true for our dell hardware
Dee Dee commented
This is something that absolutely needs to be taken care of especially with virtual desktop environments and the recomposal of desktops. Using VMWare HOrizon View, the assets are duplicated multiple times if recomposals are done. This is daunting to manually remove these so that they are not showing up as listed under patching, etc. when scanned.
We have an enormous challenge with duplicate records in our computer asset table. The issue doesn't occur during bulk asset imports so long as the current PK is selected, However, I want KACE to prevent anyone from attempting to add another record to the computer asset table if the serial number already exists. By default (at least at one time) KACE prevented duplicate computernames but that's not ideal for our environment. This would have to be an opt-in feature and I realize we'd have to clean up our existing table before we could turn it on.
Yeah this is severely needed in situations such as ours, we're in a school with 2200 devices and students get their devices re-imaged fairly regularly... because.. well... students..
Being able to configure this would be outrageously useful.
SUPER CONCUR...The ability to pick would be great! Anything is better than just duplicate. MAYBE even have the ability to pigeon hole ONLY the items that are at risk of duplication. Place them in some label, place, or state where the admin can go in and make the selection on at risk items. It would be much better to have to correct known problem systems than simply duplicate. Why would you ever opt to use the UID on of the client, the IP address...really? Or even the MAC address. If you replace a motherboard, the serial may change with some manufactures, but Dell lets you set that back to the service tag. PERFECT starting point. If you don't have a Dell, than you know to take additional steps to correct those rare instances. Integrating mac address, IP address, or anything other sort of non static data is shows weakness in design.
We have asset tags assigned to our machines and the name of the computer includes the last four characters of the asset tag. I would love to tell KACE to look at Serial number first, look at the machine name second, third check would see if this Serial and Name already had a UID. If so, It's the same system. If not, it goes into some kind of temporary association state and Admin gets alerted.
No comments on this since 2013?
Either everyone just deals with system duplication, or there's a lot of censorship by the moderators.
Either way, glad to see this one out there!!!!