Dear Avid,

I have asked this in the past but I want to bring this under your attention again as my frustration with this issue is getting bigger and bigger.

First of all, Microsoft in all their wisdom decided to make the network card binding order, which is network card 1, 2, 3, etc... , dynamic in windows 10 without control or an easy view of the nic binding order. As Avid Link (and previously application manager and license utility) creates a device ID which is propably based on the MAC address of the first NIC, the device ID changes when the binding order changes. 

On machines with a single wired network card this isn't an issue of course, but almost every workstation (and server) on the market today has 2 or more Nic's.

The past 1-2 years things have become increasingly more unstable. I'm not saying Avid is causing these issues. I'm actually not 100% sure who is. All I know is that Microsoft, HP, Dell, etc.. (typically Intel) are more frequently including bios updates and new nic drivers in windows update and these can go as far as windows detecting new network cards and loose existing ones causing the binding order and ip settings to get messed up.

But lately simply plugging in a cable in the second/other nic on a workstation that was activated and working and removing it later can cause activation to fail from there on or deactivation can also fail with the servers saying they do not know this device while MC still activates. Moving cables and network settings between the nics sometimes helps. Normally I always see the device ID change in Avid link when doing so, but lately this can also stop as if the device ID shown is cached. More often then not activation will keep failing from there on and support needs to be asked for a manual de-activation which they always do including deletion of the usual files.

I feel I am almost forced to copy paste the device ID during intial activation to sustain my sanity and be able to trace if a device ID changed, after something as simple as a restart, windows update or (temporary) secondary network connection.

Everybody understands securing your software against piracy is important, but is it really not possible to check the MAC addresses of all available nics, connected and unconnected (not deactivated) in a system and create device ID's for each MAC address so Media composer, Protools or any other product (Mediacentral, Airspeed, etc..) activate with any of the network cards used on a machine or whichever network card Microsoft wants to designate as the first network card?

Thank you. 

Dear Avid,

After an MC activation related support call I spend 2 hours with MC + Avid link finding out if something has changed and it has!

In the past moving network cables between nics on Windows 10 machines would result in the Device ID changing and MC activating when the 'right' nic was used. This is no longer the case on Windows 10 21H1 in combination with Avid Link 2021.6.1.

I can't say when, date or version, this change occured, only that it did and I have now reproduced this on 2 systems. As usual I have opened a case and am sure Avid support will be able to quickly solve the issue.

However, I believe having an unpredictable license activation method is a risk nobody benefits from. So if any of the Customer advocates read this, please confirm if and what changes have been made (could be Windows 10) and look into what can be shared in public or with your ACSR's so we can have better knowledge on how to prevent activation failures on workstations and servers with multiple network cards.

Thank you.   

And the story continues

On Avid Link 2021.6.1, so not the latest version, on HP z8. Media compser activated and running for 3 weeks using intel I219LM connected to Nexis E4. Other nic not used.

MC all of a sudden does not activate. Multiple restarts make no change. Device ID copy pasted in notepad file.

Check both Nics. The second nic X722 is disabled. I enable the nic and as expected it shows the red cross that no cable is connected. But MC now opens, also after several restarts and device ID has changed. 

So Avid Link/MC now (also) uses the mac address of a non connected nic. 

Yea, we constantly have to email support to deactivate our license because of this stupidity.

Avid Link is horrible.

If Avid expects people to get off dongles, then Avid Link would need to be significantly improved. Including administration.

Guys... Seriously...


1) Avid Link is not the cause of this.  The old licensing server process Avid initiated for Media Composer 8 is what you're talking about here, not the Link desktop app.  Link is merely the "holder" for the buttons that port you through to the licensing and activation.

2) Avid already has fixed this. It's called Cloud Licensing, and Marianna and I have been posting about it constantly. It specificaly fixes all of this. 

We launched it publicly last year. You'll need MC 2021.12.9 or later, and Avid Link 2021.6.1 or later.  (It is hard-coded into the Media Composer app itself, as well as the Avid Link app itself, so going back to older versions would be impossible to do.)

FAQ is here: https://avid.secure.force.com/pkb/articles/en_US/faq/Cloud-Licensing-FAQ?fbclid=IwAR3PfQOPBvIIHxM6of6YpwODbwYhuOZaM1NrtPlOy623hw_XrHskAq_TdtI 

