VMware

In the previous post, I covered how to license a standalone ESX 9.0 host by importing a private license file directly on the host with esxcli. That workflow was straightforward: generate a keypair, grab a license file from the portal, scp both files to the host, run two esxcli commands, done. VCF 9.1 changes everything. Starting with 9.1, you cannot generate individual ESX host licenses from the VCF Business Services console and apply them directly. Instead, Broadcom introduced a License Server appliance — a small OVA that sits between the portal and your hosts. You import your private license file into the License Server, and the License Server issues host-scoped licenses to each ESX host via API. ...

After years of running my tech blog on WordPress, I finally pulled the trigger and migrated everything to Hugo — a blazing-fast static site generator — hosted on Cloudflare Workers. The result? A site that loads in milliseconds, costs nothing to host, and requires zero server maintenance. Here’s exactly how I did it, what went wrong, and what I’d do differently. Why Leave WordPress? WordPress served me well for years. But as my post count grew to 278 articles (mostly VMware VCF guides with dozens of screenshots each), the cracks started showing: ...

If you upgraded (or deployed) ESX/ESXi 9.0 in a lab and let the evaluation expire, you can end up in the classic chicken-and-egg situation: your vCenter is a VM, but you can’t power it on because the host is no longer licensed. With VCF / vSphere Foundation 9.0, licensing moved away from the old 25-character keys and into license files(normally handled through VCF Operations), which is great… until you don’t have VCF Ops up yet. (VMware Blogs) ...