What is the setting in the CI so Discovery doesn't scan it? I've added a screen shot of the field that has to have an opt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2022 02:41 PM
There are like 15 options in the Discovery Source box. What option should be selected if I do not want Discovery to scan an asset?
thanks
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2022 03:12 PM
Hi -- the Discovery Source field is not what you are looking for. This field only shows WHERE the CI came from, but does not control if the CI is scanned via disco or not.
To stop a CI from being scanned by Discovery, the disco job/ecosystem must be informed not to scan the CI, which can be done via a few ways:
- Dont' include the IP of the CI in the discovery scope/range for schedules
- Blacklist the IP from an existing range/set. This is effectively the same as the prior point, just a different approach
- don't include the credential for the CI in Discovery's scope. Or if there is a enterprise cred that is used for all machines remove that cred from this CI. the point being to block disco from having required access
Bottom line: If a device's IP is in scope for a discovery schedule and valid credentials exist to scan it, and the disco MID servers can reach the device, it'll generally get discovered.
Hope this helps?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2022 07:16 PM
+1 twice over to what Dave says but you might also look at the IRE to set data precedence rules on devices in the CMDB that should or should not be updated by a particular discovery source
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2022 04:13 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2022 04:52 PM
No, that will be worthless and it'll likely just get overwritten next time Discovery runs.
Same answer as before - if you want to stop the CI from being discovered, the setup of Disco (IP, schedule, credential, etc.) needs to change
The Discovery source field has NOTHING to do with controlling IF a CI get discovered or not. that field just reports where the data came from.