---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discovery for VMware virtualization

# Discovery for VMware virtualization {#ariaid-title1}

* Release version: Yokohama
* 
* Updated December 2, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

A Discovery schedule for VMware virtualization can discover vCenter and ESX hosts as well as individual ESXi hosts that manage VMs and related components without a vCenter.  
These options are available for getting VMware vCenter data:

* Discovery runs the [VMware - vCenter Datacenters](https://servicenow-prod.fluidtopics.net/F4fPHL_pRcSyOUcSLoqUPA "A wide variety of probes exist for the Discovery application to detect elements on your network.") probe when it identifies a VMware vCenter process running on a Windows machine or detects activity with the vmapp port probe.
* [Classic Orchestration](https://www.servicenow.com/docs/access?context=r-orchestration&version=yokohama&pubname=yokohama-integrate-applications&ft:locale=en-US) can run any of the vCenter probes from a workflow
{#c_DiscoverVMwareInfrastructure__ul_psw_2dy_5p}

To discover VMware data without a vCenter, use standalone ESXi discovery.  
Note:  
See the knowledge article [KB0687582](https://support.servicenow.com/kb_view.do?sysparm_article=KB0687582) for information on model_id and manufacturer.
* **[Discovery for VMware vCenter](https://servicenow-prod.fluidtopics.net/S4sT9mXn~Jvl1GsT0myOfA)**   
  Discovery can explore the VMware vCenter process running on a Windows or Linux host. IPv6 is supported for discovery in VMware vCenter.
* **[ESXi server discovery](https://servicenow-prod.fluidtopics.net/69HIi_wE1an9UMq2Y8I74Q)**   
  Discovery identifies and classifies information about ESXi servers and ESXi resource pools through the discovery of vCenter and not from the direct discovery of any ESXi servers.
* **[Standalone ESXi discovery](https://servicenow-prod.fluidtopics.net/kfJMNZe2fFanLSf9yr4AMg)**   
  Standalone ESXi discovery supports discovery of individual ESXi servers that host virtual machines (VMs) and related components without a vCenter. Various CIs and relationships are discovered as part of a discovery schedule.
* **[Discovery for VMware virtual machines](https://servicenow-prod.fluidtopics.net/EzspSMqJ6LoEIJ4S_TWVUg)**   
  Discovery gathers information about virtual machines managed by VMware vCenter.
* **[VM instance state and status fields](https://servicenow-prod.fluidtopics.net/U0dPtfhL_EEGPhbGQgTPJQ)**   
  These tables represent the state and status of the cmdb_ci_vm_instance in various flows such as vCenter Discovery and vCenter Events and the Business Rules which are triggered.
* **[Datastore Discovery](https://servicenow-prod.fluidtopics.net/qZQPEZ7tqukOEwKBi2XMQw)**   
  A datastore is a storage object for virtual machines that are hosted on an ESXi server.

