Disk Table Not Populated via SCCM Integration

[syed_but_not]

Hi, 

I've set up our SCCM integration and we've been pulling data for quite some time now. The CI data mostly looks good, however we noticed that a bunch of models were created without assets under the manufacturer (Standard Disk Drive), which I now realize are coming from the Disk data source. When I look at the robust transform for SCCM Disk, I see that it's mapped to the CMDB Disk table and that the relationship between the Disk and the CI is there as well, however this relationship isn't being established and our CMDB Disk table is empty. Does anyone know why this is happening? Are these supposed to be generated as models instead of disks? We haven't modified anything regarding Disk since setting up the integration

[Andrew_TND]

Hi @syed_but_not 

From what your saying it was set up correctly from an asset point of view but doesnt create the CI's, an asset needs to be converted to Ci which is why you've got no data in your cmdb_ci_disk table.

All is not lost, that and can be easily remedied. Just create a new robust transformer which points towards the cmdb_ci_disk table, coalescing the computer or asset field... Essentially the field which would normally be populated by the "Converted from" CI. 

When you run it once it will update all your disk information more or less over night.

The second option if you dont want to touch the SCCM module would be to set up a business rule on your asset table to push the disk data through to cmdb table on insert or update to create the CI's.

Please mark as helpful or if it resolves the issue, CORRECT!

Andrew Robinson
ServiceNow Developer

Follow me on Linkedin!

[syed_but_not]

Hi @Andrew_TND, I'm a bit confused by what you mean here. The disks are not being generated as assets, just models, so I'm not sure which assets you're referring to that need to be converted to CI's or how that would populate the disk table.

[Andrew_TND]

Hi @syed_but_not 

Right okay, in that case if it’s just being crested as a model, create a second transformer to populate the cmdb_ci_disk table or a business rule which creates CI. Ensure the model matches the existing records so you can maintain the relationship.

[syed_but_not]

Hi @Andrew_TND 

We would be able to do this, however we'd prefer to figure out why the mapping that's already predefined by the integration isn't working. I understand now that the models are being generated through the Cleanse Manufacturer Model transform operation, so it isn't that the data is being mapped to the hardware table but that the data isn't mapping at all despite the fact that it's supposed to map to the disk table.