IRE does not mark CIs as duplicate. No de-duplication task is created.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Here is the case:
2 CIs belong in the same Class (cmdb_ci_win_server)
Same Name
Same Serial Number and Types
Same MAC Address
Same IP
Identification Rules checked.
Glide properties checked.
Inclusion rules (both Health and IRE) checked.
IRE creates tasks for other classes as normal. What could be the issue here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @dimitrios_l
Why This Happens (Internals of IRE)
1. IRE is not equal to Find duplicates and merge
IRE’s primary goal is identification, not cleanup.
If, Two CIs independently satisfy the same identification rule
And neither CI violates the rule priority
And there is no ambiguity during a single payload execution
As you mentioned: “IRE creates tasks for other classes as normal”
- That’s expected, because other classes:
- Have weaker or more flexible identifiers
- Are more commonly reconciled (e.g., applications, services)
- May involve partial matches or identifier conflicts - For Windows Servers:
- Identification is intentionally strict and non-destructive
- Auto‑merging servers is considered high risk - IRE creates a de‑dup task only when:
- A single payload matches more than one CI
- And the match cannot be resolved by identifier priority
- And one CI is clearly a better match than the other - If the two CIs were:
- Created by separate discoveries
- At different times
- Independently “valid”
Please mark it as helpful or correct solutions as such. That helps others find their solutions.
Thanks & Happy to Help,
Prahlad Kumar (Tera Guru)
Solution Architect at HumIT
ITOM | ITAM | ITSM | CMDB | HRSD
LinkedIn: https://www.linkedin.com/in/prahlad-kumar-92a877117/
If this helps, please mark it as Helpful.
