Fix the Horrendous Licensing/Activation issues in LabVIEW 2018

[paul_cardinale]

This has been a problem since LV 2018 beta.  LabVIEW deactivates for no apparent reason; and it's gotten worse and worse as the year has progressed.  I now must reactivate LabVIEW every time I start it (your product support seems to be clueless).

My idea is that you design a Licensing/Activation system that behaves in a sane manner.

[crossrulz]

My first thought is that you have software that is changing something in the PC, most likely the MAC address.  At a company I used to work at, we had VPN software for a customer that changed the MAC address every time the PC was rebooted and then none of our NI software was activated due to the CPU ID changing.  The solution was to add an entry in the registry to make the license manager only look at the harddrive serial number when determining the CPU ID.

The other solution is to use a Volume License Manager so that your licenses are managed on a server instead of a local license based on the CPU ID.

[paul_cardinale]

 

 crossrulz 

 wrote:

My first thought is that you have software that is changing something in the PC, most likely the MAC address.  At a company I used to work at, we had VPN software for a customer that changed the MAC address every time the PC was rebooted and then none of our NI software was activated due to the CPU ID changing.  The solution was to add an entry in the registry to make the license manager only look at the harddrive serial number when determining the CPU ID.

The other solution is to use a Volume License Manager so that your licenses are managed on a server instead of a local license based on the CPU ID.

---

That seems unlikely as LV 2017 still works OK.

[paul_cardinale]

My first thought is that you have software that is changing something in the PC, most likely the MAC address.  At a company I used to work at, we had VPN software for a customer that changed the MAC address every time the PC was rebooted and then none of our NI software was activated due to the CPU ID changing.  The solution was to add an entry in the registry to make the license manager only look at the harddrive serial number when determining the CPU ID.

The other solution is to use a Volume License Manager so that your licenses are managed on a server instead of a local license based on the CPU ID.

[AristosQueue (NI)]

Paul: I flagged Licensing about your post, but many in R&D are already on Christmas vacation, so it may be a while. I don't have any help to offer myself. I recommend you contact NI support... an NI application engineer may be able to help you figure out why LV is doing this to you. I don't think this is a systemic problem -- if it were common, I'd expect customers to be banging down our doors to fix it.

Because this sounds like a bug and not a feature request (I assure you, entering license info on every launch is NOT a feature!), I'm going to close out this idea on the Idea Exchange. The Licensing folks will still be able to reply even after the idea is declined.

[Darren]

Declined for reasons listed in AristosQueue's post:

"Paul: I flagged Licensing about your post, but many in R&D are already on Christmas vacation, so it may be a while. I don't have any help to offer myself. I recommend you contact NI support... an NI application engineer may be able to help you figure out why LV is doing this to you. I don't think this is a systemic problem -- if it were common, I'd expect customers to be banging down our doors to fix it.

Because this sounds like a bug and not a feature request (I assure you, entering license info on every launch is NOT a feature!), I'm going to close out this idea on the Idea Exchange. The Licensing folks will still be able to reply even after the idea is declined."