SCCM Integration - Mulitple Network Adaptors

joespenceley
Kilo Contributor

‎05-10-2017 09:44 PM

Hello,

We are new on the road with ServiceNow and run into a problem with the SCCM Integration Module.

For a small number of computer objects SCCM is also importing multiple unnamed Network Adaptor CIs.   As these are unnamed, they sort to the top of the CI list causing issues with Incident and Problem creation.

Wondering if anyone else has seen this and found a away to deal with it.

Thanks,

Joe

Labels:
0 Helpfuls
  • 877 Views
2 REPLIES 2

sachin_namjoshi
Kilo Patron
Kilo Patron

‎05-10-2017 09:48 PM

You will want to check the box Enforce CI Verification on your respective model categories to prevent SCCM from just blindly creating asset records for you. The CI data will be there and you will need to figure out a way to effectively join that data but it will keep your asset tables cleaner.



Model Categories - ServiceNow Wiki



Regards,


Sachin


akash_mehta
ServiceNow Employee
ServiceNow Employee

‎05-11-2017 02:06 PM

I would have to do more investigation on the network adapter side - I'm thinking adding something on the network adapter transform map to not allow insert if no name exists - or if name is null - adding some sort of calculated default value



Additionally, you could have a reference qualifier added to your CI reference field on the Incident or Problem table to not display the CI when name is NULL.



-Akash


0 Helpfuls