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

Thor A Simensen
Giga Contributor

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?

1 ACCEPTED SOLUTION

Thor A Simensen
Giga Contributor

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

View solution in original post

22 REPLIES 22

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).

Hi there, would it be possible for you to share that onBefore code? I'm keen to keep the network adapter information but I don't want the ndiswan multitude of records.

Paul Wilson
Giga Contributor

Hi there, would it be possible for you to share that onBefore code? I'm keen to keep the network adapter information but I don't want the ndiswan multitude of records.

 

Add a new Transform Script to https://???.service-now.com/nav_to.do?uri=sys_transform_map.do?sys_id=45b0b598ef13210098d5925495c0fb00

NameValue
WhenonBefore
Script
(function runTransformScript(source, map, log, target /*undefined onStart*/ ) {

	// ignore Windows intermediate driver (i.e. fake interface)
	if (source.getValue('u_servicename0').toLowerCase() == 'ndiswan')
		ignore = true;

})(source, map, log, target);

 

Paul Wilson
Giga Contributor

Brilliant! works perfectly. Thank you for that.