vCenter Server Appliacnce (VCSA) 6.5 Deployment

vCenter Server Appliacnce (VCSA) 6.5 Deployment
You may already heard of that VMware released the vCenter server 6.5 and you can experience new features with this new release. I’m in the middle of articles writing during my busy schedule and this is the article for the vCenter Server Appliance aka VCSA 6.5 Deployment. 
It is not just a typical appliance deployment and there are few changes when compared to the traditional pre-built OVA or OVF appliances. Basically, it has two main Stages in the deployment.

Let’s get started….

Stage 1 Deployment

 First of all you need to setup your DNS entries for your vCenter Appliance as that’s a common requirement for every deployment.

Mount your ISO to your Management server as we need to run the deployment wizard. Go to “vcsa-ui-installer/win32” folder and run the “installer”.

It will open up a “vCenter Server Appliance installer” installer wizard and you can select below options for the deployment according to your requirement.

  • Install – Fresh installation of the VCSA appliance 
  • Upgrade – Perform a VCSA upgrade 
  • Migrate – That’s a new feature which you can use to migrate your old vCenter server to a new VCSA6.5 appliance. 
  • Resetore – You can backup your vCenter from the VCSA management console and this is an option to restore the vCenter from your backup. Click on “Install” to start the deployment.

You can see the introduction on the first page and this is the Stage 1 of the deployment, just click on “Next” to continue
Accept the EULA and click “Next” to continue 
At the next step you need to select the deployment method and I’m using here an embedded deployment, select your method and click “Next” to the next step
Enter your ESXi host or the vCenter details where you want to keep the vCenter Appliance, Click “Next” to continue.
It will throw you the “Certificate warning!”,  I believe you are familiar with those warnings when you are working with the ESXi hosts. 
It will take sometime to validate the provided information and at the next step you need to specify a name and a password for the appliance. 
Select the Resource requirement for the deployment sizes 
Note: If you are enabling VCSA HA feature which we are going to discuss in the future, you need to have at least “Small” Deployment Size in your vCenter. 
Select the datastore where you are going to keep your VCSA Appliance, If it is a test environment you can enable the “EnableThin Disk Mode” for your appliance, Click “Next” to continue
Configure the Networking settings at the next step and options are self explanatory, Click “Next” to the final step of the Stage 1
You can review the settings at the next step and click “Finish” to start the deployment
Let the installation Complete the Stage 1 and click “Continue”.

Stage 2 Deployment

You can see the Introduction in the first page and click “Next” to continue
At the next step you can specify the NTP servers for the Appliance or you have the option to sync the time with the ESXi host. Also you can enable/disable the SSH to the appliance 
Specify the SSO domain name, Administrator password and the Site name at the next step, click “Next”
If you would like to participate to the CEIP select the check box and go to the next step by Clicking the “Next”
You can see the Summary of the Stage 2 Configuration at the next page, review and click “Finish” to start the Stage 2 Deployment. You can see a Warning! Message saying you will not be able to stop or pause the installation after this. Click “OK” to continue
Let the Appliance to complete the deployment and “Close” the wizard once it deployed the appliance successfully
Open your web browser and type “https://<FQDN or IP of the Appliance>, You can see there are two links to access the web console. 
Note: HTML 5 Browser is coming with the appliance and you can access it here, Please note it is still in the development and you can find me previous posts regarding the HTML5 Fling test from here
Generic, web console 
HTML 5 browser 
Type “https://<VCSA FQDN or the IP Address>:5480 to access the Management console
That’s it for the deployment. You can try your own and thank you for reading my Post.
Click to rate this post!
[Total: 0 Average: 0]

Leave a Reply

Your email address will not be published. Required fields are marked *