Allowing to Disable Network Adapter OptionSolved

After 6-7 products and tens of thousands of activations with Turbo.Activate, I'm starting to realize that the Network Adapter requirement is starting to be a tech support nightmare. Yes it's more secure, but if someone wants to crack it, they can very easily with our without this as an identity.

Would you consider making a flag or switch to not make this mandatory for authorization and just use all of the other system information for an identity?

Use the latest version (4.1.x). It has a new error code for broken network adapters (TA_E_BROKEN_WMI) that you can automate a fix for. See our FAQ

Regarding not reading the network adapters at all, no we wont support that. See the FAQ. Customers that use modern Windows (8, 8.1, 10) wont have any problems. Customers that use Windows that Microsoft will no longer support in 6 months (7 and older) will need to actually enable their network adapters once in a while. Again see the FAQ.

We tried a flexible approach with TA 3.x where we only read enabled adapters. It was a disaster. It increased false positives and false negatives.

To sum up:

1. Use the latest version of TA.

2. Provide good 1-click solutions to your customers problems (see the FAQ)

Can you please post a link to where that 1-Click option is to repair network adapters?

#1. Use the latest version of TurboActivate. This is critical.

#2. For TA_E_ENABLE_NETWORK_ADAPTERS, run your app as an admin (i.e. have a button that relaunches your app with "elevated" credentials -- google for examples in your programming language of choice).

See the FAQ, it explains this: https://wyday.com/limelm/help/faq/#disabled-adapters

#3. For TA_E_BROKEN_WMI, run your app as admin and run the 2 "mofcomp" commands described in the FAQ: https://wyday.com/limelm/help/faq/#fix-broken-wmi

So, basically, you created a button which launches your app as admin and whether the error code is TA_E_ENABLE_NETWORK_ADAPTERS (in which case you do nothing but launch your app as admin and nothing else -- TurboActivate handles the details as described in the FAQ) or the error code is TA_E_BROKEN_WMI in which case you run the 2 mofcomp commands as described in the FAQ.

Reply
Discard post