Plain Virtualization

This brought to my attention thanks to my colleague, Tessa Davis . Previously I mentioned on the different editions of vCenter here .  I did mentioned about the limitation of vCenter Standard and Foundation used to manage Essential and Essential is not possible due to End User Licensing Agreement (EULA).  However starting from vCenter 5.0 Update 1, this EULA enforcement is also a programmatic enforcement.  If you refer to vCenter 5.0 Update 1 release notes here , you will see the below: vCenter now enforces restrictions on which vSphere editions can be managed by vCenter With this feature, vCenter Standard and Foundation is disallowed from managing vSphere Essentials and Essentials Plus host editions. This is disallowed per the EULA already, but was not programmatically enforced until now. The exception to this rule is the ‘Essentials for ROBO’ edition. This is still allowed per the EULA and as per the programmatic enforcement. Furthermore, it is also enfo...

Have met some customer who are tight on budget and is on Essentials or Essentials Plus. There are some confusion with the packaging of the vCenter editions and I would like to clarify some of this with some of the links around VMware sites for easy understanding. Essentials or Essentials Plus are bundled with vCenter Essentials while vSphere Standard, Enterprise and Enterprise Plus is often quote with vCenter Standard. So what does this mean?  With the different vCenter Edition, there are some hard limitations.  If you refer to my vRAM entitlement post here , I have mentioned that there is a hard 192GB vRAM entitlement and limit to 3 hosts to one vCenter for Essentials and Essentials Plus.   vCenter Essentials bundled ONLY in vSphere Essentials or vSphere Essentials Plus kit is limited to manage hosts up to 6 CPUs or 3 hosts whichever comes first.  This is due to the limitations from this vCenter edition. Also with vCenter Essentials, there is no linked mod...