Hypervisor discovery identifies guest virtual machines through supported virtualization management platforms. The platforms shown are:
VMware vCenter
XenServer / Citrix Hypervisor
Nutanix Prism
Use this job type to discover virtual machines from the virtualization platform’s perspective. This complements Network discovery, which connects to a guest operating system through protocols such as WMI or SSH.
Example: A virtualization administrator creates a Hypervisor discovery job for VMware vCenter to identify guest virtual machines. Network discovery can then collect operating system information from reachable guests using suitable credentials.
To create a new job for Hypervisor devices, perform the following steps:
Click Workspace > ITAM > Asset > Discovery > Discovery Jobs.
The Discovery Jobs list page is displayed.Click New Job.
On New Job, select the job type that matches your discovery source.
Figure: New JobJob type
Purpose shown on the selection screen
Network
Discover Windows through WMI, Linux through SSH, and network devices through SNMP.
Cloud
Enumerate virtual machines and resources across AWS, Azure, GCP, and Oracle Cloud.
Container
Discover Docker containers and Kubernetes resources.
Hypervisor
Discover guest VMs through virtualization platforms.
Database
Connect to database engines to discover instances and inventory.
Directory
Discover Active Directory information without an agent.
Storage / SAN
Discover storage systems through supported platform interfaces.
Select Hypervisor on the new job.
On Identity, select the tenant and enter a descriptive job name.

Figure: IdentityField name
Description
Tenant *
Tenant context associated with the job. The demonstration displays Information Technology.
Job Name *
Name used to identify the job in the jobs list and run details. Example: HQ Windows Inventory.
Status
Activation state selected for the job. The demonstration shows Active.
Description (optional)
Purpose, scope notes, ownership, or other context for the team.
Next
Continues to the next wizard stage.
Cancel
Leaves the wizard. Confirm any save or discard behavior presented by the application.
Click Next to open Scope.
On Scope & Exclusions, choose the scope type.
Enter the corresponding addresses. For a subnet scan, enter its CIDR block.
Add addresses, ranges, CIDRs, or hosts to exclude, one entry per line where the control is available.
Review the target boundaries and click Next.
For a branch subnet, select CIDR Subnet and enter 192.168.50.0/24. Exclude any management or sensitive targets that the network team has removed from the approved scan list. First test the worker and credentials against one representative host.Configure an address range.
Select IP Range (start - end).
Enter Start IP and End IP, for example 192.168.50.10 and 192.168.50.40.
Review any exclusions, and continue to Type.
Configure a host list.
Select IP List (multiple).
Enter the approved addresses or hostnames, one per line or separated by commas.
Check spelling, DNS resolution where applicable, and the completeness of the list.
Click Next.
Use a single host during initial validation. Expand to a list, range, or subnet only after checking that the selected worker can collect the expected data.
Figure: CIDR Scope and exclusionsField name
Description
Scope Type
Selects Single Host / IP, IP Range (start - end), CIDR Subnet, or IP List (multiple).
CIDR Block *
Subnet address and prefix for CIDR Subnet. Example: 192.168.50.0/24. Confirm the resulting range before scanning.
Start IP * / End IP *
Beginning and ending addresses for IP Range (start - end).
Exclude IPs / ranges / CIDRs / hosts (one per line)
Targets to skip within the scan scope. The UI states that excluded targets are never probed, even when they fall inside the scope.
On Type & Credentials, select the applicable Hypervisor type: VMware, Xen/Citrix, or Nutanix. You can also more than 1 types.
For each selected method, add a stored credential. Use quick creation if a suitable credential is not yet available.
Use the up and down controls to arrange the displayed execution order.
Review the methods and selected credentials, then click Next.

Figure: Protocol execution order and credentialsField or control
Description
VMware
A virtualization platform that enables discovery of guest virtual machines through vCenter.
Xen/Citrix
A virtualization platform that enables discovery of guest virtual machines through XenServer or Citrix Hypervisor.
Nutanix
An infrastructure platform that enables discovery of guest virtual machines through Prism.
Create Nutanix Credential
Enter the credential name, username, password, and port.
Click Create & Add. Confirm that the credential appears under Nutanix.

Figure: Create Nutanix credentialField or control
Description
Credential Name *
Enter a descriptive name to identify the credential.
Username *
Enter the Nutanix account username used for discovery.
Port *
Enter the connection port for the Nutanix endpoint. The displayed value is 9440.
Skip TLS Verify
Select to skip verification of the endpoint’s TLS certificate. Leave cleared to verify the certificate.
Create and Add
Creates the credential and adds it to the current discovery job.
Cancel
Closes the dialog without completing credential creation.
Credential Selection Guidance
Use a dedicated Nutanix account with permission to read the infrastructure and virtual machine information required for discovery. Enter its username and password, and confirm the endpoint port—9440 is shown. Keep Skip TLS verify cleared so the endpoint’s certificate is verified. Give the credential a descriptive name, such as Nutanix Production Discovery, then click Create & Add.
On Settings, select the collection depth needed for the job.
Review what the selected mode collects.
Scroll down to configure performance, data scope, and reachability options.

