- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2018 07:57 PM
We have to discover VMware virtual appliance and VPx. There is no vCenter here. How can we do that?
Solved! Go to Solution.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2018 04:30 AM
But since the vmapp is triggering VMWare - vCenter Datacenters probe, would we still get the ESX and VM information?
- Yes, you will get the ESX and all the VM resources from VMWare probes.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2018 04:30 AM
But since the vmapp is triggering VMWare - vCenter Datacenters probe, would we still get the ESX and VM information?
- Yes, you will get the ESX and all the VM resources from VMWare probes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2018 10:50 PM
Thank you so much. Is this documented anywhere?
R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2019 11:24 AM
I am still baffled by this. My client has vcenter appliance. Shazzam detects port 22 and http port, but soon the discovery stops, with credential issues. We do have read only ID set up on the Vcenter, but the VMWare probes never get triggered since they need "command contains vpxd" from running process, which never happens since OS discovery is prevented.
So, how are we supposed to run discovery on these vcenter appliances?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2019 07:51 AM
Did you find a solution for this issue?
We're facing the same problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2019 07:03 AM
Hi jcanjura, Did you get a breakthrough on this ?