I’m using vSAN within my Homelab. In this post I explain the update (replacement) of the vSAN Witness Appliance. An update is a replacement in fact. You power up a new Witness Appliance, configures it, disable the Stretched Cluster and reconfigure this one with the new Witness.
Sounds to easy? But it is…
This little post describes the deployment of the vSAN Witness Appliance.
The list of my articles with “Update vCenter Appliance” is growing :)
This article explains the update to version 6.0.0 U2 (18.104.22.16800) of the VMware vCenter Server Appliance.
In my older articles I described the updates for earlier versions
- http://blog.ganser.com/975 Update from the first version of vCenter Server Appliance 6 to the 6.0.0 U1.
The update needs to connect an ISO image and CLI commands to be installed.
- http://blog.ganser.com/1165 Update from version 6.0.0 U1 to 6.0.0 U1b.
In this update was an error where the installation stucks at 70%, but in fact the update was complete. Only a manual reboot was necessary.
I prefer the update via Webinterface, but do also watch the progress with the console.
In my article http://blog.ganser.com/975 I described the update from the first version of vCenter Server Appliance 6 to the Update 1. The update needs to connect an ISO image and CLI commands to be installed.
In vCenter Server Appliance you could go the same way or update via Webinterface.
On January 22nd VMware Release Notes added a hint, what to do if the installer stuck at 70%. Read more at the end of my install steps.
As I advertised here is my upgrade how-to for vCSA (vCenter Server Appliance) 5.5 to vCSA 6.0.
In my previous post I show the “workaround” to get a vCS (vCenter Server) 5.5 installed on a Windows Server 2012 R2 on a Windows Server 2008 R2.
After this migration it was possible to “Migrate Windows vCenter Server 5.5 to vCenter Server Appliance 5.5“ with the VMware Fling vCS to vCSA Converter.
Now its time to get the Version of vCSA from 5.5 to 6.0