VMware vSphere 6: New Release & New Certs
VMware vSphere 6 arrived as one of the most significant updates in the history of virtualization infrastructure. IT professionals around the world had been anticipating this release, and VMware delivered a platform that addressed scalability, performance, and management needs in ways that previous versions simply could not match. From the ground up, vSphere 6 was designed to handle the growing demands of modern enterprise environments, supporting larger workloads, more virtual machines, and far more complex configurations than ever before.
The release introduced sweeping improvements across every core component of the platform. Whether organizations were running small virtual environments or massive data centers with thousands of workloads, vSphere 6 provided the toolset to manage it all efficiently. VMware made it clear with this release that virtualization was no longer just about consolidation — it was about building an intelligent, software-defined infrastructure capable of evolving with business needs.
One of the most talked-about aspects of vSphere 6 was its dramatically improved scalability. The platform now supports up to 64 vCPUs per virtual machine, 1 TB of RAM per VM, and 480 physical CPUs per host. These numbers represented a quantum leap over vSphere 5.5, which topped out at far lower thresholds. For enterprises running memory-intensive database applications or high-performance computing workloads, these improvements were game-changing.
The underlying architecture was also refined to reduce bottlenecks that had affected earlier versions. VMware worked extensively on the ESXi hypervisor to make sure that the added capacity did not come at the cost of performance. The result was a more responsive, stable platform that could handle dense virtualization scenarios without degradation. Organizations deploying vSphere 6 quickly found that they could do significantly more with the same hardware investment.
Live migration has always been a flagship feature of vSphere, and version 6 pushed the boundaries of what vMotion could do. For the first time, long-distance vMotion across different vCenter Server instances and even different geographic sites became possible without shared storage requirements. This opened up entirely new approaches to workload mobility and disaster avoidance, giving administrators the ability to move running virtual machines across vast distances with no downtime.
vSphere 6 also introduced support for vMotion across different virtual switches and network configurations, reducing the constraints that had previously limited migration paths. Administrators no longer needed to ensure perfect symmetry between source and destination environments. This flexibility translated directly into reduced planning overhead and faster execution during maintenance windows or emergency situations.
Previous releases of vSphere offered Fault Tolerance, but it came with a major limitation — only single-vCPU virtual machines were supported. With vSphere 6, VMware removed this restriction entirely. The new Fault Tolerance supports virtual machines with up to four vCPUs, making it practical for a much wider range of production workloads. This meant that business-critical applications running on multi-processor VMs could now benefit from continuous availability without any application-level changes.
The underlying mechanism for Fault Tolerance was also reworked in vSphere 6. The older record-and-replay approach was replaced with a faster, more efficient synchronization method based on fast checkpointing. This new approach reduced the performance overhead associated with FT, making it a far more attractive option for organizations that previously avoided it due to the resource cost. With these improvements, Fault Tolerance became a viable protection mechanism for a broader set of enterprise applications.
VMware introduced the Content Library in vSphere 6 as a way to standardize and simplify how VM templates, ISO files, and other content were managed across distributed environments. Before this feature arrived, organizations often struggled with template sprawl, inconsistent versioning, and the challenge of distributing content across multiple vCenter Server instances. The Content Library provided a single, governed repository for all of this material.
The Content Library supports both local and subscribed configurations. A local library stores content within a single vCenter, while a subscribed library can pull content automatically from a published library on another vCenter Server. This synchronization capability ensured that all sites in a distributed environment were working from the same approved templates and configurations, reducing configuration drift and improving compliance across large deployments.
vSphere 6 introduced the Platform Services Controller, or PSC, as a dedicated component responsible for authentication, licensing, and certificate management across the vSphere environment. Before the PSC existed, these functions were tightly bound to individual vCenter Server instances, which made managing identity and certificates in multi-site deployments unnecessarily complex. Separating these services into a distinct component brought clarity and flexibility to vSphere deployments of all sizes.
The PSC could be deployed in two configurations — embedded or external. An embedded PSC ran on the same machine as the vCenter Server, making it ideal for smaller environments. An external PSC ran independently and could be shared across multiple vCenter Server instances, which was valuable for large-scale deployments that required centralized identity management. This architectural decision gave administrators the flexibility to design their environments according to actual operational requirements rather than being constrained by a single deployment model.
Virtual SAN, which had been introduced in vSphere 5.5, received substantial improvements in version 6. The storage policy-based management model was refined, making it easier for administrators to define and apply storage policies at a per-virtual-machine or per-disk level. Organizations could now specify requirements like redundancy, performance tiers, and cache allocation directly through the vSphere Web Client, and Virtual SAN would enforce those policies automatically.
vSphere 6 also brought support for all-flash Virtual SAN configurations, which significantly improved performance for latency-sensitive workloads. The ability to use solid-state drives for both the caching and capacity tiers unlocked a level of storage performance that had previously required dedicated, expensive SAN hardware. For organizations looking to reduce infrastructure costs while maintaining high performance, all-flash Virtual SAN was a compelling option introduced alongside the broader vSphere 6 release.
VMware introduced its own Certificate Authority component, called VMCA, as part of the vSphere 6 platform. This component was designed to streamline the process of managing SSL certificates across ESXi hosts, vCenter Server, and other solution components. In previous versions, certificate management was often a manual, error-prone process that caused significant pain during upgrades and deployments. VMCA addressed this by automating certificate issuance and renewal within the vSphere environment.
VMCA could operate in several modes depending on organizational security requirements. In its default configuration, it acted as a standalone root CA and issued all vSphere certificates automatically. For organizations with stricter compliance requirements, VMCA could be configured as a subordinate CA under an existing enterprise certificate authority. This hybrid approach allowed IT teams to maintain central control over certificate trust hierarchies while still benefiting from the automation that VMCA provided.
The vSphere Web Client received noticeable improvements in version 6, addressing many of the performance and usability complaints that administrators had raised about the earlier Flash-based interface. Navigation was streamlined, and common tasks could be completed with fewer clicks. VMware also improved the performance of the client itself, reducing the lag that had frustrated users of the 5.x web interface. These refinements made day-to-day administration smoother and less time-consuming.
While the traditional C# client was still available for vSphere 6, VMware made it clear that the Web Client was the primary interface going forward. Certain features in version 6 were only accessible through the Web Client, which pushed administrators to become comfortable with the browser-based interface. This transition, while initially met with some resistance, ultimately resulted in a more consistent and capable management experience, especially in environments with diverse client operating systems.
With the release of vSphere 6, VMware updated its certification program to align with the new platform. The VCP6-DCV (VMware Certified Professional 6 — Data Center Virtualization) became the new baseline certification for professionals working with vSphere 6 environments. This credential validated a candidate’s ability to install, configure, manage, and troubleshoot vSphere 6 infrastructure, and it quickly became one of the most sought-after certifications in the IT industry.
VMware also introduced the VCAP6-DCV Design and VCAP6-DCV Deploy certifications for professionals looking to demonstrate advanced skills. The Design track tested candidates on their ability to architect vSphere solutions based on specific business and technical requirements, while the Deploy track focused on practical implementation skills in complex environments. Both certifications required the VCP6-DCV as a prerequisite, creating a structured progression path for IT professionals looking to build their credentials around the vSphere 6 platform.
The VCP6-DCV exam covers a wide range of topics that align with the features and capabilities introduced in vSphere 6. Candidates are tested on their knowledge of ESXi installation and configuration, vCenter Server deployment, virtual networking with vSphere Distributed Switches, storage configuration including VMFS, NFS, and Virtual SAN, as well as resource management and performance monitoring. The exam also includes questions on high availability, fault tolerance, vMotion, and cluster configuration.
One aspect that distinguishes the VCP6-DCV from earlier VCP exams is its emphasis on the newer components introduced in vSphere 6, including the Platform Services Controller, Certificate Manager, and Content Library. Candidates who studied only for the VCP5 and assumed their knowledge would carry over found themselves unprepared for these newer topics. A thorough review of the vSphere 6 documentation, combined with hands-on lab experience, remained the most effective preparation approach for this exam.
Organizations running vSphere 5.1 or 5.5 had a relatively straightforward path to upgrading to version 6, but it required careful planning. VMware provided detailed guidance on the upgrade sequence, which typically involved upgrading vCenter Server first, then updating ESXi hosts, and finally updating virtual machine hardware versions and VMware Tools. Following the correct sequence was critical, as upgrading components out of order could result in compatibility issues and management disruptions.
For those upgrading from vSphere 4.x, a direct in-place upgrade to version 6 was not supported. These environments required an intermediate upgrade to vSphere 5.x before proceeding to version 6. VMware’s upgrade compatibility matrices helped administrators plan these multi-step migrations, but the process still demanded significant testing and staging work before touching production infrastructure. Organizations that had maintained good documentation of their existing environments found the upgrade process considerably more manageable.
VMware updated its licensing structure with vSphere 6 to better reflect the new capabilities and deployment models it supported. The core editions — Standard, Enterprise, and Enterprise Plus — remained, but the feature sets assigned to each tier were adjusted to align with what customers needed at various scales. Some features that had previously been Enterprise Plus exclusive, such as certain networking capabilities, were made available in lower tiers, while new features introduced in version 6 were distributed across the editions in ways that incentivized upgrades.
The Essentials and Essentials Plus bundles for smaller businesses were also updated to support vSphere 6 capabilities, ensuring that organizations of all sizes could benefit from the new platform. For customers with existing licenses, VMware provided upgrade pricing that made moving to version 6 financially accessible. Understanding the licensing differences between editions was important for organizations planning vSphere 6 deployments, as the wrong edition choice could result in either overspending or missing out on required features.
vSphere High Availability received meaningful refinements in version 6, including improvements to how the HA agent communicated between hosts and how admission control policies were enforced. The new HA architecture introduced in version 6 made the feature more resilient and reduced the incidence of false HA isolation events that had occasionally plagued earlier versions. These improvements increased administrator confidence in HA as a reliable protection mechanism for virtual workloads.
Distributed Resource Scheduler also received updates that improved its ability to balance workloads across clusters. The DRS algorithm in vSphere 6 became more aware of network I/O utilization in addition to CPU and memory, enabling more holistic balancing decisions. When combined with the expanded scale limits for clusters — now supporting up to 64 ESXi hosts and 8,000 virtual machines per cluster — these DRS improvements made managing large environments considerably more efficient.
Security received significant attention in vSphere 6, with several features introduced to harden the platform against unauthorized access and configuration tampering. The integration of VMCA as an automated certificate authority reduced the reliance on self-signed certificates, which had been a long-standing security concern in many vSphere deployments. By ensuring that all components used properly issued certificates, VMware improved the overall trustworthiness of vSphere management communications.
Role-based access control was also enhanced in vSphere 6, giving administrators finer-grained control over who could perform specific operations within the environment. Audit logging improvements made it easier to track changes and detect unauthorized activities. For organizations operating under regulatory compliance frameworks such as PCI-DSS or HIPAA, these enhancements were particularly valuable, as they directly addressed requirements related to access control, encryption, and activity monitoring.
When vSphere 6 reached general availability, the response from the IT community was largely positive. Technology analysts praised the scalability improvements and the maturity of features like long-distance vMotion and multi-vCPU Fault Tolerance, which addressed real operational needs that had gone unmet in previous versions. Enterprise customers who had been waiting for these capabilities moved quickly to evaluate and deploy vSphere 6 in their environments.
Real-world deployment feedback highlighted some initial challenges, particularly around the new Platform Services Controller and the changes to vCenter Server architecture. Administrators who had extensive experience with earlier versions occasionally needed time to adjust to the new component model. However, the majority of feedback indicated that once teams became familiar with the new architecture, they found it more logical and easier to manage than the older model. VMware’s technical support and community resources played an important role in helping customers through the learning curve.
VMware vSphere 6 represented a turning point in enterprise virtualization that resonated well beyond the immediate feature announcements. It was a release that demonstrated VMware’s commitment to solving real operational problems at scale, and the platform improvements it delivered set the standard for what a mature virtualization infrastructure should look like. From the dramatic increases in per-host and per-VM capacity to the sophisticated management features like the Content Library and Platform Services Controller, every aspect of vSphere 6 was designed with operational practicality in mind.
The certification program that accompanied vSphere 6 had an equally lasting impact on the IT workforce. The VCP6-DCV became one of the defining credentials for data center professionals throughout the mid-2010s, and the VCAP6-DCV certifications elevated the careers of engineers who demonstrated the ability to work with vSphere at an advanced level. These credentials were not simply resume checkboxes — they required genuine knowledge and, in the case of VCAP Deploy, hands-on skills tested in live lab environments. Passing these exams signified real competence.
For organizations that invested in vSphere 6 deployments and encouraged their teams to pursue the associated certifications, the return was substantial. Certified engineers were better equipped to design resilient environments, troubleshoot complex issues, and take full advantage of the platform’s capabilities. The combination of a powerful platform and a rigorous certification framework created an ecosystem where technical excellence was both expected and rewarded.
Looking back, vSphere 6 also prepared the industry for the deeper software-defined infrastructure trends that would follow. Its emphasis on policy-based management, automated certificate handling, and flexible deployment models laid the groundwork for the hyperconverged and cloud-integrated environments that became dominant in subsequent years. The lessons learned from deploying and certifying on vSphere 6 remained relevant long after newer versions arrived, because the foundational principles it introduced continued to shape how VMware and the broader industry approached infrastructure design and management.