Figure: Settings | Collection depthCollection depth
Description
Fast
Collects identity, hardware, and operating system information without software. The screen lists hostname, OS, CPU/RAM, disks, and NICs.
Normal
Adds information such as software, hotfixes, services, users, and Hyper-V guests to hardware collection.
Deep
Adds running processes, scheduled tasks, system restore configuration, and CVE correlation when enabled. The UI identifies it as suitable for small scopes or deep audits and slower per host.
The visible helper text explains that depth controls how much Hypervisor collects for this job.
Recommended starting point
Begin with a representative host and the collection depth required by the inventory task. Reserve Deep collection for situations where its additional data is needed and the scan window can accommodate the work.
Configure Performance and Reachability

Figure: Performance and Reachability SettingsField name
Description
Timeout per host (s)
Time allowed per host. The UI shows 180 seconds and states that 0 removes the per-host limit for deep WMI. This is separate from the job timeout.
Job timeout (hours)
Overall Temporal workflow limit. The visible helper text specifies a minimum of 24 hours.
Pre-flight Ping
Checks reachability before protocol collection and skips hosts that do not respond to the selected ping protocol.
Ping Only
Checks host reachability without collecting protocol data. Use for a network sweep, not a detailed inventory.
Reachability Decision: Use a reachability method that your network permits. A target that does not respond to ICMP may still provide a discovery protocol. Investigate the network policy before treating a failed pre-flight check as proof that a device is powered off.
This section of the Discovery job Settings screen controls how long discovery can run, how target reachability is checked, and how scan requests are managed. These settings help administrators balance inventory collection requirements with execution time and network capacity.
Before collecting information, the job can perform a preliminary reachability check. The screen labels this process Knocking.

Figure: Knocking configurationField Name
Description
Timeout per host (s)
Specifies the time allowed for collection from an individual host. The displayed value is 180 seconds. For deep WMI discovery, 0 removes the per-host time limit. This setting is separate from the overall job timeout.
Job timeout (hours)
Specifies the overall execution limit for the Temporal workflow. The displayed value is 24 hours, which the screen identifies as the minimum.
Pre-flight Ping
Checks whether a target responds to the selected reachability protocol before attempting discovery. Hosts that do not respond are skipped. This option is enabled in the screenshot.
Ping Only
Checks host reachability without collecting inventory through WMI, SSH, or SNMP. Use this option for a reachability sweep. It is disabled in the screenshot.
Ping Protocol
Selects the method used for the preliminary reachability check. The displayed selection is ICMP (default). The helper text also identifies TCP connect and UDP probe methods.
Knock concurrency
Controls the number of parallel reachability checks. The displayed value, 0, selects Auto (500). The screen specifies a maximum of 2,000.
Rate limit (req/s)
Limits the number of discovery requests per second to help manage load on target devices. The screen indicates that 0 means unlimited.
These are collection settings shown in the demonstration, not a complete firewall specification. Have the infrastructure team validate the connectivity required by the selected protocol and deployment.
Recommended tuning sequence: Start with a small scope. Review duration, unreachable targets, and partial results. Adjust request rate, concurrency, or timeouts one at a time so you can assess the effect of each change.
Configuring scoring and diagnostic capture
Enable Coverage Score when you need to assess inventory completeness.
Enable the diagnostic capture options needed for operational review and support.
Enable CVE Correlation only after its prerequisite configuration is in place.
Click Next to open Schedule.

Figure: Scoring and diagnostic optionsField name
Description
Coverage Score
Calculates per-device collection coverage for WMI, SSH, and SNMP enrichment. Helps identify which parameters were collected and why others were not.
CVE Correlation
Matches discovered software against the NVD CVE database. The screen states that an NVD API key is required.
Capture Engine Logs
Stores detailed engine log lines for each run. Helps troubleshooting and increases storage use.
Capture Per-Host Results
Stores per-IP drill-down results for each host. The screen notes that disabling it can reduce storage.
During initial implementation, keep enough diagnostic detail to verify host outcomes. After the job is stable, review capture and retention requirements with the team responsible for storage and support.
Execution and Scheduling: You can run the job using either Temporal Worker or using Discovery Engine. If you opt for Discovery Engine, it will not use the worker.
Select the execution option supported by your deployment.
For Temporal Worker, choose a worker with access to the target network. Check the Effective task queue carefully.
For an immediate validation run, leave Enable scheduled runs off and click Create & Run Now.
For recurrence, enable Enable scheduled runs and configure the interval supported by your deployed release. Verify its time basis and save behavior before activating the recurring job.

Figure: Scheduling and ExecutionField Name
Description
Temporal Worker
Executes through the discovery worker and Temporal. This option is selected and marked recommended in the UI.
Discovery Engine
Alternative local execution option shown in the demonstration.
Effective task queue
Selects the worker queue used for execution. The helper states that both scheduled runs and Run Now use only the selected worker queue.
Worker search
Searches the available worker entries when the queue selector is expanded.
Enable scheduled runs
Turns recurring execution on or off. The helper describes automatic runs at the configured interval.
Create & Run Now
Creates the job and starts an immediate run. The button is shown while scheduled runs are off.
Once you click Scan and Run Now, you will get a message mentioning Job started.

Figure: Job saved successfully