CIs reverting to cmdb_ci_computer due to Discovery classification
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
We are observing that certain CIs are consistently reverting back to the cmdb_ci_computer class after Discovery runs.
- These records were previously classified under other classes (should be classed as Windows or Linux servers - depending on the operating system)
- After Discovery executes (via MID Server), they are reclassified back to cmdb_ci_computer
- The reclassification appears to be driven by the Windows – Classify pattern
- Affected devices are running Windows 11
We understand that modifying OOB patterns is generally not advisable. So, what is the best practice to handle this situation?
0 REPLIES 0
