I was skeptical to see if there was actually anything extra that was put into the installer – because we all know that it most of the customization is provided within the OVF itself. I even went so far as to use the vSphere Client! I then proceeded to deploy this appliance as I would any virtual appliance. So for my test I copied the vmware-vcsa file and added the. It is obvious that the file is not an OVF – but probably an OVA – because of its size. In the VCSA folder you will find a file vmware-vcsa which is almost 2GB in size.

The ISO is about 3GB in size which means that it actually has to be appliance is probably there somewhere. The VCSA is appliance after all – which means it is probably an OVF – like most of VMware’s appliances.ĭisclaimer – This is probably not supported – definitely not endorsed by VMware – so use it at your own risk! If you look at the ISO that is provided for download – you will see a folder structure there for all platforms in the vcsa-cli-installerīut this got me thinking. I do understand that VMware wanted to provide a generic tool that could be used on any platform to deploy a vCenter Server. Why limit this to connecting directly to an ESXi host?Īlso I am quite intrigued to know what is the benefit of using such a tool for deployment. I actually find this really silly and a really weird move on behalf of VMware. When trying to put in a vCenter as the target for deployment it will throw an error. The documentation also says the same thing.

Hey… Is that even possible? It seems that it is not – at least that is what I heard this week over only to ESXi at the moment supported.- Frank Büchsel March 15, 2015

Vmware vcenter appliance 6.0