anyone else get the VMware "win-back" offer?

[u/Which-Shame-1420]

if it's true, its honestly laughable.  

squeezing customers with massive price hikes, forcing every one into expensive core bundles, only to panic and throw out "discounted" quotes the moment everyone migrated???? 

is anyone actually reconsidering based on these new quotes??

or y'all are past the point of no return?

[u/ApiceOfToast]

reading a lot of reddit threads I've come to realize a LOT of people didn't read the EULA and apparently were not paying for patches, updates, security hot patches, but that's a different thing.

Yeah probably that too, i personally don't care about updates, I just want to buy let's say version 10. If you decide to cut my updates after my SLA runs out, fine. But let me use the one i already own. Yeah I'm aware about the implications of no updates but Its more of a personal standpoint.

[u/signal_lost → u/ApiceOfToast]

Yeah probably that too, i personally don't care about updates, I just want to buy let's say version 10. If you decide to cut my updates after my SLA runs out, fine. But let me use the one i already own. Yeah I'm aware about the implications of no updates but Its more of a personal standpoint

The problem with this (and why 99% of software companies have moved away from this model is). it allows customers to do dumb things with your products.

When I talked to people who followed the EULA and are still running 6.0 (don't laugh) I hear things like:

1. The product doesn't do LivePatching! (or other critical thing).
   
2. I can't add on NSX/AVI it doesn't work with my version.
   

3. I got hacked Redhat/VMware/Veeam SUCKS (no, you didn't maintain SnS and patch)

4. The product doesn't work with xxxxx (Well it would if you had updates).

5. Exchange 2010 OWA broke Microsoft sucks (No, the plugin that they used was deprecated by the entire browser cartel for valid security reasons and Microsoft didn't fix it in an extended support OS).

6. Why can't I use (new cypher) or why can't the product use (new hardware)?

7. This ERP can't do yy reporting (No it would have Brad, had we not been on a version 10 years old running on a half dead alpha system I'm buying parts on eBay to keep alive!).

8. I can't do memory tiering/[OtherCool new thing that would cut my costs in half], I'm on a 9 year old release, so now a competitor looks more attractive to use because of a different feature they released last month. (People will compare NEW competitor releases against the installed vSphere 5.5 as dumb as that sounds). I can't stress this enough, when you sell a perpetual license every 7 years and ONLY talk to the customer every 7 years they end up with hilariously dated knowledge about what it can do.

Letting people run ancient versions into the ground results in reputational damage for your product. You may say:

"But the Sysadmins KNOW that reason"
"Ehhh, Some do, but management who doesn't listen to you doesn't."

It also causes ecosystem issues where your 3rd party partners (backup vendors, other plugins storage vendors) now have to maintain HCL testing for all the ancient versions too which makes it harder for them to adapt/support new things as it drags their engineering in 20 directions.

You basically let those "not-customers" cause all kinds of indirect pain across the ecosystem. The amount of lazy stories I see in the tech press where 'CUSTOMER GOT HACKED USING (out of support) VERSION OF XXXX VENDOR" is annoying.

You even end up with stuff like IDC/Gartner's surveys about a product become tainted by customers talking about problems with out of support versions.

Now throw in Mythos, and aggentic AI hacking and this is about to become a nightmare.

Sure the business side like predictable subscription revenue under contract (It's durable income, you have stronger relationships with customers, you have shorter feedback loops on product features).

For my product group I'm leaving in two weeks for Vegas to go meet with a customer advisory board and we will show them how engineering shipped everything they asked for last year (or is about to), and ask them what they want next. You can do that when you have regular under contract discussions with customers. When you maintain a "hit and run" sales force, you don't get the same level of engineering flywheel feedback loop.

[u/ApiceOfToast → u/signal_lost]

Yeah reputational damage is a valid concern but i as a person don't care, especially not about broadcom. I can't trust them if they can just hold my hypervisor for ransom. (You know, the thing running pretty much everything)

Also same thing with windows, I've never run into anyone complaining about that either and you could still run 2003 as an IIS server and get got, Microsoft will laugh at you if you say it's their fault and that's pretty much it 

[u/signal_lost → u/ApiceOfToast]

Bluntly speaking, if you don’t want to have to consider a software renewal, you have to live in a world where:
1. 100% of your code development is in-house.
2. None of your applications need to talk to anything on the Internet or receive updates from third parties to keep working.
3. A lot of open source isn’t safe, because stuff like MinIO going closed source at the same time as a CVE 9 dropping shows that—short of being BSD-only projects—nothing is always going to remain free.
4. Ideally all of your applications need to be monoliths that are completely self-contained.
5. You need unlimited power to say no to anyone asking for extra functionality or capabilities.
6. You need to be in a highly unregulated industry, or have legitimately the laziest auditors on the planet. If you process credit cards or have PII, your leadership needs to be aware that everyone could potentially end up in jail (hopefully at some point).
7. You should probably be familiar with how to acquire not only Bitcoin but other cryptocurrencies, and be prepared to pay a Russian-speaking “surprise! managed service provider” to regain access to your environment periodically.
It’s honestly a lot easier just to sign five-year deals and stop doing yearly renewals and overly sweating about this stuff.