VMware Virtualization, Cloud Management & Automation
In modern virtualised environments, memory often becomes the constraint before CPU does. That problem is more challenging today as memory pricing remains volatile and supply less predictable, driven by AI-focused hardware demand. Expanding DRAM is no longer a simple upgrade decision. It carries real budget, procurement and planning impact. There is also an indirect domino…
I was doing an in-place vCenter upgrade from vCenter 8 to vCenter 9 using the VCSA 9 ISO. Stage 1 (deploying the new appliance) completed fine, but Stage 2 prechecks failed with a generic “internal error” in the installer UI. In this post I’ll show how I troubleshooted and solved it.
Deploying vCenter Server (VCSA) using the CLI installer is fast, repeatable, and ideal for lab environments or scripted deployments. In this post, I’ll demonstrate how to deploy a brand new vCenter server using the CLI installer. While this post focuses on CLI deployment from macOS, the process for Linux and Windows is very similar.
The VMware Cloud Foundation (VCF) 5.2.1 poster, available here, provides a clean, visual overview of how the platform integrates compute, storage, networking, and security into a unified, automated stack. It highlights key features such as full-stack lifecycle management, flexible storage options, built-in micro segmentation, and the ability to deliver a public cloud–like experience within the…
If you’re using standard vSwitches, keeping port groups consistent across ESXi hosts can be tedious and error-prone. VLANs are easy to replicate, but port group policies like security, NIC teaming, and traffic shaping are often missed. This PowerCLI function lets you clone standard vSwitch port groups from one host to another, including their associated policies….
I recently moved over to an Apple Silicon-based Macbook Pro, and after installing Visual Studio Code and Powershell (pwsh), I was prompted with the following error. Unable to find PowerShell! Do you have it installed? You can also configure custom installations with the ‘powershell.powerShellAdditionalExePaths’ setting. Fortunately, the fix is straightforward. First, open up Terminal (zsh)…