First Discovered Field is getting populated on each discovery from null to a fixed time stamp.

[Ssinha4]

We have Azure and sccm in IRE that updates the windows server field. No mapping/script in RTE for first discovered field. There are only few servers having this issue.Kindly help.

[shubhamseth]

@Ssinha4 

Since only a few servers are affected, this is unlikely to be an IRE rule or RTE mapping issue.

The first thing I'd check is which source initially created those CIs.

Review the Identification Attempts, sys_object_source, and CMDB Audit History for the affected servers to identify which data source first inserted the CI. Also verify whether Azure or SCCM is creating a new CI instead of matching an existing one due to identifier differences (hostname, serial number, UUID, etc.).

If there is no mapping or script updating First Discovered, it's usually being set when the CI is initially created. IRE won't update this field on subsequent reconciliations unless the record is recreated.

My focus would be on identifying why those few servers followed a different identification path rather than looking at reconciliation rules.