Currently, the VMware vCenter Server Appliance (vCSA) requires a Windows helper VM. This helper VM can be loaded with a number of different items, most notably vSphere Update Manager (VUM) and VMware Horizon View Composer. The services this VM can contain are listed later in this article. Suffice it to say, the helper VM (or VMs) become critical to …
Continue reading “vSphere Upgrade Saga: vCSA Helper VM, Part 2”
VMworld 2016 has officially begun, kicking off with Pat Gelsinger’s keynote presentation at the Mandalay Bay Hotel in Las Vegas, Nevada. Some events have been taking place over the weekend, but I consider the keynote to be the true starting point of the event. This year, the Solution Exchange welcome reception was held the night before …
In my previous vSphere Upgrade Saga post, VSAN Upgrade Woes, I discussed upgrade problems in a relatively unsupported configuration. I finally figured out why I had such a problem. It was not the unsupported nature of the configuration, but the disk space used within VSAN. In effect, my VSAN was heavily overcommitted, and as such, there was no …
I’ve written before about the difficulty as a user of getting hold of VMware’s NSX and about other problems with the release, but a small recap is in order. Founded in 2007, Nicira was bought by VMware in 2012 for its SDN platform. This consists of deep integration that combines the open VXLAN standard with vSphere’s vShield-like products …
In case you have not heard the news, Microsoft recently announced that the company is open sourcing PowerShell and will be bringing PowerShell to both Linux and OS X. Actually that is just part of it in that it is not just PowerShell that Microsoft has open sourced, but rather the .NET framework as well as the PowerShell Editor Service and making it available for Linux and OS X at the PowerShell GitHub repository.
The upgrade to VSAN 6.2 did not go as smoothly as I wished. It was possible to do but required me to rebuild not only VSAN but my cluster as a whole as a rolling upgrade did not work as expected. Perhaps this is just the way I have my VSAN configured.
