SG-SCCM Dependent CIs Most Recent Discovery date not being updated

[ctdemato]

Hello. Several months ago, I installed the SCCM service graph connector.  The computer CIs populate, and update as expected. Dependent CIs populate insert as expected. However, once the related items are rescanned, the Most Recent Discovery date is not updating. This is causing our stale items count to be way off because of the old date, even though these items are scanned daily. I checked a few samples in SCCM and the SCCM hardware scans have occurred very recently, if that has anything to do with it. Any guidance would be appreciated, as I do not want to have to maintain these discovery dates manually. 

[k_lutz]

Hello ctdemato,

My guess is that it relates to this article: https://www.servicenow.com/community/cmdb-blog/service-graph-connector-for-microsoft-sccm-updating-m...

In the RTE, the property is most likely set to true which is not having the value updated and there is no follow-up job like the one mentioned which runs for the computer. I am not sure of the best option but I would check here and at least you would know why that it is happening. You could then try tests with that set to false or maybe coming up with another mechanism to update the dates when the date on the computer record is updated.

[ctdemato]

Thank you for the follow up. However, I already had set that for the 4 definitions to false.

[k_lutz]

You may need to check your recon rules or other logic. In our setup, we had true set and in non-prod I turned the network adapter to false and the date got updated as expected. In looking through other postings, it seems like changing it to false is not suggested because it can have unintended impacts. In looking at the setup, it seems like you could add a post processing script to SG-SCCM Last Discovered Update schedule and have the related entries updated but that is only a suggestion...not sure how well it work work in practice without testing.

[Will O]

I suggest looking at the "last_discovered" and "IRE" related system properties to see if these are affecting how SG-SCCM is updating Most Recent Discovery (Last Discovered): 

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/configuration-managem...

I would also validate within the IntegrationHub ETL that the SG-SCCM Last Discovered Update RTE is populating the expected data info on the sample import sets.

Here are some excerpts from my notes that I found helpful: 

Last Discovered related Sys Properties

glide.identification_engine.ire_message_listener_skip_updating_source_last_discovered_to_now

The ServiceNow system property glide.identification_engine.ire_message_listener_skip_updating_source_last_discovered_to_now is related to the Identification and Reconciliation Engine (IRE) and its behavior when updating the last_discovered field of Configuration Items (CIs) in the CMDB.

Purpose: This property controls whether the IRE should skip updating the last_discovered field to the current timestamp (now) when processing discovery messages.

Behavior:

• TRUE: If set to true, the IRE will not update the last_discovered field to the current timestamp when processing discovery messages. This means the last_discovered field will retain its previous value unless explicitly updated by the discovery payload.
• FALSE: If set to false, the IRE will update the last_discovered field to the current timestamp whenever it processes discovery messages. This is the default behavior, ensuring that the last_discovered field reflects the most recent discovery activity. This property can be useful if you want to maintain the last_discovered field based on specific criteria or external updates rather than automatically updating it with each discovery run.

 ServiceNow Community - Preventing Discovery Data Source from updating "Most Recent Discovery" field

glide.identification_engine.skip_updating_source_last_discovered_if_older

The ServiceNow system property glide.identification_engine.skip_updating_source_last_discovered_if_older is used to control how the Identification and Reconciliation Engine (IRE) updates the last_discovered and discovery_source attributes in the CMDB.

Purpose: This property determines whether the IRE should update the last_discovered and discovery_source fields when the discovery data is older than the existing data in the CMDB.

Behavior:

• TRUE: If set to true, the IRE will not update the last_discovered and discovery_source fields if the discovery data provided in the payload is older than the existing data in the CMDB. This helps prevent older or stale data from overwriting more recent information
• FALSE: If set to false, the IRE will update the last_discovered and discovery_source fields even if the discovery data is older than the existing data in the CMDB. This is the default behavior, ensuring that the fields are updated with the latest discovery run

This property is useful for maintaining the integrity of the last_discovered and discovery_source fields, ensuring that only newer data updates these fields.

skip_updating_source_last_discovered_to_now

The ServiceNow system property skip_updating_source_last_discovered_to_now is used to control whether the Identification and Reconciliation Engine (IRE) updates the last_discovered field to the current timestamp (now) when processing discovery messages.

Purpose: This property determines if the IRE should skip updating the last_discovered field to the current timestamp when processing discovery messages.

Behavior:

• TRUE: If set to true, the IRE will not update the last_discovered field to the current timestamp. This means the field will retain its previous value unless explicitly updated by the discovery payload
  
• FALSE: If set to false, the IRE will update the last_discovered field to the current timestamp whenever it processes discovery messages. This is the default behavior, ensuring that the last_discovered field reflects the most recent discovery activity
  

This property is useful if you want to maintain the last_discovered field based on specific criteria or external updates rather than automatically updating it with each discovery run.

ServiceNow Community - Preventing Discovery Data Source from updating "Most Recent Discovery" field 

IRE - Prevent Records with an Older Last Discovered Date from updating CIs