Skip to main content

Installing vCenter Appliance 6.5

vCenter appliance 6.5 is one of the latest & stable release of vCenter . vSphere 6.5 adds an X-Large deployment size, the update manager and a fully supported migration assistant to the appliance. So it’s time to migrate your Windows based vCenters to appliance with vSphere 6.5.
vSphere 6.5 is fully dependent on webclient. So no more vSphere client or C# client.

VCSA 6.5 Enhancements

  • Supports up to 2000 ESXi Hosts and 35.000 Virtual Machines
  • Guided Installer (Interactive Installer, instead of OVF Template)
  • Robust deployment (Separate Deployment and Configuration to prevent failed deployments
  • Migration Assistant (Migrate vCenter Server 5.5 or 6.0 for Windows to vCenter Server Appliance)
  • Native High Availability
  • VMware Update Manager
  • Built-In Backup+Restore
  • Improved Appliance Management
  • HTML5-based vSphere Client
  • Photon OS (Replaces SUSE Enterprise 11)


To view the compatibility of Esxi, vCenter server and vsphere client version, hardware compatibilty for Esxi , device comparability, Guest operating system compatibility, VM compatibility for Esxi. please use below link.

For Hardware compatibility for Esxi follow below link

So, Get started with the deployment of vSphere 6.5

  1. Download the VMware VCSA 6.5 ISO from MyVMware
  2. Mount the ISO or extract it and depending upon the system (Linux, Windows or Mac) you’re using to start the deployment locate the installer folder under ‘vcsa-ui-installer’
  3. Create A record & PTR for the vCenter
  4. If you were not configuring AD, add host entry details.

1) Launch the installer

Follow the instruction and click on Install if its a fresh install or select Upgrade if you have upgrade plan.

Accept the agreement with VMware and select the deployment model as per your design

Enter the details of ESXi host or vCenter server

Accept the SSL certificate prmpt and enter the name of VCSA VM and credentials.

Specify the deployment size and based on your environment and LLD.

Select the datastore where you would like to install

At end configure networking requirements 

After this review the configuration and start the deployment.

Stay tuned for next update.... : :)


Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl