Hyper-V
Hyper-V Discovery
What it does
Discovers Microsoft Hyper-V infrastructure across an Active Directory domain. Discovery sources (configurable): - TargetHosts (explicit list of FQDNs / NetBIOS names) - EnumerateFromAD (boolean): queries AD for computer objects whose servicePrincipalName contains "Microsoft Virtual Console" / "Microsoft Virtual System" / "Hyper-V Replica" - typical Hyper-V server SPNs. Returns FQDNs. - FailoverCluster (FQDN of a cluster): Get-Cluster + Get-ClusterNode + Get-ClusterGroup + Get-ClusterResource + Get-ClusterSharedVolume on each node - VmmServer (FQDN of SCVMM): Get-SCVMMService + Get-SCVMHost + Get-SCVirtualMachine Per host, enumerates VMs (Get-VM), switches (Get-VMSwitch), checkpoints (Get-VMSnapshot), replication (Get-VMReplication), host networking (Get-NetAdapter + Get-NetIPAddress), SMB shares, and cluster shared volumes where applicable. Permission-denied / DCOM / CIM errors are surfaced as [ACTIONABLE] warnings (not silent skips) and persisted to HyperV_Warnings.csv for review. All exports go to $Context.Paths.RawDataOutput (static filenames so the renderer-side useHyperVDiscoveredLogic hook can load them by name).
How the app exposes it
The module feeds into the ACQI app's dedicated results view. From there, conflicts, dependencies, and readiness scores roll up into the deal workspace.
/discovered/hyperv Outputs
Each module produces a CSV with readiness and risk scores, evidence-source counts, and last-seen timestamps. The exact columns vary by module — the app's results view shows the live schema.