- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2017 02:45 PM
I want to populate the CMDB with VMs from vCenter, I just want to pull the VMs I don't need to procure VMs yet.
After reading the Wiki, I still don't know if at all SerivceNow Discovery and/or Orchestration is required to be enabled in order to just pull VMs.
I see that there is a related link "Discover vCenter Details" as per Wiki, does it means that it is actual Discovery feature running with a MID Server in order to "discover" the VMs?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2017 10:36 PM
Hi Oscar,
That's right. ServiceNow uses Discovery to discover the different VMs by interacting with VMWare VCenter.
As the documentation states:
Discovery can explore the VMware vCenter process running on a Windows or Linux host.
ServiceNow Discovery supports these vCenter versions:
- vCenter versions 6.0 and earlier
- vSphere version 5.5
- vCenter appliance version 6.0 and earlier
See vCenter data collected for a description of the VMware architecture and component relationships.
When Discovery runs, a classifier called vCenter classifies the process running on a Windows or Linux machine.
Discovering vCenter CIs
After classifying vCenter, Discovery launches the VMware - vCenter Datacenters probe, which in turn launches specific probes that return information about ESX machines, virtual machines, and other vCenter objects.
If you use a domain account to access vCenter, specify the domain with the user name in the credential record in one of the supported formats such as Domain\UserName.
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2017 10:36 PM
Hi Oscar,
That's right. ServiceNow uses Discovery to discover the different VMs by interacting with VMWare VCenter.
As the documentation states:
Discovery can explore the VMware vCenter process running on a Windows or Linux host.
ServiceNow Discovery supports these vCenter versions:
- vCenter versions 6.0 and earlier
- vSphere version 5.5
- vCenter appliance version 6.0 and earlier
See vCenter data collected for a description of the VMware architecture and component relationships.
When Discovery runs, a classifier called vCenter classifies the process running on a Windows or Linux machine.
Discovering vCenter CIs
After classifying vCenter, Discovery launches the VMware - vCenter Datacenters probe, which in turn launches specific probes that return information about ESX machines, virtual machines, and other vCenter objects.
If you use a domain account to access vCenter, specify the domain with the user name in the credential record in one of the supported formats such as Domain\UserName.
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2017 10:38 PM
Here goes the links to the documentation. Please go through all of it. It will greatly expand your understanding of how discovery actually discovers VMWare WMs through VCenter.
I hope this helps and answers your question
Greetings!
Thanks,
Berny

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-14-2019 09:47 AM
is this the usual ip based discovery or is this more like a service account based discovery like in azure?
i am finding it hard time finding documents to to actually configure the discovery.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2017 01:33 PM
Hello Oscar,
I've developed a REST integration with vCenter 6.5 in order to populate the CMDB with VM's without the need to purchase Discovery or Orchestration. If you are interested please contact me adrian.herdan@gmail.com
Regards,
Adrian