{"id":24338,"date":"2023-09-07T10:49:33","date_gmt":"2023-09-07T09:49:33","guid":{"rendered":"https:\/\/licensedashboard.com\/resources\/your-guide-to-navigating-the-vmware-vsphere-licensing-evolution\/"},"modified":"2025-04-08T14:29:32","modified_gmt":"2025-04-08T13:29:32","slug":"your-guide-to-navigating-the-vmware-vsphere-licensing-evolution","status":"publish","type":"post","link":"https:\/\/licensedashboard.com\/en-gb\/resources\/your-guide-to-navigating-the-vmware-vsphere-licensing-evolution\/","title":{"rendered":"Your Guide To Navigating The VMware vSphere+ Licensing Evolution"},"content":{"rendered":"
\n \n \n\n
\n
\n
\n
\n

\n Your guide to navigating the VMware vSphere+ licencing evolution <\/h1>\n \n \n \n \n \n <\/div>\n\n
\n <\/div>\n <\/div>\n <\/div>\n <\/section>\n\n\n\n\n\n \n\t \n\n\t
\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\tResource<\/span><\/span>\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t<\/section>\n\n\n\n\n
\n
\n \n\n
\n
\n \n
\n

7th September 2023<\/p>\n

Michaela Gray<\/p>\n

\n Blog,<\/span>\n \n <\/p> \n <\/div>\n \n

\n
\n
\n
\n \n

<\/h3>\n \n\n

In the world of IT infrastructure, licencing models have the power to shape an organisation’s operational landscape. VMware have adopted a per-core licencing model for its VMware vSphere+ suite, which means that subscriptions are more tailored to the specific needs of organisations, simplifying the management process. Discover everything you need to know about VMware purchase subscriptions within our handy guide.<\/span><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n \n <\/div>\n <\/div>\n\n

\n \"a\n \n <\/div>\n <\/div> \n
\n
\n
\n \n

<\/h3>\n \n\n

The shifting landscape of VMware Licencing<\/h2>\n

The most common licence these changes will be a consideration for is VMware vSphere. This is now available to be purchased as a new subscription known as vSphere+, or by upgrading your existing licences to subscription.<\/p>\n

vSphere+ can be purchased as vSphere+ standard or vSphere+. As part of the new subscription model, VMware have altered the licence metric from per CPU to per Core. This is a big change in how VMware will be metering the usage of vSphere, in the previous licencing construct, the acquisition of licences was based on the total number of CPUs that a physical host server would have. With the shift to Core-based licensing, VMware requires organisations to licence a minimum<\/u> of 16 cores per CPU.<\/p>\n

VMware customers going through the transition from CPU to Core based licencing have been granted the ability to purchase the minimum of 16 cores per CPU for the initial agreement. However, upon renewal of the agreement, the customer is expected to buy the difference, which is often a significant increase in subscription cost.<\/p>\n

Customers will not be affected by these changes until their renewal date has been reached. This extra time gives VMware users the opportunity to continue operating under the older processor-based licencing model until they are ready to transition to the new core-based model, while also reviewing how the change in licencing could impact you.<\/p>\n \n <\/div>\n <\/div>\n\n <\/div> \n <\/div>\n <\/div> \n <\/section> \n\n \n<\/div>\n<\/div>\n\n\n\n \n\n \n

\n \n
\n
\n
\n \"\"\n <\/div>\n \n
\n

IT and SAM news delivered straight to you<\/h3>\n \n \n \n
\n