With the Windows 2025 Server issue in Discovery, multiple Computer CIs have got created
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
With the Windows 2025 Server issue in Discovery, multiple Computer CIs have got created. We need to do a cleanup of all the Computer CIs and associate the existing relationships to the correct Windows 2025 Server CI before the cleanup.
What's the best way to do this, if de-dep tasks may have not been generated for all the these duplicates.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Do not delete the extra Computer CIs first. Fix classification, move relationships, then retire the dupes.
Windows 2025 is often landing in cmdb_ci_computer instead of cmdb_ci_win_server, so IRE creates a second CI instead of updating the server. Confirm that in the CI class manager / Discovery classification before you clean anything.
1. Find pairs by serial number, correlating_id, or name: one cmdb_ci_computer, one cmdb_ci_win_server (or two computers).
2. Pick the Windows Server CI as survivor.
3. Move relationships: query cmdb_rel_ci where parent or child is the Computer CI, set that end to the survivor sys_id, update. Same for related lists you care about (IP, NIC, serial number, running processes if they exist only on the dupe).
4. De-dupe tasks: Duplicate CI Remediator / reconcile duplicate tasks. If a task was never generated, you can create one from the Duplicate CI related link, or skip tasks and do the move+retire in a fix script after a backup export.
5. Retire or delete the extra Computer CI only after relationships are on the survivor. Deleting first orphans the rels.
6. Fix going forward: Windows 2025 OS classification so Discovery writes cmdb_ci_win_server, and check IRE identifier entries so serial/name coalesce instead of insert.
Test the script on 1 pair in subprod. Do not mass-delete from list view.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
We have already fixed the IRE issue of not correctly classifying the CIs as Windows. I am looking at the next step now for getting rid of the dupes and not losing the relationships, etc.
I am looking at a better mass update approach for Step 3 & 4 as you mentioned, because it would be difficult to go through each record and perform the necessary steps manually.
Assume other customers might have also run into this issue.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2008561
