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
The VMware Labs engineers created a converter machine to migrate your vCenter Server 5.5 installed on a Microsoft Windows Server to the vCenter Server Appliance.
This guide shows the steps to successful migrate the data.
With the experience I’ve made I could not recommend the use of the Fling in production. I’ve tested several times the conversion in Testlab without any errors. But the database of our production seems to have many object which are not upgradeable from vCSA 5.5 to vCSA 6. The Upgrade fails in a vPostgres firstboot error.
VMware Flings are not offical software releases from VMware.
Your support might be obolete by using this Fling.
Read the Technical Preview Agreement
The VMware Labs engineers built a fling to migrate a vCenter Server installed on a Windows Server to the vCenter Server Appliance.
For me the greatest limitation is that Windows Server 2012 a higher isn’t supported yet. Because of “winexe-bug” the migration appliance could not get the data from the source machine. William Lam told me that the engineers know about this issue and hopes that it would be fixed soon.
For all of you who could not wait… maybe I’ve a workaround.