Reconciliation rule not working on Windows server table

venkram
Tera Contributor

4 weeks ago

Hello Everyone,

 

Recently we have created a reconciliation rule on Windows Server table and we keep first priority is ServiceNow and second priority is SG-SCCM ad third priority is SG-Intune and we have selected apply to all attributes.

 

the issue is SG-Intune is still updating Operating System, OS Version and Disk Spaces fields even though SG-SCCM is already updated. Could someone please help me.

 

@Ankur Bawiskar 

@Dr Atul G- LNG 

@AJ_TechTrek 

0 Helpfuls
  • 804 Views
1 REPLY 1

ayushraj7012933
Mega Guru

3 weeks ago

Hi @venkram ,

This kind of issue is usually related to how reconciliation and data source tracking are working in CMDB.

Even though you’ve set the priority as:

  • ServiceNow

  • SG-SCCM

  • SG-Intune

and applied it to all attributes, a lower priority source like SG-Intune can still update fields if a few things are not configured properly.

First, check the discovery_source on the CI record. Reconciliation depends heavily on this field. If SG-SCCM is not correctly setting discovery_source = SG-SCCM, the system won’t treat it as a higher priority source, and SG-Intune may overwrite those values.

Next, make sure the data is going through the Identification and Reconciliation Engine (IRE). Reconciliation rules are only enforced when IRE is used. If updates are coming through transform maps without enabling “Use IRE”, or via scripts/direct updates, then these rules can be skipped. So it’s important to ensure that “Use IRE” is enabled and the correct data_source is mapped.

You should also check the sys_object_source table. Each CI should have proper entries for both SG-SCCM and SG-Intune. If these entries are missing, ServiceNow may treat incoming data as new or unmanaged, which allows overwrites.

Additionally, review your reconciliation rule again. Make sure there are no conflicting rules. If the issue continues, you can create attribute-level rules for specific fields like Operating System, OS Version, and Disk Space. This gives you better control compared to applying the rule to all attributes.

Finally, I’d recommend enabling IRE debug logs by setting:
cmdb.ire.debug = true

Then run updates from both sources and check the logs. They will clearly show which source is updating the fields and why the system is allowing it.