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?

[Ant2]

I am having this same issue, but am on Paris and using the Service Graph connector for SCCM with integrationHub ETL.   So it is a little bit different.  Any pointers on how to fix it?

[Bob Kolosky2]

Which network adapter(s) is this happening with?

With the new Service Graph Connector, 'ndiswan' is explicitly being excluded from the 'SG-SCCM Network' Data Source query:

SELECT
dhcpenabled0 as dhcpenabled0,
macaddress0 as macaddress0,
servicename0 as servicename0,
ipaddress0 as ipaddress0,
ipsubnet0 as ipsubnet0,
defaultipgateway0 as defaultipgateway0,
TimeStamp as TimeStamp,
resourceid as resourceid
FROM v_GS_Network_Adapter_Configuration
where ipaddress0 is not null and macaddress0 is not null and
servicename0 NOT IN ('NdisWan')

You could add additional adapter names to exclude from the query if they are exhibiting the same behavior as ndiswan does. Virtual adapters that change MAC address each time the laptop is docked/undocked or on/off VPN could still cause this issue.

[Ant2]

Hi Bob

Thanks for the response.  After some digging around I realised that the NdisWan entries were from the previous SCCM integration we had, but didn't notice the select statement had excluded them from the Service Graph connector.

Much appreciated.

Ant