VMBook field guide

Cross-platform remote VM support for users on different operating systems

Support virtual-machine users across Windows, Linux, macOS and other guest systems from one remote VM inventory.

Why this becomes a problem

Remote support becomes difficult when every host, hypervisor and guest has a different tool. A Windows administrator may need to help a Linux guest, a Mac user may run Windows 11 Arm, and a lab may mix x86-64, Arm64 and RISC-V machines. Asking users to translate hypervisor-specific commands during an outage increases delay and risk.

Remote support specialists assisting users at computers
A support workflow should identify the host and guest before an operator changes machine state. Photo: Jep Gambardella / Pexels.

How VMBook approaches it

VMBook organizes sites, computers, platforms and machines in one model. An authorized operator can inspect state, start or stop a machine and coordinate access without pretending that all guests are identical. The user can keep working in Windows, Linux, macOS or another supported guest; VMBook assists at the virtualization layer and leaves guest credentials and applications under their normal controls.

Blue illuminated servers installed in a data-center rack
The same VM inventory can span a desktop, a homelab rack and a remote machine room. Photo: panumas nikhomkhai / Pexels.

Recommended workflow

  1. Identify the physical host and platform before changing the guest.
  2. Check machine state, architecture, firmware and recent lifecycle events.
  3. Use the guest console or its approved RDP, SSH or VNC path for in-guest work.
  4. Record the action and return control to the user; do not share host-level tokens with the guest user.

Limits and checks

VMBook is not a replacement for an endpoint-management, help-desk or privileged-access product. Guest screen sharing, identity, audit retention and consent must follow the organization’s own support policy. Network isolation may intentionally prevent console or guest access.

Primary documentation

Frequently asked questions

What problem does this guide solve?

The operator and the person asking for help do not need to run the same operating system. VMBook manages the host and virtual-machine lifecycle, while the guest can use its own console or remote-access method.

How does VMBook help?

VMBook organizes sites, computers, platforms and machines in one model. An authorized operator can inspect state, start or stop a machine and coordinate access without pretending that all guests are identical. The user can keep working in Windows, Linux, macOS or another supported guest; VMBook assists at the virtualization layer and leaves guest credentials and applications under their normal controls.

What should I verify before using it?

VMBook is not a replacement for an endpoint-management, help-desk or privileged-access product. Guest screen sharing, identity, audit retention and consent must follow the organization’s own support policy. Network isolation may intentionally prevent console or guest access.

Download VMBook free Browse all guides

VMBook connecting desktop, server and compact hosts across processor architectures
One machine model across desktops, servers and processor architectures.
VMBook control plane connecting virtual machines across three data-center sites
Remote hosts grouped into sites, with each host in control of its machines.