Skip to main content

vSphere 6.7 Released

VMware has just released vSphere 6.7 and everyone will be looking to see what the new features are and  possibly of upgrades. Here are some of the steps I usually follow:

  • Check if the hardware that you wish to run vSphere 6.7 is supported, as per usual every release VMware will drop some support for some hardware support especially around CPU If your system is not listed then the next best bet for you is to visit your hardware vendors website to see if they have newer information. For example we have HPE servers and I obtain information from this page 
  • Next step is to check all the other VMware products you have as part of your solution. You have to see if they are compatible with vSphere 6.7 and if there is an upgrade path for the version you are currently using

Usually once I done the above then I know it is worth planning the upgrade path. Here is the main landing page for vSphere 6.7 but I have also provided some of the direct links below to the articles in case they change them

  • Introducing vSphere 6.7
  • Introducing vCenter 6.7
  • Introducing faster lifecycle management operations in vSphere 6.7 
  • Introducing vSphere 6.7 Security
  • Introducing vSphere with Operations Management 6.7
  • Introducing Developer Automation Interfaces vSphere 6.7
  • Introducing vSphere 6.7 Enterprise Applications

Documents on vSphere 6.7

  • Read this KB before upgrades

  • Release Notes for 6.7

  • ESXi Upgrade

  • vCenter Upgrade Paths

I will be updating this page as I find more useful resources around vSphere 6.7


  1. Thank you for sharing the vSphere 6.7 update. My computer's hardware is fully supported by vSphere. Virtualization is really very useful in IT field.


Post a comment

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://,udp:// 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net