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 https://www.vmware.com/resources/compatibility/search.php. 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 https://www.vmware.com/resources/compatibility/sim/interop_matrix.php


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 https://blogs.vmware.com/vsphere/launch but I have also provided some of the direct links below to the articles in case they change them


  • Introducing vSphere 6.7 
https://blogs.vmware.com/vsphere/2018/04/introducing-vmware-vsphere-6-7.html
  • Introducing vCenter 6.7
https://blogs.vmware.com/vsphere/2018/04/introducing-vcenter-server-6-7.html
  • Introducing faster lifecycle management operations in vSphere 6.7
https://blogs.vmware.com/vsphere/2018/04/introducing-faster-lifecycle-management-operations-in-vmware-vsphere-6-7.html 
  • Introducing vSphere 6.7 Security
https://blogs.vmware.com/vsphere/2018/04/introducing-vsphere-6-7-security.html
  • Introducing vSphere with Operations Management 6.7
https://blogs.vmware.com/vsphere/2018/04/introducing-vsphere-operations-management-6-7.html
  • Introducing Developer Automation Interfaces vSphere 6.7
https://blogs.vmware.com/vsphere/2018/04/introducing-developer-automation-interfaces-vsphere-6-7.html
  • Introducing vSphere 6.7 Enterprise Applications
https://blogs.vmware.com/vsphere/2018/04/introducing-vsphere-6-7-enterprise-applications.html


Documents on vSphere 6.7

  • Read this KB before upgrades

https://kb.vmware.com/s/article/53704

  • Release Notes for 6.7

https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vsphere-esxi-vcenter-server-67-release-notes.html

  • ESXi Upgrade

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.esxi.upgrade.doc/GUID-65B5B313-3DBB-4490-82D2-A225446F4C99.html

  • vCenter Upgrade Paths

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vcenter.upgrade.doc/GUID-EB29D42E-7174-467C-AB40-DB37236FEAF5.html


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

Comments

  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.

    ReplyDelete

Post a Comment

Popular posts from this blog

New Azure KMS IP and domain Addresses for activation

For Windows virtual machines deployed into Azure using marketplace images you may have created rules in your NSG or firewalls to allow the server to communicate the Azure KMS activation service. This used to be kms.core.windows.net and had an IP address of 23.102.135.246. As of March 2023 Microsoft has moved to a new address azkms.core.windows.net and has two IP addresses "20.118.99.224" and "40.83.235.53". The existing address kms.core.windows.net is pointed to the new IP of 40.83.235.53.  So if your servers are having issues with activation please check your rules to ensure they have the new IP addresses and you can resolve the old and new domain names ( azkms.core.windows.net,  kms.core.windows.net)

On board Azure Resources to use Azure AD Privileged Identity Management (PIM)

If you have Azure AD Premium P2 licences one of the reasons would of been to use Privileged Identity Management (PIM) as its a great tool to help provide "just-in-time" privileged access for resources where you don't need permanent access to.  In this article I will be going through how to onboard Azure resources into PIM so that you can control privileged access for your Azure resources as well. This means you can create conditional access policies for certain resources, resource groups, subscriptions or even management groups to ensure users only have the required permissions at the right time.  An example would be, by default you assign reader role for IT operations staff so that they can see all the resources. If they decided they need to make a change they would need to use PIM to activate a particular role you have assigned them which gives them permissions to make the change. As part of activating the role you might want to add some conditions. You might add that u

Visual Studio and Azure Services access behind a firewall

There is an article by Microsoft that lists all the URLs that Visual Studio requires to install or interaction with Azure services if you was behind a firewall or proxy. Obviously you don't have to allow everything through but you can see what you need to allow through if there was something specifically needed. I know after the pandemic most people are working from home and have a direct access to the internet but there are environments where access are still very control behind firewalls. This document provides the URLs, the ports it uses and a brief explanation about why it is needed which is always useful when you are speaking to your security team on why you need to punch another hole through the firewall. https://docs.microsoft.com/en-us/visualstudio/install/install-and-use-visual-studio-behind-a-firewall-or-proxy-server?view=vs-2022 Snippet of web page which list why each of the URLs are required and for what service