Well, after the announcement of VMware vSphere 6.7 Update 2, the bits are finally GA! VMware vSphere 6.7 Update 2 is a great step forward for the platform. VMware continues to evolve the platform to be more and more powerful and cloud aware as well as provide features and functionality that customers around the world need and want. This certainly helps to solidify their position as the leader in enterprise virtualization across the landscape of on-premises virtualization as well as delving into cloud. It is remarkable that VMware Cloud on AWS is now in the #4 cloud spot after such a short lifespan! In most environments, the order of upgrading your VMware vSphere 6.7 environment to vSphere 6.7 Update 2 will be upgrading your vCenter Server. In this post, we will take a look at how to upgrade to VMware vSphere vCenter VCSA 6.7 Update 2 with VAMI to see this process in action.
What’s New in VMware vSphere 6.7 Update 2 vCenter Server?
First, before we look at the process to upgrade, let’s take a look at some of the new features contained in this release of vSphere 6.7 Update 2.
- Ability to change the MAC address selection policy
- New REST API to converge vCenter Server appliances with external Platform Services Controllers
- CEIP integrated into the converge utility
- Ability to track encryption keys with a new SOAP API
- Precheck for upgrading vCenter Server systems
- vSphere Auditing Improvements
- Simplified restore of backup files
- New Auditing events recorded
- Ability to create alarm definitions to monitor backup status of vCenter
- New Enterprise Edition ROBO feature of DRS in Maintenance Mode
- Publish .vmtx templates directly from a library to multiple subscribers
- vSphere Health Alarm and Categories provides better visibility
Tremendous new features to be fair, included in this newest release of VMware vSphere 6.7 Update 2.
Upgrade to VMware vSphere vCenter VCSA 6.7 Update 2 with VAMI
In this video tutorial I walk you through the installation and configuration of VMware vCenter Server Appliance 6.7 (VCSA). This tutorial is designed for anyone that wishes to learn how to install. This walkthrough will cover the ability to migrate a Windows Embedded vCenter Server 6.5 to a VCSA 6.7. The Migration process is not only a migration but also an upgrade from 6.5 to 6.7.
In the following screenshots and steps, let’s take a look at what the process looks like to upgrade to VMware vSphere vCenter VCSA 6.7 Update 2 with VAMI interface which allows easily pulling down the latest update to VMware vCenter Server and applying the patch through the VAMI interface. To login to the VAMI interface, navigate to the URL https://<your VCSA IP>:5480
Login as root and navigate to the Update menu. The VAMI update menu is very straightforward and allows pulling updates from URL or CD-ROM. Click the Check Updates button in the upper right hand corner and check for updates from URL and CD-ROM. This should correctly pull the latest “Update 2” patch which is listed in VAMI as 6.7.0.30000 and the release date is Apr 10, 2019.
Expanding the patch details displays more information regarding the patch including services affected, download size, etc. Click the Stage and Install link to begin the installation.
This begins the Stage and Install Update wizard. Scroll down on the EULA and check the “I accept” checkbox, then click Next.
On the second step, you have a choice to Join CEIP or not. Make your selection here and click Next.
On the third and last step, select that you have backed up vCenter Server and its associated databases before you will have the option to Finish. One thing to notice and I have seen this before is the Estimated downtime to vCenter Server time can be wildly inaccurate. I can assure you that I ran through the update after seeing this screen and it was not down for 267 minutes! Anyways, something to take note of and not necessarily rely on.
Once you click Finish, the installation in progress will begin. The download of the update will begin as noted by the Staging in progress status.
After the download of the update is complete, the installation will begin stopping services on the VCSA appliance.
The installation will begin installing packages which indicates the update is progressing along.
After a few minutes, the Installation succeeded message should display. You simply have the option to Close the dialog.
One other nice thing I noticed about the Update 2 installation through VAMI is the appliance was automatically rebooted for me. In fact, I didn’t notice the reboot happening at all until I started checking things out. As you have no doubt seen before, you will install an update and then have the notice that you will need to reboot. This in my case was done automatically. After the appliance came back up, I checked the version under the Summary dashboard and it is correctly showing the new version 6.7.0.30000 build number 13010631.
You will know for sure you have Update 2 as VMware has finally updated the login screen to reflect the new Clarity UI theme! Cool stuff, looks much better!
Wrapping Up
The Upgrade to VMware vSphere vCenter VCSA 6.7 Update 2 with VAMI interface is extremely easy and painless. I have come to rely on the VAMI interface over the years since it has gotten so much better with the VCSA appliance in the past few releases. It is certainly becoming an even more powerful tool for vSphere administrators managing their vSphere environments. The new tools and functionality built-in are allowing a lot of functionality for administrators in terms of visibility, troubleshooting, and management of the VCSA appliance. I am looking forward to getting deeper under the hood of vSphere 6.7 Update 2 and the new goodies included. Stay tuned for more Update 2 blog posts to come!
vCenter Server Installation and Setup describes how to install and configure VMware vCenter Server,
vSphere 6.7 provides various options for installation and setup. To ensure a successful vSphere deployment, understand the installation and setup options, and the sequence of tasks.
The two core components of vSphere are ESXi and vCenter Server. ESXi is the virtualization platform on which you can create and run virtual machines and virtual appliances. vCenter Server is a service that acts as a central administrator for ESXi hosts connected in a network. vCenter Server lets you pool and manages the resources of multiple hosts.
You can install vCenter Server on a Windows virtual machine or physical server, or deploy the vCenter Server Appliance. The vCenter Server Appliance is a preconfigured Linux-based virtual machine optimized for running vCenter Server and the vCenter Server components. You can deploy the vCenter Server Appliance on ESXi hosts 6.0 or later, or on vCenter Server instances 6.0 or later
Starting with vSphere 6.0, all prerequisite services for running vCenter Server and the vCenter Server components are bundled in the VMware Platform Services Controller™. You can deploy vCenter Server with an embedded or external Platform Services Controller, but you must always install or deploy the Platform Services Controller before installing or deploying vCenter Server.
vSphere Web Client and vSphere Client
Instructions in this guide reflect the vSphere Client (an HTML5-based GUI). You can also use the instructions to perform most of the tasks by using the vSphere Web Client (a Flex-based GUI).
vSphere Web Client Software Requirements
Make sure that your browser supports the vSphere Web Client. The vSphere Web Client 6.7 requires Adobe Flash Player v. 16 to 23. For best performance and the most recent security updates, use Adobe Flash Player 23. VMware has tested and supports the following guest operating systems and browser versions for the vSphere Web Client. For best performance, use Google Chrome.
Mount the ISO and click autorun. The VMware vCenter Installer will open. Ensure vCenter Server 6.7 for Windows Server 2012 is selected.
Read and Accept the end user license agreement and click Next.
In this section, we will be using a vCenter Server and embedded deployment model. If you are using an external deployment model the Platform Services Controller (PSC) component must be installed first before the vCenter. Select the deployment type and click Next.
in this section Enter the A fully qualified domain name (FQDN) in the System Name field and click Next.
vCenter Single Sign-On Configuration section, or join the vCenter to an existing Single Sign-on (SSO)domain. If you are creating a new Single Sign-on (SSO) domain give this a meaningful name, please do use same as your Active Directory name, VMware vCenter Server 6.7 default name is vsphere.local. enter the password and Configure a password for the Single Sign-on (SSO) administrator account and a vCenter site name, Then click on Next.
Enter Specify a user to login or Windows Local System Account,
By Default, the vCenter Server Instance runs in the Windows Local System Accounts, if you need to run in another administrative user account, select the blow option to specify a user service account and provide the account credentials.
Enter default, Select an embedded Postgre database or configuration Microsoft SQL Server Express edition, or another supporting database. Then click Next.
here show all port which using the VMware vCenter Server 6.7, and easily customize ports, best is default port configuration and click Next.
If you need to change the vCenter Server 6.7 installation location, Select the directory to install vCenter services and click Next.
- First Location Install vCenter Server with an embedded Platform Services Controller
- Second Location Store data for vCenter Server with an embedded Platform Services Controller
VMware Customer Experience Improvement Program, Then click Next.
The complete summary of installation VMware vCenter Server 6.7.0. Check the configuration on the review page, after review Click on Install
Begin the installation process.
this section the installation has completed Click on Launch vSphere Web Client Once, Then Click on Finish
After Launching
Login VMware vCenter Single Sign-On