SCCM Creates Duplicates when machines are imaged

[smfoister]

Good morning,

I'm noticing that we're getting some duplicate CI's from SCCM after machines are imaged. This appears to happen because SCCM generates a new correlation ID for these machines and during the SCCM import it attempts to match a correlation ID that is no longer valid. Identification rules for computers have Correlation ID as the first matching criteria followed by serial number,serial number type.

I'm considering altering this identification rule to put correlation ID after serial number. Will this have any other side effects that I may be overlooking? Does this sound like a prudent way to approach this issue?

[Andrew Westerv4 · Accepted solution]

The IRE goes through all of the different steps and doesn't just stop at the correlation ID. When this scenario happens, the default SCCM integration and IRE setup wouldn't duplicate CIs. It sounds like something has been customized with your integration that it's failing these steps.

[smfoister]

Now that you mention it and I'm thinking about it I know what's happening. We had a partner attempt to integrate two different SCCM databases uaing the 2012 and the 2016 integration and we had some duplicated correlation IDs come from the secondary integration. It took weeks to clean up that mess and this is sounding like residual.

[Ashutosh Munot1]

Hi,

I Agree with Andrew, If correlation id is not matched it will always check for Serial number and other rules on it. If match is found then it will not create a new CI instead update it.

Also in first go it will check sys_object_source table to see if the Correlation id is mapped with Any CI. If yes it updates it or else it goes and trigger IRE engine.

We have include Host name as additional field on form and we have included the same on Identifiers which is last rule in our list.

Which Version of SCCM are you on 2012, 2016?

Thanks,
Ashutosh Munot

[Damhoej]

This might help

Clone Hyper-V virtual machines (servicenow.com)