Why this becomes a problem
Teams often expose the wrong layer. Publishing a hypervisor or VM manager directly to the internet gives a user far more authority than a remote desktop session needs. Relying only on RDP or SSH creates the opposite problem: when the guest fails to boot, loses its address or blocks a firewall rule, nobody can see the firmware or recovery screen. Mixed Windows, Linux and macOS environments add different clients, authentication systems and display behavior.

How VMBook approaches it
VMBook keeps machine lifecycle management at the host layer and groups machines by site, computer and platform. An operator can verify which physical computer owns a guest, inspect its state and assist with start, stop or recovery. The person using the guest can continue with the operating-system-native access method. This separation lets a Windows support desk assist a Linux VM, or a Mac user reach Windows 11 Arm, without requiring every person to administer the underlying hypervisor.

Recommended workflow
- Place VMBook host access behind a trusted management network, VPN or zero-trust gateway.
- Give ordinary users guest-level accounts rather than host tokens.
- Enable RDP for supported Windows guests, SSH for Linux administration, or a secured VNC/SPICE path where appropriate.
- Keep an out-of-band console route for boot, firmware and broken-network recovery.
- Confirm architecture, firmware, encryption and snapshot state before changing virtual hardware.
- Document who owns the guest, how consent is obtained and which actions must be logged.
Limits and checks
Do not expose port 3333, an RDP listener, VNC or a BMC interface broadly without network controls and authentication. VMBook 0.1 is not an enterprise privileged-access, endpoint-management or help-desk suite. macOS virtualization and Windows 11 Arm packaging must be validated on the actual Apple-silicon host before production use.
Primary documentation
Frequently asked questions
What problem does this guide solve?
A remote desktop virtual machine has three separate control paths: the VM management connection changes power and hardware, the virtual console reaches the guest when its network is broken, and an in-guest protocol such as RDP, SSH or VNC supports daily user work. Use each path for its intended job.
How does VMBook help?
VMBook keeps machine lifecycle management at the host layer and groups machines by site, computer and platform. An operator can verify which physical computer owns a guest, inspect its state and assist with start, stop or recovery. The person using the guest can continue with the operating-system-native access method. This separation lets a Windows support desk assist a Linux VM, or a Mac user reach Windows 11 Arm, without requiring every person to administer the underlying hypervisor.
What should I verify before using it?
Do not expose port 3333, an RDP listener, VNC or a BMC interface broadly without network controls and authentication. VMBook 0.1 is not an enterprise privileged-access, endpoint-management or help-desk suite. macOS virtualization and Windows 11 Arm packaging must be validated on the actual Apple-silicon host before production use.

