Hi

We have experienced the very same issue. We know the reason this happens is because how SCCM stores the records. I.e SCCM will record different MAC addresses for a particular device over time as it connects to different docking stations... if it's a laptop for example.

ServiceNow will just accept the data coming from SCCM as it imports, so it will create a brand new record against the ServiceNow Ci every time there is a new mac address reflected on the device SCCM record.

At the moment we can't seem to use the MAC address, Network adapter name or network adapter category names to coalesce and get around this issue.

Does anyone have a solution or possible workaround for this apart from using discovery?

Thanks

Llewellyn

Anyone find a work around for this item? We're having the same issue..

We're only using SCCM for asset scans, we don't have discovery.  It would be ideal to capture this data in the CMDB, however in it's current format isn't useful.

It looks like lots of "ndiswan" adapters are being created, which I think is a virtual device created by Windows.

I've added an onBefore to the SCCM Network transform that ignores any device with a name of "ndiswan" (ignoring case).