
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-05-2021 11:02 AM
When I run a Discovery Schedule, "Alive, not active, not classified" Devices appear in the Discovery Results whether "Include Alive" is checked or not. How can I remove the "Alive, not active, not classified" Devices from the Discovery results?
Background
I setup a Discovery Schedule. I check "Include Alive".
I then run the Schedule.
In the Shazzam results, five IP addresses are found to be "active=false" and "alive=true". Only one of the five is shown in the screenshot below, but all five are listed in the Shazzam log.
- 10.2.133.2
- 10.2.133.106
- 10.2.133.109
- 10.2.133.110
- 10.2.133.112
As expected, these five IP addresses appear in the Discovery results as Devices "Alive, not active, not classified"
I return to the same Discovery Schedule. I uncheck "Include Alive", then Save the changes.
I then run the same Schedule with "Include alive" not checked. The same five IP addresses appear in the Discovery results as Devices "Alive, not active, not classified". This is not expected. Should the Discovery results omit all Devices that are "Alive not active not classified"?
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-20-2021 09:24 AM
ServiceNow Development says the "Include Alive" checkbox is no longer supported.
This is from CS5288030 'The Checkbox "Include Alive" In Discovery Schedules Does Not Work'.
The "Include Alive" checkbox is no longer supported.
It was removed in London release as part of 'PRB1250860' but documentation was not updated. Dev team will work on the documentation.
Also refer to PRB1250860 'Remove include alive from discovery schedule form and add completed activity "alive, not classified"'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-03-2021 12:20 AM
PRB1250860 now resolves back to this post. this appears to be all the information available on this error.