Duplicate Asset created

[Thor Simensen]

We recently implemented SCCM 2012 v2 plug-in in our Development environment, but we are getting duplicate assets created about the time the SCCM integration runs.   However, the duplicates don't happen every evening when the SCCM integration runs.   And there are no duplicate CI's being created, just duplicate assets.

After SCCM creates the CI, is there a different process that then creates the Asset?

[Pradeep Sharma]

Hi Thor,

Check for the BR "Create CI on insert"

[Michael Kaufman]

Couple ideas:

It could be the Create asset on model change business rule.   Maybe the integration is changing the model and clearing the asset field on the CI during the import.   There are multiple imports on the SCCM integration which might cause that.

Another idea is that you are actually causing CI duplicates and don't notice them yet.   Here are some scripts to help find duplicates: Duplicate Record Scripts — ServiceNow ELITE.com

I had issues with older versions of the SCCM integration in the past due the coalease (matching) method used by the integration.   It goes off a coorelation id, but every time they would reimage a computer, the correlation id would change and cause a duplicate.   I had to switch the matching so that would stop.

[lileem09]

I experienced the same issue and switched the coalescing value to serial number only. I'm in the middle of testing SCCM 2012 v2 for a new client, and will be interested in seeing if I experience the same issue - for now, I am performing UAT using the OOB coalesce rules.

[Michael Kaufman]

Switching to serial number is good if it always available.   I wasn't able use serial number that at the client I was at because serial number was empty on a lot of CIs.   You could only import the CIs that had a serial number which might work.

The issue with the coorelation id (resource id) and the reimages is that you don't notice it on the first import.   It takes until the first reimage that a duplicate shows up.

Mike