- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-27-2023 08:25 AM
In our environment we have 2 separate SCCM Databases for our 2 different Active Directory Domains. For about a year we had only one of the SCCM instances integrated into ServiceNow. About 2 weeks ago we added the second one and we are now noticing that some of our CIs are being overridden with the information from the other SCCM instance. My guess is something to do with the CorrelationID being a duplicate ID and so both SCCM Instances are fighting over updating the CI record with information. I was wondering if anyone knows of a similar issue or a way I can confirm that the CorrelationID are duplicates.
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2023 06:10 AM
The problem was that there wasn't a second connection set up. Consequently, both SCCMs had duplicate resource IDs. This KB article addresses the issue we were experiencing.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1001248
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-31-2023 04:05 AM
We get problems when people are cloning servers and renaming them. This somehow messes with the unique keys used by SCCM, and thus also confusing the CMDB. I have not been able to find a solution to this yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2023 06:10 AM
The problem was that there wasn't a second connection set up. Consequently, both SCCMs had duplicate resource IDs. This KB article addresses the issue we were experiencing.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1001248
