Skip to main content

vSphere Licensing Changing

VMware has just announced the way vSphere editions will be offered soon. Currently there are 6 SKU available which are:
  • vSphere Standard
  • vSphere Enterprise 
  • vSphere Enterprise Plus
  • vSphere with Operations Management Standard
  • vSphere with Operations Management Enterprise
  • vSphere with Operations Management Enterprise Plus
VMware will be reducing this down to 3 SKU which will be: 
  • vSphere Standard
  • vSphere Enterprise Plus
  • vSphere with Operations Management Enterprise Plus
As you can see VMware has removed the following:
  • vSphere Enterprise
  • vSphere with Operations Management Standard
  • vSphere with Operations Management Enterprise
So what options do I have if I have one of the editions listed above?

  1. Existing customers with vSphere Enterprise who have a valid Support and Subscription (SnS) will be entitled to an optional upgrade to vSphere Enterprise Plus at 50% discount off the upgrade licence prices. This promotion is valid from 10th February 2016 to 25th June 2016.
  2. Existing customers with vSphere with Operations Management Enterprise who have a valid Support and Subscription (SnS) will be entitled to an optional upgrade to vSphere with Operation Management Enterprise Plus at 50% discount off the upgrade licence prices. This promotion is valid from 10th February 2016 to 25th June 2016 
  3. Existing customers with vSphere with Operations Management Standard will not be impacted, as the component products of these bundles will still be available as standalone products. 
  4. Do nothing and you will be supported till 12th March 2020 where vSphere 6 support will end.

VMware has set a date of 30th June 2016 where you will  not be able to purchased any of the retired edition (exception cases will be considered) so if you intend to stick with do nothing then you may need to plan ahead for your growth of your estate so that you purchases the licences sooner.

As a nice sweetener and incentive for peoplpe to try vRealize Log Insight for vCenter. VMware is offering 25 Operating Systems Instances (OSIs) of vRealize Log Insight limited to monitoring logs from VMware vCenter Server, vSphere and vRealize Log Insight content packs for existing and new customers.

There is also some pricing changes to vSphere with Operations Management Enterprise Plus and vCenter Server Standard which you should speak to your reseller to get a better picture.

As you can see with this change in vSphere edition offering changing you will need to see if you need to upgrade or purchases more licences for your environment going forward.


Sources:

VMware Blog Announcement
http://blogs.vmware.com/vsphere/2016/02/vmware-simplifies-lineup-core-virtualization-offerings.html

Product Editions Offering
http://www.vmware.com/products/vsphere/compare.html

FAQ around pricing and upgrades
http://www.vmware.com/files/pdf/products/vsphere/VMware-vSphere-vSOM-Pricing-FAQs.pdf






















Comments

Popular posts from this blog

Rolling back a version of ESXi

There is an option in VMware where after you have performed an major upgrade of ESXi you can roll back to your previous version. The benefit of this is that you would not need to reinstall your ESXi and its configuration if you had issues with the new software. I had to do this on one occassion in my lab where I upgraded from 6.5 to 6.7 and my VMs would not run because the CPU was not supported in 6.7. Please remember if you are using ISO method to upgrade ESXi please ensure you select "Upgrade ESXi, preserve VMFS datastore". Selecting "Install ESXi, preserve VMFS datastore" does not mean preserving datastore means retaining ESXi as it will still do a clean install of ESXi. This method does not work for vSphere 7.0 as there are changes to the partitions on the boot device. Below are the steps to roll back to a previous version which is quite straight forward. As always perform an backup of your host configuration before you upgrade or rollback ( KB2042141 ). I have

Configuring ESXi 6 host to send logs to Syslog Server

In my previous post I talked about configuring VMware Syslog server for Windows which is installed and enabled by default on installation of vCenter 6 for Windows. I will now describe the basic configuration that is required on an ESXi 6 host to be able to send logs out to a syslog server using my vCenter as the example. 1) Navigate to your ESXi host within vCenter. Go to "Manage" tab and select "Settings" followed by "Advanced System Settings". Look for the settings "Syslog.global.loghost" and highlight this settings. Click the pencil icon to edit the configuration for this setting. 2) You can now add the host name or ip address of your syslog server/s. You can enter just hostname or IP address, use udp://hostname:514 or ssl://hostname:1514 to be more specific on the port and protocol to be used. If you have multiple hosts then you use the comma (,) to separate each server i.e. udp://192.168.0.1:514,udp://192.168.0.2:514 3)We n

Custom ESXi Image - ISO using PowerCLI

There comes a time when you have purchased a new hardware to run your ESXi software and discover that the installable base media provided by VMware does not include the drivers or the drivers are out of date. In the world of Windows (Plug and Play) it would discover the hardware and prompt you to provide the drivers so that Windows would install/update the drivers for the hardware. For ESXi if the drivers are not present during load time then the hardware will possibly not work. VMware uses VIB (vSphere Installation Bundle) as a way for vendors to distribute their drivers. To install these VIBs you can either use Update Manager or command line (esxcli). Now this is all good but it does mean you have to first install the base ESXi then use one of the steps above to install/update the drivers.   Some people might feel that it is OK to update the drivers using the above methods but what if it was the network card that was the new hardware and you needed new drivers. Without the net