How does SG-SCCM determine when a CI can be updated?

[paulciarfella_w]

I am evaluating using SG-SCCM for computer and software inventory.  We are also running discovery for servers.

I need some help to understand how SG-SCCM determines if a computer CI needs to be updated.

For example, I run an SCCM import, a computer is updated or created and the Assigned to field is set.

I then clear the Assigned to field and the Most recent discovery field on the Computer CI, and the Last runtime field in the SG-SCCM Computer Identity data source.  I then rerun the import.

I do this multiple times where sometimes the Assigned to field gets set correctly from the SCCM Computer record, and sometimes it does not.

I see the computer getting processed via the robust transform map.  But its an overcomplicated abstract beast to me, and I'm unable to decode how it decides to update or not.

Can anyone shed light on how the SCCM processing works and how it determines when to update a CI?

[Rahul Priyadars]

Coming to Your Point-I do this multiple times where sometimes the Assigned to field gets set correctly from the SCCM Computer record, and sometimes it does not.

How it Works

Transforming the assigned user

The SCCM <version> Computer Identity transform script attempts to set the Assigned to field in the CMDB record by looking up the name of the user in the SCCM source table and comparing the value with the matching field in the ServiceNow sys_user table. If a match is found, that user is assigned to the record. If no match is found, the Assigned to field is left blank. The matching field is controlled by the glide.discovery.assigned_user_match_field system property, which is set to user_name by default.

How general update works:-

The SCCM integration uses CI identification to update CIs created from data imported from SCCM with a resource ID. The Hardware Rule identifier returns the resource ID of a computer from SCCM and stores it in the Source [sys_object_source] table. When resource IDs are first imported, either from SCCM or Discovery, the [sys_object_source] table is populated with IDs for each CI it identifies. In subsequent imports, if an incoming ID matches that of an existing CI, IRE (Identification and Reconciliation Engine) updates the information for that CI in the CMDB. If the incoming resource ID does not match that of an existing CI, IRE creates a new CI and populates it with the resource ID.

Regards

RP

[Paul Ciarfella]

I understand the mechanism of the update and how IRE.

What I am trying to understand is the inconsistency of why is it sometimes updating a CI and why it is NOT updating when there are changes.

[Rahul Priyadars]

Post IRE logs here ..logs will give clue.

[Paul Ciarfella]

Thanks for the offer to look but I do not post logs from my corporate systems into public forums.