In-depth blog about it here: https://www.avid.com/resource-center/avid-media-composer-in-2022-lets-talk-licensing 

If you're having any specific problems, I'll be happy to get them into official tech support Case Creation. Email me at [email protected] and I'll get someone on it quick.

Jeroen, I have copied your post and shared it internally. You can email me oif you want, and we can get a specific case going for it. 

Requiring 2021.12 makes it DOA for us. Overwhelming majority of our clients request MC 2018 right now. 

Yep - I understand that 2018 users are still out there and strongly loving it. I myself still have two systems running it, and work with a few facilities that still have old Flip Factories and require the QuickTime (pre-UME) engine for exports. This is despite it reaching end-of-development, and not supported on any macOS newer than Mojave. So I get it.

Also note that perpetual licenses and dongles are still honored, still available for new purchase, and still supported for upgrades and previous purchases.

If you cannot upgrade Media Composer to take advantage of all the Cloud Licensing fixes, then I still strongly advise at least upgrading Link. Even if a facility is requiring Media Composer 2018 (hopefully 2018.12.15 because it has the most bug fixes and feature-adds), they should be using the latest Avid Link version 2022.5.1. Running old versions of MC does NOT mean running old "matching" Application Manager or Link versions is a requirement or even a good idea. Running any licensing app from four years ago means you will not have access to four years worth of bug fixes from our licensing and activation teams. 

Chris,

In my case most users are also using MC 2018.12.15 with Avid Link 2021.6.1 or up. But I think my problem isn't limted to versions used, their problems or the new MC & cloud licensing potentially fixing them.

My problem is directly related with my sanity.

All jokes aside, of course Avid does not share the algorithms by which Avid creates a device ID out of the hardware specs, typically Mac addresses. And also not how to read/debug the files created in the Licenses, SWL and application manager/Avid link cache folders. It is 100% understood that all this info could be used for piracy purposes.

But not sharing any info on how it works, so your users, not to mention your resellers/ACSR's, have an idea about the do's and dont's of licensing, while Microsoft, Intel, HP, Dell, etc... do 'their thing', isn't helping either.

Add to this that the subscription renewal emails say:

From: [email protected] <[email protected]>

Title: We’ve successfully processed your recurring subscription payment

Text: Hi <customer name>,

We've processed your recurring subscription payment for Media Composer Perpetual License Crossgrade to Media Composer | Ultimate 1-Year —woohoo! We're excited to be a part of your creative process!

Sincerely,

Your fellow makers at Avid

ps. Want more creative power—free? Connect with the Avid Community! Ask questions, promote your work, and find out what’s new with other creatives using Avid to power their passions. It’s even easier to connect if you download Avid Link, our free app supporting makers looking for collaboration, inspiration, or just a place to share their awesome skills.

Important

Due to a change in licensing for a third-party component, your subscription will  only be able to run Media Composer 2018.9 or higher. Please click here for more information. 

For each susbscription you receive a seperate email. No system ID mentioned, no payment code, no related invoice nr. Could you provide any less info?

I'm not doubting the new cloud licensing works better, but your whole user base has nothing else than your word on it. There is, as far as I know, still no technical info why things are now better. Instead we are ONCE AGAIN faced with undocumented behavioral changes of the DeviceID creation and its consequences, spending time trying to find out why, how, etc... contacting support who reset, no questions asked.

It's just too fragile and lacks in information.

I thought it was time to bring this old thread back.

The new cloud licensing was supposed to improve the never ending problems with activation and to some extend it has. The ability in Avid Link to use a license it thinks is being used on a different machine helps.

But on some machines, until now those with multiple nics, when activation fails, it results is a message saying: This license is activated on the machine with hostname: <hostname>. Do you want to activate it on this machine? Which is the exact same machine with the exact same hostname. I'm not sure but assume Microsoft + Avid Link still can't decide on which Nic and Mac address to base the device ID on.

Furtermore Avid Link with cloud licensing introduced another requirement on some systems. Some need to connect to the license server at least once a week to stay activated. And it seems Avid forgot to update this knowledge base article.

https://avid.secure.force.com/pkb/articles/en_US/FAQ/Avid-Link-Networking

with the new ports needed for cloud licensing. The combination of both costing me another 6 hours of troubleshooting with the IT dept firewall admin of one of our customers trying to figure out which Cname's/URL's/IP's and ports Avid Link now uses.

