Why do I have over 500,000 network adapter ci's in cmdb

[Thor A Simensen]

I only have about 20,000 computers, servers, and network devices in the cmdb, but have over 500,000 network adapter ci's.   Is this normal, or is there something I don't have configured right?

[Thor A Simensen]

There was something with SCCM integration that was creating all the network adapters.  We disabled the Network import from SCCM and then cleared out the network adapter table from the MySQL database.

Network adapters reported from Discovery were created fine and we haven't turned back on the SCCM network import.

[llewellynbartle]

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

[Wendy Morin]

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

[Thor A Simensen · Accepted solution]

We ended up removing the network adapter field from the Transform map for the SCCM integration.

[Wendy Morin]

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.