How can we enable Credential‑less Discovery only on selected CIs ?

[Pranita Bahugun]

Hello everyone,

We have enabled credential‑less discovery in our environment, but our intention is to run it only for specific CIs. At present, it’s executing across all CIs and generating unnecessary discoveries during scheduled runs. Could you advise how we can configure this to target only the intended CIs?

Thanks,

Pranita Bahuguni

[Vijaya_Mnpram]

@Pranita Bahugun  This can be done only if your desired CI's are under same sub-net/Host. As Serverless discovery uses reverse DNS, it will discover everything under that IP range. 

If there is difference between CI you want to discover and not-to discovery CI, then you can use that logic in the 'Credentialless Discovery Network Device' discovery pattern and achieve it. 

https://dev300861.service-now.com/sa_pattern_list.do?sysparm_query=nameLIKECredentialless&sysparm_vi...

[pavani_paluri]

Hi @Pranita Bahugun ,

In ServiceNow, credential‑less discovery will, by default, attempt to run across all CIs in the ranges defined in your discovery schedules. That’s why you’re seeing it execute everywhere.

To restrict it to only the intended CIs, you need to scope it explicitly:

Discovery schedules: Define separate schedules with specific IP ranges or CI filters for credential‑less discovery.
Discovery behavior rules: Configure rules so credential‑less probes only run for certain CI classes (e.g., printers, IoT devices) and are blocked for others.
Classification rules/patterns: Tailor probe activation conditions so only the CI types you want trigger credential‑less discovery.

This combination ensures credential‑less discovery doesn’t run globally but only where you intend.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P