- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2018 09:02 AM
Hi Everyone 🙂
I currently have a MID server running on an EC2 Linux instance. It is on a subnet with another dummy EC2 instance for it to discover. I think I have everything properly set up now. The ServiceNow instance seems to be able to detect the dummy EC2 instance through Quick Discover, but I am getting some weird logs. Wondering if anyone knows how to fix these issues.
Thanks in advance.
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2018 09:32 AM
Hi -- I think your setup is a basic, traditional SN Discovery... The mention of EC2 and AWS is generating some responses about cloud-stuff that I don't think applies in your scenario. Since I think you are doing traditional (non-cloud) discovery, it looks like your errors is more basic... i.e. is your MID server installed on Linux? Are you trying to discover a Windows based machine? If so, this wont work...
per error:... it implies your MID is Linux based... if so, and you need to discover a WINDOWS machine, this won't work. To discovery WINDOWS based target devices, you need to use a Windows-based MID server.
Does this help? Hope so
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2018 09:23 AM
Hi Dave!
So, if my subnet is a mixture of windows and linux EC2 instances, I would need to have two MID servers? One on a linux EC2 and one on a Windows EC2?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2018 09:33 AM
You could just have a Windows MID server because this can discover Linux and Windows. Almost all MID server used for discovery are usually installed on Windows for this reason.
Only the Linux MID server has the limitation of not being able to discover Windows.
Regards,
Dave

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2018 09:40 AM
No, a Windows based MID server can do it all. But the inverse is not true, i.e. a Linux-based MID can't discovery Windows. For this reason, its very, very common for MIDs to be installed on Windows based machines... which empower flexibility. i.e. a Windows based MID can discovery Linux, network, etc... via SSH, SNMP, WMI, etc.
The linux-based MID doesn't "speak" WMI, so therefore Linux MID's can't discovery Windows.
Hope this helps?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2018 09:32 AM
Hi -- I think your setup is a basic, traditional SN Discovery... The mention of EC2 and AWS is generating some responses about cloud-stuff that I don't think applies in your scenario. Since I think you are doing traditional (non-cloud) discovery, it looks like your errors is more basic... i.e. is your MID server installed on Linux? Are you trying to discover a Windows based machine? If so, this wont work...
per error:... it implies your MID is Linux based... if so, and you need to discover a WINDOWS machine, this won't work. To discovery WINDOWS based target devices, you need to use a Windows-based MID server.
Does this help? Hope so
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2020 12:57 AM
Check out this video, it will clear all your doubts and help you to understand Cloud Discovery queries in details.
Link: https://www.youtube.com/watch?v=GWAvGbnCmlQ&ab_channel=ServiceNowHelpdesk
It help you to understand below points.
- Cloud Discovery
- Cloud Service Mapping vs Discovery
- Steps by step setup
- Practice with real world scenario
- Troubleshooting
- CI Class Tables and Attributes
- Amazon AWS Cloud Discovery Step by Step Configuration
- Azure Cloud Discovery Step by Step Configuration
Please mark reply as Helpful/Correct, if applicable. Thanks!!