+1We have duplicate assets that have been imported with the same serial number, but the asset tag number is different. How can we stop this from happening? Besides the obvious of letting 30 other techs know not to do this, I would like a solution that states this is a duplicate asset and to not create. See photo for example.
Best answer by Kathryn Carter
It looks like when these devices were imported, the toggle to match by the asset tag or serial number would be imperative to have those matching. This setting can be found in your MDM.
As for the agents creating new assets on the fly, I would suggest taking away their ability to create new assets.
Thank you for the assist and your thoughts
Are these being created individually, through a CSV import or something else?
There’s a couple ideas out there about this; looks like there isn’t a default behavior to stop this from happening when it comes to individual creation or CSV, though.
+1This happens when the asset tag is wrong and the tech in the field scans by asset tag. Shows no such asset exists, so they create one and thus the duplicate is created.
Sounds like an individual/manual creation, then. Someone else might have ideas, but I don’t think there’s a built-in way to prevent this, other than to restrict asset creation entirely.
+18It looks like when these devices were imported, the toggle to match by the asset tag or serial number would be imperative to have those matching. This setting can be found in your MDM.
As for the agents creating new assets on the fly, I would suggest taking away their ability to create new assets.
Thank you for the assist and your thoughts
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
