As you all know, 17 / 04 / 2018 was the 6.7 version of VMware products. We have some cool news, including vCenter's HTML5 interface is almost 100% ready. The list with all the news you can see in the following links:
As in the links above we already have a lot of information about the launch, I decided to do a step by step update from VCSA to new version, since I want to update my homelab as soon as possible to know the news!
So come on. I am assuming that you have VCSA 6.5 installed and working in your environment, and that vCenter is using the topology with the PSC in the same VM. The process of upgrading VCSA 6.7 is a two-step process:
- First is the deploy of a new ESXi host appliance;
- In a second moment all the data from the current VCSA is copied to the new one.
Therefore, ensure that there are memory, cpu, and disk resources available for creating this new VCSA VM. Also, make sure you have a backup of your vCenter data.
With the VCSA 6.7 .iso file, extract it and navigate to the "vcsa-ui-installer" and "win32" folders. Open the installer.exe file
The VCSA installation, upgrade, migration, and restore wizard will open. Click "Upgrade."
On the first screen just click "Next" to start.
Accept the license terms and click "Next."
In the next screen we must fill in with the FQDN or IP of our VCSA current and click "Connect to Source".
After connecting you will be prompted for the SSO User name and SSO Password of your VCSA besides the root password. You must also enter the FQDN or IP and host credentials where your current VCSA is running. Click "Next" to proceed.
In the next screen we must define the FQDN / IP and host credentials that will host the new VCSA. In my case it's the same as I already use for the current VCSA. Click "Next" to proceed.
In the next screen we must define the VCSA 6.7 VM name and the root password. Click "Next" to proceed.
Choose the configuration of your VCSA based on the needs of your environment. In my case I will use the "Tiny". Click "Next" to proceed.
In the next screen we must choose the datastore where the VM will be created. We can also choose to be created with "Thin" discs. Click "Next" to proceed.
In the next screen we must fill with the temporary network information for the new VCSA. After restoring data from old to new this IP will no longer be used and you will be able to access the new VCSA as it was already accessing the old one. Click "Next" to proceed.
The next screen shows only a summary of the settings. Click "Finish" to start.
Wait for the process of deploying and configuring the new VCSA.
After you finish, click "Continue" to proceed to the next phase of deploy.
In this phase we will restore the data from the old VCSA to the new one. Click "Next" to proceed.
In the next screen we can choose the data that will be taken. Not necessarily you need to take all the events, tasks and performance metrics, but in my case I will take everything. Choose the best option for your environment and click "Next".
In the next screen we can choose to participate in the VMware CEIP and share technical information of the product deploy and operation. This is very important for VMware to enhance its products, so if it is possible to leave it marked. Click "Next" to proceed.
On the next screen we will only have a summary of the settings and a checkbox to confirm that you have a backup before starting the process. Click "Finish" to start.
You will also receive a warning that the source VCSA will shut down after the network migration to the new VCSA is complete. Click "OK."
Wait for the entire process. It can take a lot depending on the size of your base.
After finishing click "Close".
When accessing our VCSA will already be presented a new screen to choose between the HTML5 or Flash interface. Remember that from the next release we will no longer have the interface in Flash.
When accessing the VCSA the environment is ready for use.
Checking the version we will see that the upgrade was successful.
That's it, people.
In case of doubts you can access the official documentation on the upgrade by clicking HERE.