Skip to main content

Basic Install of VMware VCSA 6.0

Installing VMware VCSA 6.0

In this post I will be detailing the basic steps required to setup a basic install VMware's vCenter Appliance 6.0. As I am just deploying this in to my test lab I have not considered much on the design of new offering from VMware around the setup of  Platform Services Controller (PSC) offering.

If you would like to know more about PSC a good starting place would be VMware KB2113115 and VMware Blog.
Pre-Requisites :

- Follow my other post on installing Client Integration Plugin
- Have VMware vSphere 6 appliance ISO
- Have an ESXi host built and connected to storage to host the appliance to be installed
- Have access to a Windows machine which you can mount the VMware vSphere 6 appliance ISO
- Have ESXi host username and password
- Have a read of the following KB from VMware on the supported method of installing SSO
- Have a name and IP address you will assign to this appliance
- Have subnet, gateway and DNS settings
- Have a password to set for VCSA Appliance 6
- Have a password to set for SSO

 1) You should of already installed "Client Integration Plugin" already before moving on. If not then follow my other post on installing it. Installing Client Integration Plugin

2) Mount the VMware vSphere 6 appliance ISO and browse to the CD content and locate "vcsa-setup.html" on the root of the CD. (Try to use Internet Explorer 11 which I was using at the time as with other browsers there seems to be issues with the plugin working depending on the version of the browsers that you have)

3) You may receive this prompt and you can just click "Yes"

4) Within the browser window you will see the following message and it should disappear within 30 seconds if it detects the plugin has been installed correctly

5)  The vCenter Server Appliance 6.0 installation option screen should appear so click "Install"

6)  Select "I accept the terms of the license agreement" and click "Next"

7) Enter the ESXi host IP or FQDN to connect to so that we can deploy our VMware vCenter appliance to and click "Next"

8) If you receive a certificate warning just check if it is correct for your organisation i.e. the VM host  and then click "Yes"

 9) Give the appliance a name as this will be the "Display Name" for the appliance and set a password for this appliance then click "Next". The password rules are as following:
  • At least 8 characters
  • No more than 20 characters
  • At least 1 uppercase character
  • At least 1 lowercase character
  • At least 1 number
  • At least 1 special character (e.g @, !)
  • Only visible lower-ASCII characters (Spaces are not allowed)

 10) Select which option you would prefer for installing SSO (Platform Services Controller) or have a read of VMware KB article KB 2108548 before proceeding at this point. I selected Embedded as this is only a lab test

11) Select "Create a new SSO domain" as this is the first PSC (Platform Services Controller) that we will be deploying. The password rules are as following:
  • At least 8 characters
  • No more than 20 characters
  • At least 1 uppercase character
  • At least 1 lowercase character
  • At least 1 number
  • At least 1 special character (e.g @, !)
  • Only visible lower-ASCII characters (Spaces are not allowed)
 Give a SSO domain name that does not exists in your environment and a site name for this PSC to be associated with then click "Next"

Domain Name rules:
  • Each character in a label must me alphanumeric or a dish (-)
  • The first character in each label must be a letter and the last character must be alphanumeric
  • Each label must not exceed 63 characters and the entire name must not exceed 253 characters in textual representation
  • Must contain at least one dot (.)
  • Example vsphere.local
Site Name rules:
  • Should include alphanumeric characters or the symbol dash (-)
  • Should not include high-ASCII/non-ASCII characters
  • Should not exceed 63 characters 

 12) Select appliance size based on the number of host and VMs this appliance will need to support. The description section will tell you what size the VM will be configured. Click "Next"

 13) Select which datastore you wish to deploy this appliance to and also select if you would like to use thin provisioning. If you do then select "Enable Thin Disk Mode" and click "Next".


14)  Decided if you wish to use the embedded DB (vPostgres) or Oracle. For this case we will select "Use an embedded database (vPostgres)" and click "Next".

15) Configure all the network settings for this appliance and enable SSH if you want. Use the scroll bar to navigate down and then click "Next". Do make sure you that there is time synchronisation between the ESXi host and NTP server otherwise the deployment will fail.

16) Check all the settings are correct. If there are any that are not correct then press the "Back" button to go back to the relevant pages to edit. Once all OK click "Finish" to deploy the appliance.

17) You should see the screen below once the appliance has been deployed successfully and click "Close" to finish.

18) Use which ever method you prefer to view the console of the appliance to make sure it has started up correctly

 To access the appliance browse to the FQDN of the appliance followed by vsphere-client. Example would be https://ServerName.myvmx.local/vsphere-client.



Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://,udp:// 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net