Hyper-V Satellite
Discover the virtual machines running on your Microsoft Hyper-V hosts and roll them into the CMDB — securely and read-only.
Microsoft Hyper-V
Hyper-V resources brought into the CMDB
- Virtual machines across standalone & clustered Hyper-V hosts
- Identity, run state, status & clustered (HA) flag
- Each VM rolled into the CMDB as a managed asset
- CPU count, uptime & creation date
- Memory — startup, min/max, assigned, demand & Dynamic Memory
- Attached virtual disks & network interfaces (NICs)
Deploy alongside your Hyper-V hosts
Run the Hyper-V Satellite as a Docker container or install it on any supported Linux host — ideally within the same network as your Hyper-V hosts, so all data stays inside the customer’s network boundary.
Docker image
Pull the public CMDB-360 Hyper-V Satellite image from Docker Hub and run it on any host that already has Docker installed.
Universal Installer
Install on any Oracle Linux 8/9 or Ubuntu 20.04/22.04 host (ARM or x86_64) with the graphical Installer or the non-interactive AutoInstaller for scripted setups.
We recommend deploying the Satellite within the same IP space as your Hyper-V host(s) so sensitive data stays inside the customer’s network boundary — though it can run anywhere that can reach the hosts and has outbound access to the Base Station. Minimum footprint: 1 vCPU, 4 GB RAM, 10 GB disk. It needs outbound access to the Hyper-V host management interface over WinRM (5985/tcp or 5986/tcp) and to the Base Station; no inbound ports are required.
A simple two-step setup
When you deploy with the Installer or AutoInstaller, configuration is handled for you. Otherwise the on-instance tools walk you through two steps.
1 · Connect to the Base Station
Using the AdminTool, point the Satellite at your MSP’s CMDB-360 Base Station with its URL and the unique access token issued for the Satellite. These are held in an encrypted config.yml, then services are restarted.
2 · Connect to Hyper-V
Run the ConfigTool and enter your Hyper-V host IP or FQDN and a read-only Hyper-V user and password. The Satellite connects to the host management interface over WinRM and begins discovery.
The Satellite needs only read-only access to Hyper-V and must be able to reach the host management interface over WinRM (typically 5985/tcp for HTTP or 5986/tcp for HTTPS). You can disable discovery of any resource type — or turn off the on-demand detail channel entirely — from the Satellite scheduler, so it only ever sees what you choose to expose.
How the Hyper-V Satellite protects data
The Hyper-V Satellite runs inside the customer’s network and never touches the virtual machines directly — it queries the Hyper-V host management interface over WinRM and sends non-sensitive rosters to the CMDB-360 Base Station. Detailed information is streamed on demand and only while a user is viewing a record, so nothing proprietary is stored outside the environment.