Classifier Windows has been disabled, stopping discovery

Sanket Shinde2 · ‎07-15-2020

Hello All,

I have a couple of questions:

1. When I run discovery on a Windows device, I am getting an error as "Classifier Windows has been disabled, stopping discovery"

I have already checked all the Windows classifications and all of them are active, especially the Windows classifier.

What can be a possible reason for this?

2. If there is a Windows Server, which was created from Vcenter, then there is an entry in the CMDB from Vcenter discovery, with subcategory as VMWare Configuration and Class as VMWare Virtual Machine Instance, which is fine.

Assume,if I run a discovery on the IP (Windows server) and if we have a working credential available, then will there be an entry in the CMDB under Windows Servers?

Any help is appreciated.

Regards,

Sanket

Sanket Shinde2 · ‎08-14-2020

Hello,

There is a bug in configuration console for Servicenow instances.

It actually shows that a device class to discovery as enabled even when its disabled, if not modified for a long long time.

Here, you need to check a couple of things, which I did and it eventually resolved my issue.

Step 1:

Check the "disabled" column in the classification.It shouldn't be "disabled=true"

Step 2:

If disabled = true, then go to "Configuration Console" and check, due to the bug, it will show that its enabled,even if its disabled. So all you have to do is disable and enable the toggle 3-4 times and final value should be enabled and same should reflect in the classification table.

This will resolve your issue, as it did for me.

Regards,

Sanket

View solution in original post

Ashutosh Munot1 · ‎08-14-2020

Hi,

Is this reported by servicenow or to servicenow.

Thanks,
Ashutosh

Sanket Shinde2 · ‎08-17-2020

I have informed, but this would be a very rare case.

As in our instance, it was disabled for nearly 2 years and now when we tried enabling, it displayed as if its already enabled, thats why we did not toggle and thats where we went wrong, we should have tried toggling even when it was showing already enabled.

Jonah Piascik · ‎08-14-2020

Thanks Sanket. I checked both of those and they are set correctly. I think this had something to do with the additional CI Classification Criteria I was adding for Windows 2012 Server so I could exclude certain devices from being discovered based on hostname. I'm no longer receiving this message, but my devices are not being classified properly. I'm trying to use cidata.name in my classification, but am not having much luck. I have a ticket opened on HI as well.

Cinthya Reatig4 · ‎01-25-2021

This was absolutely helpful, thank you so much!