In this post, I am going to walk through the installation of a VCSA deployed in the combined vCenter and PSC roll, and walk through the basics of configuration. This appliance is being deployed in the new IVOXY lab, so expect more content as we walk through the pieces and parts needed to deploy a functional training lab.
Previously, our consultants were nice enough to configure our switches, internet connections, and install ESXi on our (5) servers. Basic domain services have been done, and our SAN is configured. This installation was performed by a windows 10 jumpbox in the datacenter.
First thing is first, we need to get the installation media and mount it on our jumpbox. I have already uploaded the VCSA ISO (named VMware-VCSA-all-6.5.0-4602587.iso in my case) to the local datastore of my ESX host, and will now mount it to the virtual jumpbox.
Browse out to the windows installer at: <CDROM>:VCSA-ui-installer\win32\installer.exe
This is now an executable, so no need to worry about the browser plugin (which is excellent news if you ask me).
Get through the introduction screen on the wizard and accept the EULA.
Select the vCenter server with embedded platform services controller and click “Next”.
Now, because we do not have much in the way of infrastructure, we are going to deploy this vCenter server directly to an ESXi host, although deploying to another vCenter server is supported.
You will get a certificate warning, and provided that the signatures match (which we always check of course) select “Accept”. Next, we will select a name for our appliance and a root password.
Next we are going to select the appliance size. I’m going to stick with a small appliance. I tend to oversize my appliances to help with performance.
Select a datastore, and then fill out the network info. Unlike previous versions, 6.5 will tell you ahead of time if it can’t resolve. Make sure DNS is correct and select “Next”.
Next we will configure the vCenter appliance
I enabled SSH and set up NTP
I configured a new SSO domain, notice that I no longer have the option to join an existing SSO domain.
Finish up the installation and grab a cup of coffee.
It is worth noting that my first installation failed. I am fairly sure this is due to putting in 2 DNS servers in the installation, even though only 1 is active at the moment.