Deactivation checklist

[bnz]

I'm curious if there exists somewhere a community-driven Google Sheet or so with some kind of vendor-specific checklist where and what should be deactivate prior to switching computers? Some vendors limit the amount of activations and you cannot deactivate any more once you switch the OS drive into a new machine, thus you'll sooner or later have to contact the vendor and ask for additional activations. To avoid this situation, it might be a good idea to orderly work through the deactivations beforehand.

I have started to build such a list for myself, but it has holes and some things I'm not entirely sure about. Thus I thought it might be a good idea whether something like this exists already and whether others possibly have such a list as well where it might make sense to consolidate.

Edit: I have consolidated a few comments from the other threads into my Google Sheet where I have collected stuff. I'm not sure everywhere. Feel free to comment the sheet to confirm and point out issues in the list.

https://docs.google.com/spreadsheets/d/ ... id=0#gid=0

[chagzuki]

I made the same thread a few months ago and in that someone linked to another thread they'd made which included a list.

[bnz]

Thank you for that pointer. I have found these threads.

[midi sentinel]

Could you link the thread(s) here as well?

[bnz]

There you go:

viewtopic.php?p=9047276
viewtopic.php?p=9005757
viewtopic.php?p=8993539
https://vi-control.net/community/thread ... ter.73806/

[xx JPRacer xx]

I checked those lists... I'd add Minimal Audio and Devious Machines. De-authorize in each plugins. I like your idea of a community-driven Google Sheet. Do it!

[bnz]

I have consolidated a few things above and posted the link in the first post. Check it out.

[Cuauhtli]

Hmm, Waldorf seems odd. Aren't they also licensed through iLok?

[Gamma-UT]

Hmm, Waldorf seems odd. Aren't they also licensed through iLok?

Waldorf used to be eLicenser, now it's C/R with a serial.

[mi-os]

What a nightmare. (the need for such a list)

I think you should separate iLok plugins since their deactivation just depend on the chosen activation method. This would make the list shorter and therefore easier to read.

[Cuauhtli]

Hmm, Waldorf seems odd. Aren't they also licensed through iLok?

Waldorf used to be eLicenser, now it's C/R with a serial.

Hells bells. They've used iLok. I have Largo and Lector and they were licensed through iLok. They're no longer in my iLok account, though I do have a couple of iZotope licenses for some reason.

[morphex]

This is a great idea and I think it's something that could be very helpful to the community. Personally, if a company is using c/r for authorization, then there should be a clear and easy way to deauthorize the plug-in so that you could authorize it somewhere else.

Something like a hard drive failure is even more frustrating when a bunch of licenses go down with it. So far, I've been pretty fortunate by planning ahead, but a centralized list with input from developers themselves would be even more ideal. It's a topic that we'll all face at some point, so it would be great to have a trustworthy resource to turn to.

[bnz]

What a nightmare. (the need for such a list)

I think you should separate iLok plugins since their deactivation just depend on the chosen activation method. This would make the list shorter and therefore easier to read.

Yes, I agree. It's only on issue if you authorize to the machine. Will do that.

[bnz]

I have merged the comments from VI Control into the list and separated out ilok in a separate column so that it can easily be filtered out if you have activated everything to a dongle and not the machine.

[Gamma-UT]

Hells bells. They've used iLok. I have Largo and Lector and they were licensed through iLok. They're no longer in my iLok account, though I do have a couple of iZotope licenses for some reason.

Because they were never in your iLok account.

Try looking in eLCC.

Largo-LCC-crop.jpeg