ESXi: searching for “vim-cmd vmsvc/message” lead me to the “Managing ESXi Without VI Client” series of blog posts

Last week, I wrote about ESXi: on the console/ssh, when a moved VM pauses during power-on: show which VMs have messages waiting, then answer them.

The “vim-cmd vmsvc/message” – Google Search there lead me to this very interesting series of blog posts on managing ESXi Without VI Client.

It was written in the ESXi 4 and 5 era (for a time-frame, see [Wayback] VMware ESXi Release and Build Number History | virten.net) where VIC – the [Wayback] VMware Infrastructure Client, later named VC:  [Wayback] vSphere Client – ruled.

The series content holds remarkably well now that VIC/VC got first replaced by the [Wayback] vSphere Web Client (often called [Wayback] vSphere HTML 5 Client and started out of the [Wayback] ESXi Embedded Host Client fling).

Anyway, here are the posts in the series:

1. [Wayback] Managing ESXi Without the VI Client – Part 1 – Virtual Machine and VPS Tutorials – initial setup and creating a VM
2. [Wayback] Managing ESXi Without the VI Client – Part 2 – Virtual Machine and VPS Tutorials – add a license key, enable VM automatic startup and shutdown and unregister a VM
3. [Wayback] Managing ESXi without the VI Client – Part 3 – Virtual Machine and VPS Tutorials – create a virtual switch and configure a firewall VM
4. [Wayback] Managing ESXi without the VI Client – Part 4 – Virtual Machine and VPS Tutorials – install an update for ESXi
5. [Wayback] Managing ESXi Without VI Client – Part 5 – Virtual Machine and VPS Tutorials – creating a datastore, then moving a VM between datastores

–jeroen