What’s New VMware vSphere 6.7 Update 1

vSphere 6.7 Update 1 is now generally available. This release includes a single HTML5 vSphere Client. The vSphere SSO domain also is receiving more flexibility with support for embedded repointing. Now a single embedded deployment can move to another vSphere SSO domain. Another feature with enhancements in vSphere 6.7 Update 1 is Content Library. It now supports native vCenter Server templates (.vmtx) and Open Virtual Appliance (OVA). Of course, there are more new features and enhancements in this release. Without further ado, here is what’s new in vCenter Server 6.7 Update 1.

vSphere Client

We have a fully featured vSphere client in vSphere 6.7 Update 1. The vSphere team also wanted to optimize the vSphere Client’s performance and workflows. Ensuring the best customer experience possible. This release includes smart porting over and completing the remaining features which included:

• vCenter High Availability (VCHA)
• Auto Deploy
• Host Profiles
• vSphere Update Manager
• Network Topology Diagrams
• Performance Charts
• Improved Searching
• Dark Theme

Content Library

This feature has been around since vSphere 6.0 and is one of my favorites. As a customer, I had to manage several images, scripts, OVAs, and templates for several remote sites. Having to maintain and update the same content in several locations can be a nightmare. Content Library is a native vCenter Server service which solves this problem. It uses the subscriber/publisher model to distribute content. There are two deployment models when using Content Library:

Single vCenter Server managing several sites

• Centralized managed content
• Uses WAN to sync content, requires publishing vCenter Server to be available
• Content stored on a datastore at the remote sites
• When provisioning content at the remote sites, traffic is kept local

Multi vCenter Server

• Centralized managed content
• Uses WAN to sync content
• Can sustain publishing vCenter Server failure, remote locations continue to operate
• Content stored on a datastore at the remote sites
• When provisioning content at the remote sites, traffic is kept local

vSphere Health

This is a new feature with huge potential. When deploying your vCenter Server there is an option to enable CEIP. It stands for Customer experience improvement program. When enabled data gets sent to VMware’s analytics cloud, customer workload data is not part of the data collected. This is all anonymous, data is secure and housed in VMware’s data centers. VMware uses this telemetry data to help improve features and customer experience. Now when enabled this functionality provides even more value to the customers.

Remaining new update i will cover my next post shortly. I hope this has been informative and thank you for reading!