In this article I will show you how to install VCSA 6.7 (VMware vCenter Server Appliance).
To start, you need an installation kit of vCenter Server Appliance 6.7. For this article, I will use the VCSA 6.7 Update 1 version – VMware-VCSA-all-6.7.0-10244745.iso (the latest available at the time I wrote this article).
Note: If you look for VCSA upgrade instructions, check this article: How to Upgrade vCenter Server Appliance from 6.5 to 6.7 – Stage 1.
Install VCSA 6.7 (VMware vCenter Server Appliance) – Stage 1
To launch the installer I will use a Windows virtual machine (alternatively you can use a Mac or a Linux system). Unzip the archive and navigate to VMware-VCSA-all-6.7.0-10244745\vcsa-ui-installer\win32 folder. Launch installer.exe and begin to install VCSA 6.7.
vCenter Server Appliance 6.7 Installer will start. Click on Install.
The installation process consists in two separate stages. At the end of the first stage we will deploy the appliance, then in the second stage we will configure it. Let’s start with first stage: click Next.
Read the End user license agreement, check “I accept the terms of the license agreement” checkbox and click Next.
We now must choose the deployment type. I will show a simple installation, so I will choose “vCenter Server with an Embedded Platform Services Controller”. Read more on vCenter 6.7 available deployment types. Click Next.
We now have to enter the details of the ESXi server where we will deploy the VCSA 6.7 appliance. If you don’t have any available ESXi server, you can read my article How to Install VMware vSphere 6.7. Click Next.
Installer will connect now to the ESXi server. If you don’t have trust relationship configured, you will receive a certificate warning. Click Next.
We need now to set up the appliance name (this is the name of the virtual machine that you will see in vSphere Client, and not the FQDN of the vCenter) and the root password. Click Next.
For next step we need to select the deployment size. You can see the resources allocated for different deployment sizes. As I deploy this vCenter in a home lab, I chose Tiny deployment with a default storage size. Click Next.
Select on which ESXi datastore you want to deploy the appliance. You have also the option to enable thin disk mode. Last option allows you to configure a new vSAN cluster and deploy the appliance on this cluster. I will not treat vSAN deployment in this article.
You need to decide on DNS records of the vCenter appliance. Before moving on, make sure you already have A and PTR records for VCSA in your DNS server (if you miss this one, deployment will fail). I check below for forward and reverse name resolution.
We need now to configure networking details. Pay attention to the system name (you will not be able to change it afterwards). To avoid deployment failure, double-check the FQDN and the IP address. Click Next.
Review all the settings and if everything is correct, click Finish.
The wizard starts now to deploy the vCenter Server Appliance 6.7.
First stage is now complete. We have the appliance ready and powered-on on the target ESXi server. To move to the second stage, click Continue.
Install VCSA 6.7 (VMware vCenter Server Appliance) – Stage 2
Stage 2 wizard begins. Click Next.
Choose time synchronization mode. You can either name the desired NTP server, either opt for synchronization with the ESXi host. Second option is about enabling SSH. You can change both options later in appliance console. Click Next.
We’re now at SSO configuration. Choose your domain name, password and the site name. As you can see, you can’t change the SSO administrator username. Click Next.
Decide if you want to join VMware Customer Experience Improvement Program. Click Next.
Review all the details. If alright, click Finish.
We see a warning now. Once started, we will not be able to pause or stop the installation process. Click OK.
Appliance configuration starts now. As expected, we have no button to cancel the process.
After some time, configuration will complete.
Now you have a fully functional VCSA 6.7 (VMware vCenter Server Appliance) instance. Happy VM managing