Step 2 - Extract the contents of the ISO and add the. Step 1 - Download the VCSA Beta which is available as an ISO

Here are the steps to deploy the VCSA Beta using either VMware Fusion or Workstation: However, due to the lack of OVF Property support, it can also be passed in through the VMX file of the Virtual Machine. Ideally, these are passed in from the OVF Properties using either the vSphere Web Client or the new VCSA deployment tool. If you inspect the latest VCSA Beta OVA, which you will need to extract from the ISO, you will notice a series of 'keys' that begin with guestinfo which is just leveraging custom key/value pairs for the OVF environment. That is why they have built the VCSA to be quite flexible to support both vSphere as well as Fusion and Workstation, however the process may not be completely obvious for the latter. Having said that, VMware Engineering is quite aware that this can be challenging for many customers as well as VMware Employees who make use of Fusion and Workstation on a daily basis. These parameters leverages OVF properties which are currently not supported in VMware Fusion and Workstation and therefore the new injectOvfEnv option in ovftool can not be used.

Having been a long time Beta participant when I was customer and still continuing to do so in my current role, the best way to evaluate and test new VMware software is to of course run them on top of vSphere! I know this may not be an option for everyone and the next best thing would be to use VMware Fusion or Workstation.įor those of you who have tried to run the vSphere Beta of VCSA on VMware Fusion or Workstation, you may have found that it does not work as there are some input parameters that are required as part of the new VCSA deployment. If you are taking part in the vSphere Beta (available to public to sign up but still under NDA), you may have recently noticed a new milestone release (RC) that has been made available for download.

Vmware vcenter 6.0 download