Avid, it could be I'm getting old and grumpy..., but the licensing troubles in 2022 have gone from bad to worse. Mediacentral cloud UX, Nexis F series, Mediacentral production, command, capture, production services, etc... upgrades. The majority now need days/weeks to sort mistakes out with support and sales. You present (Avid link) cloud licensing as the new method that is going to sort things out but with the underlying chaos not addressed it is just not going to work. 

PLEASE, get the licensing architecture/design and administration organised.   

Did you ever get a good solution for this issue. We've recently gone over to software activation losing our dongles. I wish I hadnt.

One of our systems constantly deactivates. Whether its cloud based or node locked.

Node locked worked the best, that lasted a couple of weeks, but now even that on a daily basis gets upset.

Every time I now have to get avid tech to reset my license.

So frustating.

Hi AntCaladine

No I have not. The licensing architecture, Avid link, traditional activation or the use of cloud licensing keep producing these highly frustrating situations where some systems fail to activate after trivial changes to that system. Numerous cases, mails, threads including this one have not resulted in a rock solid activation process.

That said, it's not as bad as it was but Avid simply seems to refuse to invest in making changes to the licensing process like multi-nic support. It is as if Avid does not care anymore about us wasting our time = money and our frustration.

Have you tried Offline Activation? I've used the Offline Activation method to get around other issues of forced deactivation. The disadvantage with Offline Activation is you cannot remotely deactivate a license. But, if this is a static, never moving license, it's the better route.

Jeroen van Eekeres:

Dear Avid,

I have asked this in the past but I want to bring this under your attention again as my frustration with this issue is getting bigger and bigger.

First of all, Microsoft in all their wisdom decided to make the network card binding order, which is network card 1, 2, 3, etc... , dynamic in windows 10 without control or an easy view of the nic binding order. As Avid Link (and previously application manager and license utility) creates a device ID which is propably based on the MAC address of the first NIC, the device ID changes when the binding order changes. 

On machines with a single wired network card this isn't an issue of course, but almost every workstation (and server) on the market today has 2 or more Nic's.

The past 1-2 years things have become increasingly more unstable. I'm not saying Avid is causing these issues. I'm actually not 100% sure who is. All I know is that Microsoft, HP, Dell, etc.. (typically Intel) are more frequently including bios updates and new nic drivers in windows update and these can go as far as windows detecting new network cards and loose existing ones causing the binding order and ip settings to get messed up.

But lately simply plugging in a cable in the second/other nic on a workstation that was activated and working and removing it later can cause activation to fail from there on or deactivation can also fail with the servers saying they do not know this device while MC still activates. Moving cables and network settings between the nics sometimes helps. Normally I always see the device ID change in Avid link when doing so, but lately this can also stop as if the device ID shown is cached. More often then not activation will keep failing from there on and support needs to be asked for a manual de-activation which they always do including deletion of the usual files.

I feel I am almost forced to copy paste the device ID during intial activation to sustain my sanity and be able to trace if a device ID changed, after something as simple as a restart, windows update or (temporary) secondary network connection.

Everybody understands securing your software against piracy is important, but is it really not possible to check the MAC addresses of all available nics, connected and unconnected (not deactivated) in a system and create device ID's for each MAC address so Media composer, Protools or any other product (Mediacentral, Airspeed, etc..) activate with any of the network cards used on a machine or whichever network card Microsoft wants to designate as the first network card?

Thank you. 

Hi Jeroen,

I logged a feature request about this scenario to improve the licensing experience.

For reference the feature request number is MCCET-5380

Thanks,

Ajay

Thanks Ajay,

Please update this thread if you receive any update from the development team(s) if they decide to implement (or not) my feature request.

Jeroen

Here's a link that avid support sent me yesterday for setting priority for multiple network cards.

https://avidtech.my.salesforce-sites.com/pkb/articles/en_US/How_To/How-to-change-the-NIC-card-binding-order-on-Windows-10

Its too early to tell, if its worked for us, as we only chnage the system last night, and on boot up this morning I had to reactivate. (it seems to be if the suite has been off for several hours it trips up). We've noticed that when its got upset, it changed device id in avid link. Its going between two different IDs (assume each network card)

So fingers crossed tomorrow it stays licesned. I'll update tomorrow.