jonjonHi,
Just a heads up, a customer went through the disabled network adapters error message and couldn't run some of the provided command lines to fix it. He contacted Intel who confirmed that this is a bug in their driver, and is waiting for a fixed release. See the whole thread here: https://communities.intel.com/message/557732
Hopefully, LimeLM could be enhanced and be more tolerant to avoid such problems in the future.
Thanks.
We can't fix broken drivers. We bend over backwards to workaround broken and misconfigured machines. However, if the machine is too broken or too misconfigured then the only option is to return an error code and give them instructions on how they might fix their machine.
For example, this FAQ: https://wyday.com/limelm/help/faq/#disabled-adapters
Notice that 3rd sentence in it tells customers to update their drivers.
jonjonHi Wyatt,
I have already read your comments on this matter but unfortunately, customers often answer that only your licensing system is problematic and they do not have such problems with other software. So you must do something wrong.
Also, in that case, there are no drivers update available to this date: a user with a perfectly working and up to date computer could be prevented from using a legally paid software indefinitely due to a driver vendor not updating its drivers... Thankfully Intel seems to be working on this case but nobody can say that this will happen with all vendors and hardware.
Anyways, you are now aware that some Intel driver might be problematic with your licensing system. Hopefully, this will not affect more commonly used Intel networking cards in the future or this forum and your support e-mails will be full of unhappy customers.
In TA 4.1 (out soon) we'll have a new error code, TA_E_BROKEN_WMI for cases where TA can't read the WMI because of corruption. And in the instructions we spell out exactly how to fix this type of error:
https://wyday.com/limelm/help/faq/#fix-broken-wmi
We wrote that FAQ before 4.1 is released because (a) we figured it would be helpful and (b) it should be something customers try.
When 4.1 is released, and you get that error, you can either choose to link them to that FAQ or give them "clickable actions" that do the same as that FAQ describes. This is one of those things we chose not to automatically fix because it's more "intrusive" that other fixes to customers' configurations.
Anyway, like I said, we bend over backwards to fix customers' problems and other companies' problems.
