Home Blog vSphere 6.5 – Deploy VCSA

vSphere 6.5 – Deploy VCSA

by Brian

With vSphere 6.5, and the deprecation of the Client Integration Plugin (CIP), our team has made a very easy to use vCenter UI installer that can be run from Linux, Mac, or Windows. The deployment/installation is split into two stages:

Deploy is very straight forward as you will see in the screenshots below. There are nine screens that will get you through stage 1.


End user license agreement – You must accept to move on, of course.screenshot-2016-10-18-08-11-49

Select Deployment Type – Here you can choose your deployment option (See an awesome poster on deployment types made by Emad Younis HERE)

Choose your deployment option and hit ‘Next’


Appliance deployment target – Here you will put in the ESXi host or vCenter server information of where you will be deploying the VCSA to. screenshot-2016-10-18-08-12-04

Certificate Warning – I haven’t replaced my certificates so I get this warning. Go ahead and accept the warning to continue.screenshot-2016-10-18-08-12-11

Set up appliance VM – Here you will give VCSA the VM name that will show up in vSphere, along with the root password that you will use for any SSH’ing, SCP’ing, or logging into the appliance management page.


Select Deployment Size – This time around we have a nice table with the sizing resource requirements to choose from.screenshot-2016-10-18-08-13-04

Select Datastore – Choose an applicable datastore for your VCSA and click ‘next’screenshot-2016-10-18-08-13-14

Configure network settings – here you will choose your network portgroup, IPv4 or IPv6, and all additional networking details. Click ‘Next’.screenshot-2016-10-18-08-14-12

The final page gives you a chance to validate that all of the information here is correct. Ensure that it all is, especially your DNS server. Click ‘Finish’screenshot-2016-10-18-08-14-22

The appliance will begin to deploy onto your target hardware. This will take a few minutes. screenshot-2016-10-18-08-28-51

Once Stage 1 completes, you will be able to see it in your vCenter server (or ESXi host). The best thing to do at this point is to hit ‘Continue’ and start Stage 2. However, if you accidentally close out of the installer at this point (as I have done on accident because I see the green checkbox and think it’s done (Deployment complete), you can still go to https://<FQDN of vCenter>:5480 and continue configuring vCenter from there at a later time.


Stage 2 will setup the newly deployed appliance. Go ahead and click ‘Next’ to begin.


Appliance Configuration – Add your NTP servers (Make sure that you get this address correct as an invalid NTP server is (along with DNS) are the top two reasons VCSA seems to fail when installing.screenshot-2016-10-18-19-38-22

SSO Configuration – Choose your SSO Domain name, username/password, and Site name. If you plan to do Enhanced Linked Mode (ELM) you must make sure that your vCenters use the same SSO Domain name.


Configure CEIP – Just check the box and click Next. This data has already helped us in things such as updating the new default admission control policy settings and more (from a DRS/HA perspective).


Double-check that all the information is correct (once again, check your NTP settings and DNS settings), click ‘Finish’.screenshot-2016-10-18-19-39-02

You’ll get a nice little warning box saying that once you hit ok, there’s no stopping or pausing the installation moving forward. Click ‘OK’.screenshot-2016-10-18-19-39-07

The VCSA will begin to configure itself. This can take a little while so go grab yourself a coke, or check twitter or something ;).


Once the VCSA configuration is complete, you’ll get a few links to get you on your way. One is for the vSphere Web Client, and one is for the Appliance ‘Getting Started Page’. If you want to use the links to jump to the HTML5 client, click the Appliance Getting Started Page link.


This will look somewhat familiar, but you will now see under ‘Getting Started’, 2 options instead of 1:

  • vSphere Web Client (Flash)
  • vSphere Client (HTML5) – partial functionality < BTW it’s getting there and you’ll be able to update with more regularity than vCenter (you’ll be able to update this independently of vCenter server)


And there you have it. Go log in, use the H5 client, and enjoy!


You may also like

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More