SCCM SGC requiring identification rules for non-CI tables?

[Claire Ashdown2]

Hello! We are working to implement the SCCM Service Graph Connector, but have run into a problem. The payload is immediately going into the CMDB IRE Incomplete Payloads table, I believe because we are getting an IDENTIFICATION_RULE_MISSING error on the cmdb_sam_sw_install, cmdb_serial_number, and cmdb_key_value tables. However, those three tables are not extended from cmdb_ci, and as such do not appear in the CI Class Manager to add identification rules to them. I know I can add them directly to the Identifiers table, but am concerned about doing so for a non-CI table and where no OOB identification rules already exist (I have checked our instances as well as my PDI to verify that identification rules do not exist OOB for these tables already). Does anyone happen to have any guidance or documentation on adding the apparently required identification rules to cmdb_sam_sw_install, cmdb_serial_number, and cmdb_key_value tables? Anything in the SCCM SGC documentation, or any guidance on adding identification rules to those tables generally in a safe manner? Where other processes (like discovery) may use cmdb_serial_number and cmdb_key_value, I am concerned that adding an identification rule to help the SCCM SGC work may impact another process in a way I'm not expecting.

Many thanks!

[CMDB Whisperer · Accepted solution]

Are you using the Utah release by chance?  Utah is the first release that supports IRE for non-CMDB tables, so you could create them in Utah, and it is expected to need to create the identifier directly, since as you point out, it is not possible to do so in the CI Class Manager.  If you are not using Utah then you will not be able to create the Identifier Entries manually.

All that said, regardless of what release you are on, I would not expect an error of this sort to occur in SGC, and would contact Now Support for  further troubleshooting and a fix.

[Claire Ashdown2]

Thank you for the quick reply! No, we are not yet on Utah, but IRE support for select non-CI tables (like sys_user and cmn tables, not sure about these specific three...) is indeed going to be a very helpful feature. We are on Tokyo, and are using version 3.2.1 of the SCCM SGC that is supposed to be compatible with Rome through Utah, including Tokyo. We tried going directly to the identifier entry to create identification rules for them anyways and found what you did -- that it is simply not possible.
Again, many, many thanks for your quick reply. We really don't want to wait until Utah, and so will hope to hear back on our Support ticket soon then.