SG-SCCM causing duplicate CI's
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2022 09:01 AM
Recently we converted SCCM integration to new Service Graph SCCM integration, and now we are getting duplicate Windows Server CI's being created with Discovery Source = "SG-SCCM". I am wondering if anyone has seen this and has suggestions on how to prevent the duplicates from being created when using the SG-SCCM integration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-26-2022 03:18 AM
Hi,
As for your comment "What is weird is that some servers that were moved to Retired status, are getting a new CI created by SG-SCCM. ".
Have you implemented an identification inclusion rule that excludes retired CIs? This is common configuration to allows for physical servers to be re-deployed with a different operating system.
Without the inclusion rule a windows machine re-used as a linux machine would just update the existing CI, regardless of status. But with an inclusion rule that excludes retired CIs it would leave the old one alone and create a new Linux CI.
More info here.