As with any new release of vSphere, it is quite common for customers to deploy the new software in either a vSphere home or test lab to get more familiar with it. Although not everyone has access to a vSphere lab environment, the next best thing is to leverage either VMware Fusion or Workstation. With the upcoming release of vSphere 6.5, this is no different. In fact, during the vSphere Beta program, this was something that was asked about by several customers and something I had helped document as the process has changed from previous releases of the VCSA.

In vSphere 6.5, the VCSA deployment has changed from a "Single" monolithic stage where a user enters all of their information up front and the installer goes and deploys the VCSA OVA and then applies the configurations. If you had fat finger say a DNS entry or wanted to change the IP Address before applying the actual application configurations, it would not be possible and you would have to re-deploy which was not an ideal user experience.

In vSphere 6.5, the new UI installer will still allow you to perform a "Single" monolithic stage but it is now broken down into two distinct stages as shown below with their respective screenshots:

Stage 1 - Initial OVA deployment which includes basic networking

vcsa-6-5-installer-1
Stage 2 - Applying VCSA specific personality configuration

vcsa-6-5-installer-2
Just like in prior releases of the VCSA, the UI translates the user input into specific OVF properties which are then passed into the VCSA guest for configuration. This means that if you wish to deploy VCSA 6.5 running Fusion or Workstation, you will have two options to select from. You either deploy VCSA and complete both Stage 1 and 2 or just Stage 1 only. If you select the latter option, to complete the actual deployment, you will need to open a web browser to the VAMI UI (https://[VCSA-IP]:5480) and finish configuring the VCSA using the "Setup vCenter Server Appliance" option as shown in the screenshot below.

vcsa-6-5-installer-3
If your goal is to quickly get the VCSA 6.5 up and running, then going with Option 1 (Stage 1 & 2 Config) is the way to go. If your goal is to learn about the new VCSA UI Installer, then you can at least get a taste of that by going with Option 2 (Stage 1 Config) and this way you can step through Stage 2 using the native UI installer.

One last thing I would like to mention is that there have been a number of new services added to the VCSA 6.5. One example is that vSphere Update Manager (VUM) is now embedded in the VCSA and it is also enabled by default. With these new services, the tiniest deployment size is going to require 10GB of memory where as before it was 8GB. This is something to be aware of and ensure that you have adequate resources before attempting to deploy the VCSA or else you may see some unexpected failures while the system is being configured.

Note: If you have access to fast SSDs and would like to overcommit memory in Fusion or Workstation, you might be able to get this to work leveraging some tricks mentioned here. This is not something I have personally tested, so YMMV.

Here are the steps to deploy VCSA 6.5 using either VMware Fusion or Workstation:

Step 0 (Optional) - Familiarize yourself with setting up VCSA 6.0 was on Fusion/Workstation with this blog post which will be helpful for additional context.

Step 1 - Download & extract the VCSA 6.5 ISO

Step 2 - Import the VCSA OVA which will be located in vcsa/VMware-vCenter-Server-Appliance-6.5.0.5100-XXXXXX_OVF10.ova using either VMware Fusion or Workstation (you can either double click or just go to File->Open) but make sure you do NOT power it on after deployment. (this is very important)

Step 4 - Locate the directory in which the VCSA was deployed to and open up the VMX file and append one of the following options (make sure to change the IP information and passwords based on your environment):

Option 1 (Stage 1 & 2 Configuration):

guestinfo.cis.deployment.node.type = "embedded"
guestinfo.cis.appliance.net.addr.family = "ipv4"
guestinfo.cis.appliance.net.mode = "static"
guestinfo.cis.appliance.net.pnid = "192.168.1.190"
guestinfo.cis.appliance.net.addr = "192.168.1.190"
guestinfo.cis.appliance.net.prefix = "24"
guestinfo.cis.appliance.net.gateway = "192.168.1.1"
guestinfo.cis.appliance.net.dns.servers = "192.168.1.1"
guestinfo.cis.appliance.root.passwd = "VMware1!"
guestinfo.cis.appliance.ssh.enabled = "True"
guestinfo.cis.deployment.autoconfig = "True"
guestinfo.cis.appliance.ntp.servers = "pool.ntp.org"
guestinfo.cis.vmdir.password = "VMware1!"
guestinfo.cis.vmdir.site-name = "virtuallyGhetto"
guestinfo.cis.vmdir.domain-name = "vsphere.local"
guestinfo.cis.ceip_enabled = "False"

Option 2 (Stage 1 Only Configuration):

guestinfo.cis.deployment.node.type = "embedded"
guestinfo.cis.appliance.net.addr.family = "ipv4"
guestinfo.cis.appliance.net.mode = "static"
guestinfo.cis.appliance.net.pnid = "192.168.1.190"
guestinfo.cis.appliance.net.addr = "192.168.1.190"
guestinfo.cis.appliance.net.prefix = "24"
guestinfo.cis.appliance.net.gateway = "192.168.1.1"
guestinfo.cis.appliance.net.dns.servers = "192.168.1.1"
guestinfo.cis.appliance.root.passwd = "VMware1!"
guestinfo.cis.appliance.ssh.enabled = "True"
guestinfo.cis.deployment.autoconfig = "False"
guestinfo.cis.ceip_enabled = "False"

Step 5 - Once you have saved your changes, go ahead and power on the VCSA. At this point, the guestinfo properties that you just added will be read in by VMware Tools as the VCSA is booting up and the configuration will begin. Depending on the speed of your hardware, this can potentially take up to 15min+ as I have seen it. Please be patient with the process. If you wish to check the progress of the deployment, you can open a browser to https://[VC-IP]:5480 and you should see some progress or you can periodically connect to the Hostname/IP Address and once it is done, you should be taken to the vCenter Server's main landing page.

13 thoughts on “How to deploy the vCenter Server Appliance (VCSA) 6.5 running on VMware Fusion & Workstation?

  1. You use File | Import to import the OVA, not Open, right?

    Also, I copied and pasted your lines and was able to get it working, then changed the IP addresses in the VCSA. However, if I edited the lines in the VMX file after copying them to change the IP addresses to mine (10.x) it kept saying Dictionary Error or that the VMX file is corrupt. Any idea why that may be?

    • Jason, I had the same problems with “Dictionary Error” or “VMX file is corrupt”. I think it has to do with the characters used when copying and pasting from the website into TextEdit. I ended up editing the file using VI and hand typed everything in. That “mostly” worked, but I still had to set a root password and configure my NIC settings once the appliance came up. After that, and a restart of the management network, everything seems to be running. Fingers crossed that it actually works!

      • Confirmed to work by using a plain text editor, or switching TextEdit to plain text mode. The other problem I had was due to the fact that I didn’t have my forward and reverse DNS entries set. Once I did that, I re-ran the deployment and it worked perfectly.

  2. These instructions seem incomplete. The instructions assume things that aren’t exactly straight forward. From what I can see, and from VMWare’s information, there is no vCSA 6.5 OVA, only in ISO format. How do we get to Stage 1 in the article if there is no OVA.

  3. I’m hoping we can edit the memory allocation for this as previous versions… I’m always of an appliance over a windows based install, but 10gb memory allocation on a home lab setup is a big ask, especially when I am running 6.5 from a 2008 server install with 3gb quite happily.
    anyone know of any ways to knock the memory allocations down again? is it similar to the 6.0 ways (java heap etc)?

    • hey bro, did you find some way to install ESXI 6.5 in hom lab with less than 10 gb of ram? i know i can install it in one of the host but i am really stubborn and i want it in my laptop (8gb ram).

  4. I just tried this and the vmx file got ignored and overwritten. It came up with localhost as the network. Before editing the file I did change the memory to 6GB

    Thoughts?

    • i actually did it, just open powershell in administrator mode (i don’t know if is mandatory) then just navigate to F:\vCenter-Server and run the .exe followed by “SKIP HARDWARE CHECKS=1” , the quotation marks are obligatory , its all, of curse i tried with 6gb and get an error because of lacks of ram, later i tried with 8 gb and it installed without problem. i dont know if my error was an isolated situation and you can actually install it with less than 8 gb of ram.

      greetings from Chihuahua Mexico.

Thanks for the comment!