Skip to main content
The Hyper-V scan module captures Hyper-V hosts with their host configuration, their virtual switches and their virtual machines. It requires a connected gateway.

​
Captured data

The scan creates assets of these types: How the detail pages of the types are structured is described in Virtualization.

​
Setting up the job

The wizard follows the standard path Basics › Targets › Schedule › Summary—see Creating a Scan Job. The Targets step is what sets this module apart. Each row carries the columns IP/Hostname and Credentials. IP/Hostname takes one Hyper-V host per row. The Credentials column may stay empty. The scan then runs under the gateway’s service account, and that account needs the rights under Permissions. An entry in Credentials for all targets applies to every row without an assignment of its own.

​
Prerequisites

​
Ports and protocols

​
Permissions

  • The account is a local administrator on the Hyper-V host, given as DOMAIN\user or user@domain.local.

​
Network requirements

  • The firewall allows the ports above.
  • .NET Framework 4.6.1 or later is installed on the host.
  • PowerShell version 3 or later can run on the host.
  • The account has access to C:\Windows\Temp and to the host’s IPC$ share.
Scan Hyper-V hosts that the gateway cannot reach with the Discovery-HyperV.exe scan script directly on the host—see Scanning by Script. After it is created, the job appears among the jobs; how you watch and adjust it is in Managing Jobs. How you provide and run the scan scripts and read in their results is in Scanning by Script.