The Hidden Cost of VMware Perpetual Support With No Path
Dell has told the English High Court it will claim £10 million from VMware if reseller Computacenter first succeeds against Dell. The customer is Tesco. The 2021 paper bought perpetual VMware licenses, upgrade rights, and an option to extend support. Under Broadcom, VMware sells subscriptions. A perpetual license with no named support path is not a product you can buy for an estate that stayed on that paper.
That’s the problem.
The parent pack is the VMware Broadcom stay vs exit page: perpetual versus VCF, the support path, portable VCF on AVS, and third-party cover.
This is not a grocery-chain story. It is what happens when a perpetual entitlement, a support obligation, and a three-hop channel all point at different legal entities after the vendor changes the commercial model. If you still run VMware on perpetual licenses, the question is not who wins in court. The question is whether you can walk into the next renewal with a defensible license position, a named support path, and a written answer for who is actually on the hook.
Four parties. Four stories. One estate that still has to run.
Tesco’s High Court action against Broadcom, VMware, and Computacenter sits on a 2021 contract. Tesco bought through Computacenter. Dell was the VMware distributor. Computer Weekly’s reading of the January and February 2026 filings is the cleanest public account of how that chain now argues with itself.
Computacenter filed against Dell on 8 January 2026. It says it cannot deliver the VMware software it was obliged to supply Tesco. Dell’s answer is a claim against VMware UK and VMware International: damages, specific performance, interest. Dell said it would claim £10 million if Computacenter succeeds.
Dell’s February filing, as Computer Weekly reports it, goes further than a pass-through. Dell signed the VMware Authorized Distributor Partner Program Agreement in June 2017. VMware terminated it on 22 December 2023. Dell says the original Tesco quote still ran to 2030, and that the distributor paper stays in force until outstanding orders are fulfilled.
On 3 October 2024 Tesco asked Computacenter to renew Production Level Support and the Tanzu subscriptions. VMware refused later that month. Tesco’s 11 February 2026 filing put the duty in one sentence: “VMware International owed to Tesco the obligation to supply the VMware Software and Support Services, via Dell and/or Computacenter.”
Broadcom’s position is the other door. It says VMware had no obligation to Dell to renew product offerings, and that the 2023 distributor agreement made any renewal subject to VMware’s written acceptance. It also says Tesco would not have an option to renew support, and Computacenter would not be obliged to procure one, if the relevant software or services are no longer available or have reached end of life. Broadcom has offered Tesco new commercial terms. Tesco has not accepted them.
Four stories. None of them is your license position.
“Owned” is not the same as “supported”
Look at your own VMware file. Most SAM teams still have a row that says “owned” and a risk register that says “covered.” Those two words describe different things.
A perpetual license is a right to keep using a version. It is not a right to patches, upgrades, or a vendor who still sells the SKU. Broadcom’s current licensing model is subscription. If your reports still collapse “license” and “support” into one status, you are reading a reporting layer, not a license position.
This is not a criticism of the teams building those reports. Traditional SAM tools collect comprehensively and answer slowly. They were built to prove completeness, not to tell you, this week, whether the thing you own is still something anyone will support. The gap is interpretation work. An analysis that arrives after the vendor has framed the meeting is a document. One that arrives during the meeting is a decision input.
Picture your procurement director, sixty days from a VMware conversation. The vendor walks in with a subscription quote. Your file says perpetual. Support is past or close. The reseller is not the legal entity that signed the original distributor paper. Your CIO wants to know whether you can stay, whether you have to move, and what the number is either way. If that answer takes three weeks of specialist reading, you have already lost the framing of the meeting.
Once support stops selling against perpetual paper, the license you already paid for does two jobs. It keeps the lights on. It also forces the conversion conversation. FinOps sees a run-rate. SAM sees an entitlement. The vendor sees a subscription. Those views only reconcile if current deployment, current entitlement, and a written support path sit in the same pack.
The channel is not your insurance policy
The partner who invoiced you is not automatically the party who can still deliver. Computacenter is in the case because Tesco bought through it. Dell is in the case because Computacenter bought through Dell. Dell is now arguing that VMware still had to fulfil an outstanding quote. Broadcom is arguing that end-of-life products cannot be compelled. That chain can break at any hop: a SKU the vendor no longer sells, a 2023 distributor termination, reseller language that obliges a message rather than a delivery.
If your next audit or renewal assumes “the partner will sort it,” you are making Tesco’s problem your operating model. Vendor, distributor, and reseller can each point at the next party. That is how a multi-tier channel behaves when the SKU at the top of the chain disappears. Your job is not to pick a side in court. Your job is to walk in with your own numbers, tied to the contract in front of you, before someone else’s number becomes the default.
What to lock before the next VMware conversation
Do this in the next thirty days, as a decision pack rather than a project.
| Step | What you produce | Why it changes the meeting |
|---|---|---|
| 1. Reconcile deployment to entitlement this week | Current count by product and version, matched to license, upgrade rights, and support extension | End-of-life arguments are version-specific. Tesco’s 2021 deal bundled perpetual licenses, Tanzu subscriptions, and a support option through year nine. Yours may not. |
| 2. Name the counterparty in writing | Vendor, distributor, reseller: who took the order, who can still sell, what each hop must do on a renewal request | Dell, Computacenter, and VMware are each describing a different duty. Name who fulfills yours before the meeting. |
| 3. Separate “owned” from “supported” | A one-page support path: vendor support, a documented exception, or a conversion. No third status called “the partner is looking into it.” | Broadcom’s court position is that products that are no longer available, or at end of life, cannot be compelled. If support is the lever, cost the lever. |
| 4. Walk in with your number first | Two paths priced on your estate: stay on perpetual with a named support answer, or convert on your deployment | Broadcom has offered Tesco new terms. Tesco has not accepted them. Have your number first. |
Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is no, you do not have a license position. You have a library.
The decision layer, not another inventory
You already have discovery data and contracts in a share drive. The gap is not another inventory. The gap is turning that estate into a decision: what is deployed, what you are entitled to, which support path is still live, and what should happen before the next vendor meeting. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. Host topology from RVTools or vCenter already lands in the data sources you run, so the pack can match what is deployed to what the contract still grants.
If you are heading into a VMware renewal or an audit and your current tools still need three weeks to turn “owned” into a decision, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.
The question to walk in with
Do not let the vendor frame this as “perpetual is over, here is the subscription.” The right question is: what are we actually running, what does the contract still grant, who is obligated to fulfill a renewal request, and what does conversion cost against this estate rather than a list price. That is a data question, not a sales question.
Tesco is litigating a support path it says it already paid for. Broadcom is selling a different commercial model. The court will sort the liabilities. You still have to run the estate. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.
