How to use "name" field instead "SerialNumber" for importing and updating CMDB via SCCM import?

Igor Virgilio
Kilo Contributor

I'm trying to import PCs via SG-SCCM, but these PCs are from OEM vendor, thus they don't have a well-defined Serial Number field, actually, its value is "To be Filled by O.E.M". 

I've tried to change the IRE rules for this case, to force the reconciliation to use the "name" field (which is unique in the company's CMDB), but it did not succeed.

Any suggestion for this case?

Thank you in advance.

8 REPLIES 8

Yeah, you're absolutely right that the IH-ETL app is a good place for this.  Perhaps even better, because there are more capabilities to define robust transformation logic in here, rather than use a blunt tool like SQL to do this.  I guess my leaning was based on a desire to get this data removed as early in the process as possible because dummy values in identifying fields are just toxic.  But yeah, field transforms in IH-ETL would be a great solution.


The opinions expressed here are the opinions of the author, and are not endorsed by ServiceNow or any other employer, company, or entity.

Hi @Paul Coste and @jgates, thank you for your responses!

 

Today we don't have the IH-ETL plugin installed, and I don't have experience with it yet, so do you recommend to instal this plugin, after that I will be able to set the script to manipulate the data from SG-SCCM? Is not necessary, to install the plugin "Microsoft SCCM spoke for IntegrationHub" (which is paid), right?

 

Thanks again.

I would recommend installing the IntegrationHub ETL plugin.  It is a good way to learn about integrations and make modifications.  You will not need to install the Microsoft SCCM spoke for IntegrationHub.

Here is a link to a demo video so you can get a better understanding of the tool.  There are multiple tutorial videos you can find with some youtube searching if you want to learn more.

rambabuboyapati
Kilo Guru

I would recommend removing the Serial Number mapping until the Serial Number data is fixed in SCCM. Otherwise, you will end up updating the wrong CIs.