Reclassify Computer as Windows sever based on processor name

[MiguelSL]

Hello everyone,

We have some Windows 10 CIs running on actual servers. We want Discovery to recognize them as servers and not as computers. The criteria we want to use is that if the processor is Xeon, it doesn't matter if the OS is Windows 10, it should be discovered as a Windows server.

First I considered a business rule, but discarded the idea since I believe it is not the right approach.

After additional research, I found THIS info on how to reclassify a Windows CI, and I believe this is the right way to go, but I haven't been able to make it work using the processor as the classification criteria. Is it possible to accomplish this with Windows classifications? Is there an alternative I can use?

Thanks in advance!

[maheshkhatal]

@MiguelSL  Make sure if you have OOB classifier classifying them as  Computers then de-activate them. See the classification probes when it classifies the CI as computers. Instead you  have to make sure it launches your probe that correctly identifies those CIs as Servers. Re-run quick discovery and make sure it classifies those CIs as Servers.

Mark my response as helpful if it helped you.

Thanks,

Mahesh.

[MiguelSL]

But if I do that, wouldn't that affect all CIs, even when they are actual computers? I just want Discovery to reclassify them when both conditions are met: Processor == 'Xeon' && OS contains 'Windows 10'.

I just noticed that the processor info is not available prior to the classification phase so I'm not sure anymore if this is the way forward!

[kaushal_snow]

@MiguelSL ,

Discovery classifies devices based on CI classification rules configured under Discovery Definition > CI Classification > Windows and....by default windows 10 os gets classified as a computer, so if you want discovery to treat a windows 10 machine as a windows server based on processor type such as Xeon, you would need to create or modify a custom ci classification rule that checks your specific criteria and assigns the cmdb_ci_win_server table when conditions are met......because discovery runs classifications in sequence and you must ensure your custom rule runs before the oob Windows workstation classifier and triggers the correct classification and probes, but be aware that processor info might not be available at the classification phase which could limit how effective this approach is unless you adjust the order of probes or use attributes that are captured early in the discovery process......

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.