Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
How to configure SCCM Import to use IRE (Identification and Reconciliation Engine) and Datasource Precedences - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • How to configure SCCM Import to use IRE (Identification and Reconciliation Engine) and Datasource Precedences
KB0721378

How to configure SCCM Import to use IRE (Identification and Reconciliation Engine) and Datasource Precedences


7855 Views Last updated : Feb 8, 2024 Internal, public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

Out of the box, IRE (Identification and Reconciliation Engine) is partially used by SCCM, in transform map "SCCM 2012 v2 Computer Identity".
It's used in the sys_id script, to check whether a CI exists. Since it doesn't do update directly, the Datasource Precedence rules are not used.

 

The onBefore script in below link should NOT be used for SCCM
Apply CI Identification and Reconciliation to Import Sets

 

Workarounds

Please note: We have developed new SCCM integration that uses IRE and RTE (Robust Transform Engine) (SG-SCCM).

Please try to setup new SCCM integration unless you have specific needs to use legacy SCCM.

If the aim is to make sure SCCM doesn't update CIs that were created/updated by Discovery, then the transform maps can be modified to check on the discovery_source field of the CIs:

if discovery_source value is 'ServiceNow', which means updated by Discovery, then SCCM will skip this record.

Attached "SCCM 2012 checking discovery_source.zip" is a demonstration of how this can be achieved.

The demonstration is based on SCCM 2012 v2. 

 

Below is the list of modifications made:

***Transform Map: SCCM 2012 v2 Computer Identity 
modified field mapping sys_id 

***Transform Map: SCCM 2012 v2 Operating System 
modified field mapping sys_id 

***Transform Map: SCCM 2012 v2 Processor 
modified field mapping sys_id 

***Transform Map: SCCM 2012 v2 Disk 
modified transform map script 

***Transform Map: SCCM 2012 v2 Network 
modified transform map script 

 

For SCCM 2016, make similar modifications to the relevant files.

Related Links

SCCM Integration transforms do not use the 'Identification & Reconciliation' engine for the CI Inserts/Updates, causing e.g. bypassing of the Precedence rules


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • SCCM 2012 checking discovery_source.zip

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.