Tag Archives: Apology

Autodesk remotely killswitches AutoCAD licenses – again

Following the AutoCAD 2019 rollout disaster, where subscription users found their AutoCAD 2018s were broken by an Autodesk licensing system meltdown, Autodesk CEO Andrew Anagnost issued an apology. He also assured customers on Twitter that it wouldn’t happen again:

While I welcomed that, I did have this to say at the time:

I don’t think such a guarantee is realistic, given that the nature of subscription software is to only work when it knows you’ve paid up. At least it demonstrates that the desire is there right at the top to try to prevent such debacles from occurring in future.

Autodesk watchers know that words mean little and actions are everything. I look forward to Andrew sharing news of the actions he’ll be taking to make good on his promise.

Back to the present. Does it come as a surprise to anybody to discover that less than a month later, Autodesk has again accidentally remotely killswitched people’s licenses? Again, not just the new release, but 2018 too. As reported on Twitter and www.asti.com:

After a couple of exchanges, the always-responsive people on the @AutodeskHelp Twitter feed came back with this:

So it’s fixed, but CAD Managers now have a bunch of work to do at their end to deal with a problem created at the Autodesk end. Somebody screwed up, they fixed it, another apology is issued, stuff happens, life goes on.  That’s it for this month, probably. But it doesn’t address a very fundamental problem.

Let’s go back to basics.

The primary function of a licensing system is to allow use of the product by legitimate users.

Everything else is secondary. If a system relies on phoning home and getting the required response from a remote system before you’re permitted to use the software you paid for, not just after installation but on an ongoing basis, then it’s fundamentally flawed from the user’s point of view. Yet that is the system that Autodesk has chosen to base its business on.

No amount of sincere, deeply felt apologies or it’ll-never-happen-again promises will alter the fact that Autodesk has put its own convenience ahead of the ability of paying customers to use what they have paid for. Will Autodesk change that state of affairs? I very much doubt it, in which case it’s inevitable that this kind of thing will happen again, whatever anyone might promise.

Andrew Anagnost apology for AutoCAD 2019 rollout disaster

Autodesk CEO Andrew Anagnost has sent an email to customers affected by the AutoCAD 2019 rollout disaster that acted as a remote kill-switch for users of earlier releases of subscription software. The email’s subject is We Missed the Mark:

Image credit: R.K. McSwain

Readers of this blog will be aware that Andrew and I have fundamental disagreements on where he has taken the company, but credit where credit is due. An apology was appropriate in this case, and Andrew stepped up and made one.

He has also stated on Twitter that it won’t happen again. I don’t think such a guarantee is realistic, given that the nature of subscription software is to only work when it knows you’ve paid up. At least it demonstrates that the desire is there right at the top to try to prevent such debacles from occurring in future.

Autodesk watchers know that words mean little and actions are everything. I look forward to Andrew sharing news of the actions he’ll be taking to make good on his promise.

Disaster in progress – Getting it wrong

No, not Autodesk getting it wrong, me  getting it wrong. In recent posts, I supported my arguments against Autodesk’s move to all-rental software with faulty evidence. As pointed out to me by several commenters, I completely failed to take deferred revenue into account. I would like to sincerely thank those who pointed out my error.* Although I included a disclaimer about not being a financial analyst, I should have gone further and simply not ventured into areas I am ill-qualified to cover. I got it wrong. I therefore offer unreserved apologies to Autodesk and my readers.

What now?

I have done myself a bunch of graphs that I think paints a fairer picture of Autodesk’s position, but there’s a reasonable chance I’m wrong about that too so I won’t be publishing them. Instead, In a day or two, I will remove the content of the offending posts (but leave the shell of the posts there to preserve the comments). I do this not to hide my embarrassment, but to limit the degree of undeserved damage to Autodesk. Feel free to copy/paste, take screenshots, etc. of the posts until then. Of course, it’s not really possible to delete things from the Internet, so if you ever want to relive the joy of seeing me get things spectacularly wrong, feel free to use the Internet Archive to do so.

What this doesn’t mean

This doesn’t mean Autodesk is off the hook with the rental thing. It may not yet be a financial disaster of the magnitude I argued, but the jury is still very much out on whether it will eventually succeed. Even if it does (and I still have very strong doubts – doing the opposite of what your customers want is rarely a winning long-term strategy), it’s still a grotesquely anti-customer move which deserves to be vigorously opposed. I will  continue to oppose it. I will continue to point out any faulty arguments that are used to support it. However, I will be much more careful to avoid using faulty arguments of my own.

* Autodesk could have also pointed out my error, but didn’t. Before I started commenting on rental I emailed Autodesk PR specifically encouraged them to point out any factual errors and/or seek a right of reply, but I want to make clear that isn’t what happened here. I have not backed off due to pressure or threats from Autodesk. Indeed, I have had no contact from Autodesk whatsoever in relation to my blog since it re-started. I continue to encourage such contact, but of course Autodesk is under no obligation to take up my offer.

ClassicArray Registration Service

When you register ClassicArray, you are supposed to receive an automated response with the registration code. I have not been able to get this working reliably, so for some customers I have been sending out the email manually. Personal circumstances dictate that I will be unable to do this promptly for much of April, so if you purchase ClassicArray and do not receive your code immediately, please accept my apologies in advance.

I will also not be able to be very active on this blog for much of April.