- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2024 06:48 AM
Hi,
In one of my discovery schedule i have applied behavior. when i am running the job the getting error for few devices but when i try quick discovery then device is getting discovered without an error.
What could be the possible reason.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2024 11:55 PM
Hi @MK-p,
If you are running schedule which has behavior configured then check below checklist.
1. Behavior should have at least one "Discovery functionality".
2. In which phase your behavior should apply.
3. Select proper "functionality definition".
4. For example : if you want to apply only windows credentials then make sure to select port probes only related to windows.
5. Check all for points if all well setup then it wont give any error.
Quick discovery are free to check all the credentials but using behavior it will only check based on defined port probes.
-------------------------------------------------------------------------
If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.
Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay
-------------------------------------------------------------------------

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2024 06:54 AM
Quick discovery doesn't use a behaviour. So you'd need to look into what the error is and update your behaviour if you want that particular functionality to occur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2024 11:46 AM
Here’s a summary of the configuration validation to help mitigate the error :
-
MID Server Selection: Please ensure that the selected MID Server has the appropriate capabilities enabled to trigger and complete the discovery process for the target system. This includes checking that it meets all necessary prerequisites and has access to the required resources.
-
Discovery Functionality: It’s crucial to verify that the discovery functionalities assigned to each MID Server are configured correctly. This includes confirming that the MID Server is set up to detect the intended protocols, such as WMI, SSH, and SNMP.
If these configurations are accurate, the MID Server should function as expected during the discovery phase.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2024 11:55 PM
Hi @MK-p,
If you are running schedule which has behavior configured then check below checklist.
1. Behavior should have at least one "Discovery functionality".
2. In which phase your behavior should apply.
3. Select proper "functionality definition".
4. For example : if you want to apply only windows credentials then make sure to select port probes only related to windows.
5. Check all for points if all well setup then it wont give any error.
Quick discovery are free to check all the credentials but using behavior it will only check based on defined port probes.
-------------------------------------------------------------------------
If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.
Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay
-------------------------------------------------------------------------