CIs reverting to cmdb_ci_computer due to Discovery classification

[MichelleS384771]

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?

[vaishali231 · Accepted solution]

Hey @MichelleS384771 

This behavior is usually seen when Discovery cannot confidently identify the device as a more specific subclass during the classification phase, causing it to fall back to the parent class:

cmdb_ci_computer

A few things to validate before making any customization:

Windows 11 is considered a client OS, not a server OS

OOB Discovery patterns typically classify Windows 11 devices under:

cmdb_ci_computer

cmdb_ci_win_server is intended for Windows Server operating systems such as:

1. Windows Server 2016
2. Windows Server 2019
3. Windows Server 2022

So first confirm whether these devices are actually:

Windows 11 workstations/endpoints (expected OOB behavior)
OR

systems that genuinely need to be treated as server-class CIs

Recommended Best Practice

Review Discovery Logs and Pattern Debug

Check:

1. WMI responses
2. OS attributes returned during classification
3. Discovery Pattern logs
4. Identification/Reconciliation activity

Also verify values such as:

Win32_OperatingSystem.ProductType

Typical values:

   1 = Workstation

   2 = Domain Controller

   3 = Server

If Discovery detects:

ProductType = 1

the CI will normally be classified as:

cmdb_ci_computer

Avoid Modifying the OOB “Windows – Classify” Pattern

Direct modification of OOB patterns is not recommended because:

1. Upgrades may overwrite changes
2. Future maintenance becomes difficult
3. Troubleshooting becomes more complex

Use Pattern Extension or Custom Classification Logic

If custom behavior is required:

   Create a Pattern Extension
      OR

   Create a custom Classification Rule

This is the recommended upgrade-safe approach.

You can then:

1. Add logic specific to your Windows 11 devices
2. Preserve the required subclassification
3. Control reclassification behavior more safely

Verify Other Discovery/Integration Sources

Also confirm whether another source is updating the CI class through IRE, for example:

• SCCM
• Intune
• Tanium
• JAMF
• Third-party discovery tools

Another source with higher precedence could also be reverting the CI class back to:

cmdb_ci_compute

****************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh

Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb

[vaishali231]

Hey @MichelleS384771 

Hope you are doing well.

Did my previous reply answer your question?

If it was helpful, please mark it as correct ✓ and close the thread . This will help other readers find the solution more easily.

Thankyou & Regards

Vaishali Singh

Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb