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.
Note: The vmapp port probe is also
configured to launch the VMware - vCenter Datacenters probe.
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
CIs removed from vCenter
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 CMDB Health Result [cmdb_health_result] table for the missing CI and marks the
- If the ServiceNow 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.
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