The EPP is aimed at mid-level customers and offers both better discounts and greater flexibility, without the complexity of more robust agreements. To do this, it is a token-based licensing program, i.e. customers buy “tokens” to be reserved for the use of VMWare products instead of getting points after purchase As in VPP. In addition, it provides access to future upgrades to ensure customers can receive “the latest and largest” VMware products. However, EPP is limited to customer-based customers in the region, not global customers. The menu of VMware licensing agreements is relatively simple, as there are only three major licensing agreements: VPP, EPP and ELA. Below is a brief overview of the three, starting at the bottom with low expenses/customer seats and ending with the complex enterprise caliber agreement. A comment about my previous article on the metric change of the VMware processor prompted some thoughts – and this article. It was a big point that VMware and ELA contracts prevailed over all other software terms, and I noticed that it was worth deconstructing VMware`s chords to correctly interpret the chain and ranking. Understanding how the agreement and all the elements fit in is the key to understanding the VMware license and your rights. The enterprise licensing agreement is the ideal contractual agreement that has been developed specifically for global customers.
It offers attractive financial and operational benefits that are not available in the transactional product agreements between VPP and EPP. With ELA, customers can obtain VMware product licenses for a period of time, with a fixed price throughout their lifecycle and a fixed annual fee. “VMware can provide you with maintenance versions, secondary versions or main versions as part of a support and subscription contract. If you install a version that VMware provides, the version of the product guide published on www.vmware.com/download/eula applies to that version. A perfect, rich piece! Thank you for exchanging valuable information. This agreement consists of this basic agreement, the conditions contained in the addendum of the product attached to it and the applicable guidelines. In the event of a conflict between the conditions set out in the basic agreement and the conditions set out in the addendum to the product, the conditions of this addendum are checked. The second clause he considers in the CLA is the definition of “Order” which is defined in paragraph 1.10: you can see here a very clear statement on the emphasis that VMware placed on the product manual. If you think back to the previous article, you can already see what it means.
Since VMware has changed the definition of the cpu metric contained in the product manual, this clause in the VMware ELA gives the right to impose this change on ELA customers. Of course, it is quite possible that you negotiated as a customer in your ELA an exception to this order. But such exceptions are rare and in more than a decade of working with clients on theirs, I`ve never seen one. It is also interesting to note that the product guide contains a very similar order of classification. This does not necessarily apply to securities such as vSphere. If you don`t need additional hosts until next year, it`s not wise to buy more hardware just to run the licenses at an early stage. This is very important for multi-layered software such as vRealize Operations Manager, NSX, new SRM license and others.