I know some of you were disappointed like I was that the new VCSA 6.0 HTML UI Installer is only currently supported on Windows and does not work on Mac OS X. I have been told by Product Management that this is temporary and that Mac OS X support will be coming in a future update. In the meantime, if you do not wish to spin up a Windows VM just to deploy the new VCSA from the HTML UI Installer, you can check out this tiny hack that allows you to deploy the new VCSA 6.0

Note: This trick will only allow you to deploy either an Embedded VCSA or Platform Service Controller. It does not work when trying to deploy an vCenter Server Management Node which is why I suspect Mac OS X support was not in this initial release of vSphere 6.0.

Disclaimer: This is not officially supported by VMware, please use at your own risk.

Step 1 - You will need to download and install the vSphere Client Integration Package (CIP) 6.0 package for Mac OS X by visiting the following URL: http://vsphereclient.vmware.com/vsphereclient/VMware-ClientIntegrationPlugin-6.0.0.mac64.dmg

Step 2 - You will need to extract the VCSA ISO to your local filesystem

Step 3 - Open up a terminal and change into the root directory of the extract VCSA ISO and we will need to modify the vcsa-setup.html file.

deploy_vcsa6_ussing_html_installer_on_mac_osx_2
Step 4 - Run the following sed command which will replace the check for the OS platform from Windows to Mac OS X:

sed -i .bak 's/Win32/MacIntel/g' vcsa-setup.html

Note: You might also be able to use this trick for Linux desktop by properly replacing the navigator.platform property with the correct OS type.

Step 5 - Open the vcsa-setup.html using either Firefox or Chrome and give it a few seconds for the CIP to be loaded and you should be able to launch the VCSA HTML UI Installer as seen in the screenshot below

deploy_vcsa6_ussing_html_installer_on_mac_osx_1
I have found sometimes the HTML UI is stuck at the "Starting VMware vSphere Web Client" screen but when you look at the VM Console of the deployed VCSA, it is completely done. I recommend that if the VM Console looks done, you can just close this screen and just open a browser connecting to the hostname/IP Address of your new VCSA and everything should be working as expected.

deploy_vcsa6_ussing_html_installer_on_mac_osx_3
If you prefer to deploy the VCSA 6.0 on Mac OS X through an officially supported method, there is also a new VCSA CLI Installer that is supported on Windows, Mac OS X and Linux which you can find more details in this whitepaper here. In addition to this trick, you can also deploy the new VCSA 6.0 directly to vCenter Server or onto VMware Workstation/Fusion, for those alternative approaches be sure to check out my Ultimate automation guide to deploying the VCSA 6.0.

5 thoughts on “How to deploy VCSA 6.0 using the HTML UI Installer on Mac OS X?

  1. Nice post as usual! I tried this procedure and was able to install VCSA 6 under ESXi 5.5U2 running under Fusion 7.1.1. However, the installer hung after 8 minutes for over 40 minutes on the “Starting vSphere Web Client Services” step, and never completed. The vCenter welcome screen comes up, but the vsphere-client just shows an unadorned login page and never responds beyond that.

    This is the same result I got when installing under Fusion, using the “ultimate-automation-guide-to-deploying-vcsa-6-0-part-1-embedded-node”. I’m starting to wonder if vCenter 6 requires internet access in order to complete the install – I have it on an isolated VLAN for testing.

    • afaik VCSA 6.0 definitely does not require internet access, in fact I’ve deployed it in several environments that definitely does not have the ability to reach out to the internet and it was successful. I’ve not tried additional layer of Nested like you have but definitely have gotten this to work with latest Fusion release. However, one thing I would note is that VCSA 6.0 does require proper NTP source (so when you deployed directly to Fusion, not sure if you specified one or just did time sync from host) other than that it should work. You can always look at the console of the DCUI to see if there’s any errors.

      • Good to know that it works on an isolated net.

        Re: logs, there are many to look at. I don’t see anything obviously wrong. Any suggestions? Any string I could search for?

        I know on vCenter 5.5U2 I had to assign a name to the host and also for esxi in /etc/hosts to fix a problem with SSO. Is it the same for 6?

  2. Good info, i do have the issue of the HTML saying “Starting VMware vSphere Web Client…” and when i check the console i see

    [Running] /usr/lib/vmware-vpx/firstboot/vpxd_firstboot.py

    this has been like this for over 20 mins now..and resources monitoring shows nothing going on…brand new clean vcenter 6 install on a clean esxi6 server

    thoughts?

  3. Does the console ever get to the point where it displays the IP Address of your VCSA? Depending on your underlying storage, it’s possible it could take some time but shouldn’t be more than 20min+ unless there’s issues with underlying storage or pESXi host

Thanks for the comment!