--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/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 vCenter # Discovery for VMware vCenter {#ariaid-title1} * Release version: Yokohama * * Updated December 2, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Discovery for VMware vCenter Discovery for VMware vCenter enables the ServiceNow platform to explore and collect detailed information about VMware vCenter environments running on Windows or Linux hosts, including support for IPv6. It identifies vCenter instances, their associated ESX hosts, virtual machines, datastores, and other components, creating configuration items (CIs) and mapping relationships within the CMDB. This discovery supports vCenter API versions 4.0 and above, with specific testing on vCenter versions up to 8.0 and vCenter appliance versions up to 6.7. Show full answer Show less ## Key Features * **Comprehensive Discovery:** Automatically classifies vCenter servers and launches probes to gather detailed data on datacenters, ESX hosts, virtual machines, and datastores. * **Relationship Mapping:** Creates accurate "Runs on" relationships between vCenter application CIs and their underlying Windows or Linux server hosts, enhancing infrastructure visibility. Note that this relationship is not created when vCenter runs on a dedicated appliance. * **Credentials Management:** Supports VMware credentials with read-only roles; for Software Asset Management, credentials need the "Assign license" privilege. Windows credentials are not required if valid VMware credentials are provided. * **Event-Driven CMDB Updates:** Integrates with the vCenter event collector MID Server extension to update the CMDB in near real-time based on vCenter events, reducing the need for full rediscovery. * **Handling of Removed or Deleted CIs:** Marks virtual machines deleted in vCenter as terminated and retired. CIs removed from vCenter are marked stale in the CMDB, with options to automate remediation workflows for stale data management. * **Configuration Flexibility:** Allows specifying alternate ports for vCenter probes and supports discovery of SUSE Linux hosts with SSH restrictions when applicable. ## Practical Guidance for ServiceNow Customers * Run vCenter discovery before discovering server CIs to ensure correct server-to-vCenter resource relationships. * Use properly formatted domain credentials (e.g., Domain\\UserName or username@domain) with appropriate privileges to enable thorough and compliant discovery. * Leverage the vCenter event collector to keep the CMDB updated with virtual machine state changes efficiently, minimizing full discovery runs. * Configure stale CI policies and remediation workflows to maintain CMDB health and accuracy, particularly when vCenter resources are removed. * Review system properties such as `glide.cmdb.health.src.cmdbhealthauditonly` to control stale CI reporting behavior according to your lifecycle management strategy. ## Expected Outcomes By implementing VMware vCenter discovery, customers gain accurate visibility into their virtual infrastructure, including detailed component relationships and lifecycle status. This enables improved asset management, operational efficiency, and effective integration with Software Asset Management processes. The event-driven updates ensure the CMDB remains current with minimal overhead, supporting proactive IT service management and infrastructure planning. Discovery can explore the VMware vCenter process running on a Windows or Linux host. IPv6 is supported for discovery in VMware vCenter. Note: If a Windows or Linux server is running vCenter application, after creating the vCenter CI, a "Runs on" relationship to the Windows or Linux server host is created. When a vCenter application is running on a dedicated vCenter appliance, a "Runs on" relationship to the vCenter CI isn't created. ## Tested vCenter versions {#c_DiscoveryForVMwareVCenter__section_kht_qrw_xcb} The ServiceNow® platform supports vCenter API versions 4.0 and higher. The following versions were tested with the Yokohama release: * vCenter versions 8.0 and earlier * vCenter appliance version 6.7 and earlier {#c_DiscoveryForVMwareVCenter__ul_uxh_m2m_qr} For installations based on the vCenter appliance, a server CI is created for the vCenter appliance and the following fields are populated: * NameIP * AddressMAC * AddressDiscovery * Source {#c_DiscoveryForVMwareVCenter__ul_vnr_ldh_ttb} Note: If you're discovering SUSE Linux hosts for vCenter appliances, version 6.0 and earlier, observe these [SSH restrictions](https://kb.vmware.com/s/article/2100508). See [Data collected for VMware vCenter Server](https://www.servicenow.com/docs/xRW8Cn8s96sW5~39xtZ8HA "Discovery identifies and classifies information and data about VMware vCenter servers.") for a description of the VMware architecture and component relationships. ## vCenter discovery process {#c_DiscoveryForVMwareVCenter__section_pbc_4wc_h1b} 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. The vmapp port probe is also configured to launch the VMware - vCenter Datacenters probe. Note: For accurate relationship mapping between server CIs and vCenter resources (such as ESX hosts and datastores), you should initiate discovery of the vCenter environment before discovering Server CIs. This approach helps Discovery associate servers with their corresponding vCenter-managed infrastructure more effectively. ## VMWare credentials {#c_DiscoveryForVMwareVCenter__section_art_1y3_xdb} To access vCenter with a domain account, specify the domain with the user name in the credential record using a supported format, such as Domain\\UserName or username@domain. The VMware credentials must have a read-only role in vCenter. For Software Asset Management (SAM) tracking, the credentials also require the "Assign license" privilege in vCenter, also known as the License Admin privilege. Important: Windows credentials aren't necessary for vCenter Discovery when valid [VMware credentials](https://www.servicenow.com/docs/access?context=r_VMwareCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) are used. ## Updating the CMDB with vCenter event collector {#c_DiscoveryForVMwareVCenter__section_k1c_4wc_h1b} In addition to finding vCenter data through the standard discovery process, Discovery can also update the CMDB by detecting vCenter events through a MID Server extension called the [vCenter event collector](https://www.servicenow.com/docs/access?context=c_VCenterEventProcessorExtension&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). The event collector allows the CMDB to be updated with changes to virtual machines (VMs), in addition to the updates detected by Discovery. A change to a VM is sent as an event from the vCenter server to the vCenter event collector. When an event is received, the CMDB is updated accordingly. Full vCenter Discovery does not need to rerun. For some events, such as powered on and powered off events, Discovery does not need to run again at all. For most events, Discovery runs only on the necessary vCenter resource. For instructions on configuring vCenter events, see [Configure and run the vCenter event collector extension](https://www.servicenow.com/docs/access?context=c_VCenterEventProcessorExtension&version=yokohama&pubname=yokohama-servicenow-platform§ion=t_ConfigVCenEvntProcExt&ft:locale=en-US). ## VM deleted from vCenter {#c_DiscoveryForVMwareVCenter__section_n3s_vw5_3mb} If the VM is deleted from vCenter, the cmdb_ci_vm_instance state changes to terminated and the Status field changes to retired. ## CIs removed from vCenter {#c_DiscoveryForVMwareVCenter__section_syb_4wc_h1b} When a vCenter CI, such as a virtual machine, is removed, the ServiceNow instance marks it as "stale" in the CMDB, using either of these procedures: * When Discovery runs, it creates an audit record in the [Components installed with CMDB Health](https://www.servicenow.com/docs/access?context=r_TablesInstalledCMDBHealth&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) table for the missing CI and marks the CI "stale". * If the instance is configured to collect vCenter events, the system can also create a "stale" audit record for the CI in the CMDB Health Result \[cmdb_health_result\] table from the VmRemovedEvent event, without having to run Discovery. {#c_DiscoveryForVMwareVCenter__ul_edc_nww_fv} Note: When the Staleness setting is configured, the dependency view (BSM map) grays out stale CIs in its relationship diagram to indicate that they were removed from vCenter. To avoid stale CI health indicators from being generated during VMware discovery, set the system property glide.cmdb.health.src.cmdb_health_audit_only to true. This disables stale CI reporting from the VMware discovery source, enabling you to manage the CI life cycle through other means. For more information, see [CMDB Health system properties](https://www.servicenow.com/docs/access?context=r_CMDBHealthProperties&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). You have the option of creating a [CMDB remediation rule](https://www.servicenow.com/docs/access?context=t_CreateCMDBRemediationRule&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) to automatically execute a remediation workflow that can, for example, delete stale CIs. For more information on stale CIs, see [CMDB Health Metrics](https://www.servicenow.com/docs/access?context=r_CMDBHealthMetrics&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US). ## vCenter Discovery on Windows host {#c_DiscoveryForVMwareVCenter__section_jvx_kpz_rz} Windows credentials aren't necessary for vCenter Discovery, when valid VMware credentials are used. * **[Configure an alternate port for vCenter](https://www.servicenow.com/docs/piDDE1AjMmKW6ImqO7zZfQ)** You can specify an alternate port for the VMware - vCenter Datacenters probe. * **[Data collected for VMware vCenter Server](https://www.servicenow.com/docs/xRW8Cn8s96sW5~39xtZ8HA)** Discovery identifies and classifies information and data about VMware vCenter servers. * **[Datastore data collected by Discovery](https://www.servicenow.com/docs/NnJSFjshExrefPBeT1V3vQ)** Discovery identifies each datastore in the system and creates the relationships with the virtual machines and the ESX servers that use these datastores. **Related concepts** * [Discovery for VMware virtual machines](https://www.servicenow.com/docs/EzspSMqJ6LoEIJ4S_TWVUg "Discovery gathers information about virtual machines managed by VMware vCenter.") * [Datastore Discovery](https://www.servicenow.com/docs/qZQPEZ7tqukOEwKBi2XMQw "A datastore is a storage object for virtual machines that are hosted on an ESXi server.") **Related reference** * [ESXi server discovery](https://www.servicenow.com/docs/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://www.servicenow.com/docs/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.") * [VM instance state and status fields](https://www.servicenow.com/docs/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.")