---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discovery for VMware vCenter

# Discovery for VMware vCenter {#ariaid-title1}

Release version: Brazil  
Updated November 17, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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

ServiceNow Discovery for VMware vCenter enables automated exploration and identification of vCenter environments running on Windows or Linux hosts, including support for IPv6.
It creates configuration items (CIs) representing vCenter components and their relationships, helping maintain an accurate and updated CMDB.
The discovery process supports vCenter API versions 4.0 and higher and has been tested with vCenter versions up to 9.0 and vCenter appliances up to version 6.7.
Show full answer Show less  

## Key Features

* **Discovery Process:** Discovery classifies vCenter and launches specific probes to gather detailed information about datacenters, ESX hosts, virtual machines, and other components.
* **Relationship Mapping:** When vCenter runs on Windows or Linux servers, Discovery creates "Runs on" relationships linking vCenter CIs to their host servers. This relationship is not created if vCenter runs on a dedicated appliance.
* **Credential Requirements:** VMware credentials with read-only access are necessary for discovery; for Software Asset Management, credentials must include the "Assign license" privilege. Windows credentials are not required when valid VMware credentials are used.
* **Event Collector Extension:** The vCenter event collector MID Server extension detects vCenter VM events and updates the CMDB in near real-time without requiring full rediscovery. It handles VM lifecycle changes such as power state and removal events.
* **Handling Deleted or Removed CIs:** When VMs or other vCenter CIs are removed, Discovery or the event collector marks them as "stale" in the CMDB and updates relevant status fields to reflect termination or retirement.
* **CMDB Health Integration:** Stale CIs are visually indicated in dependency maps (BSM) and can be managed via CMDB remediation rules to maintain CMDB accuracy.
* **Configuration Options:** Customers can prevent automatic creation of stale CI records during discovery by setting a system property to restrict stale audits to CMDB Health only.

## Practical Benefits

* Accurate discovery and mapping of VMware infrastructure components and their relationships improve CMDB completeness and reliability.
* Near real-time updates of VM status and changes reduce the need for frequent full rediscoveries, optimizing network and system resource usage.
* Integration with CMDB Health Metrics facilitates proactive CMDB maintenance by identifying and managing stale CIs.
* Support for multiple vCenter versions and platforms ensures compatibility with a broad range of VMware environments.

## Recommendations for ServiceNow Customers

* Initiate vCenter discovery before discovering individual server CIs to ensure accurate relationship mapping between servers and vCenter-managed infrastructure.
* Use VMware credentials with appropriate privileges to enable full discovery and Software Asset Management capabilities.
* Leverage the vCenter event collector extension to maintain up-to-date CMDB records with minimal discovery overhead.
* Configure system properties and remediation rules according to organizational CMDB management policies to control stale CI handling.  
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 Brazil release:

* vCenter versions 9.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 Cloud Discovery](https://www.servicenow.com/docs/lMGu59uBRa1gAeJ6MUnEXg "Discovery collects information about VMware resources in your cloud service accounts.") 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=brazil&pubname=brazil-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=brazil&pubname=brazil-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=brazil&pubname=brazil-servicenow-platform&section=t_ConfigVCenEvntProcExt&ft:locale=en-US).

## VMs deleted from vCenter {#c_DiscoveryForVMwareVCenter__section_n3s_vw5_3mb}

When a VM is deleted from vCenter, the ServiceNow instance updates the VM's record in the VM Instance \[cmdb_ci_vm_instance\] table. The field changes depend on whether the update comes from Discovery or from the vCenter event collector:

* vCenter Discovery sets State to Terminated, Install Status to Retired, and Operational status to Non-operational for every VM that's no longer in vCenter.
* The vCenter event collector sets State to Terminated and Install Status to Retired when it receives a VmRemovedEvent event. It doesn't change Operational status. The event collector doesn't save these changes in the following cases:
  * The VM is already marked stale in CMDB Health.
  * The VM's State is already Terminated or is empty.

## 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=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US) table for the missing CI and marks the CI "stale". It also updates the CI fields every time, as described in [VMs deleted from vCenter](https://www.servicenow.com/docs/NjxH1Bz_Y6GHPtdISN_3rA#c_DiscoveryForVMwareVCenter__section_n3s_vw5_3mb).
* When 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. This record is created from the VmRemovedEvent event, without having to run Discovery. The event collector handles these cases differently:
  * The CI is already marked stale: The event collector skips the event. It doesn't create another stale record or update the CI fields.
  * The VM's State is already Terminated or empty: The event collector creates the stale record but doesn't save the CI field changes.

{#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 prevent stale CI records from being created during VMware discovery, set the system property glide.cmdb.health.src.cmdb_health_audit_only to true. When this property is true, only CMDB
Health audits create records in the CMDB Health Result \[cmdb_health_result\] table. Records from the Cloud Discovery source, which includes vCenter Discovery and the vCenter event collector, aren't created. Discovery and the event collector still update the CI fields, as described in [VMs deleted from vCenter](https://www.servicenow.com/docs/NjxH1Bz_Y6GHPtdISN_3rA#c_DiscoveryForVMwareVCenter__section_n3s_vw5_3mb). For more information, see [CMDB Health system properties](https://www.servicenow.com/docs/access?context=r_CMDBHealthProperties&version=brazil&pubname=brazil-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=brazil&pubname=brazil-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=brazil&pubname=brazil-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.

