LabVIEW
labview license switch from community into professional
Solved!
@gy10c wrote:
I have used my personal computer to try the newest version of labview at home with the community version, no problem.
These days I need to use labview 2021 for my work, for which I do now get a academic license from my university. The newly installed labview 2021 is still showing it is a community version.
My question is: is there a way to force labview to use the academic license instead of picking up the community license?
May be it is just not a problem, so far I just use my labview without problem for my professional work. Yes, the license has an issue, but NI cannot sue me since I have the license purchased even though labview does not use it.
Thanks!
I wouldn't say, "Can't," but they probably wouldn't. That being said, you can't just deactivate one and activate the other?
@gy10c wrote:
This is a good idea to install academic version on local PC and community version on VM. Finally I may have to do this.
Seems like on my PC both the community and academic version use the same binary files and local files structure. The difference should be which license to use. I hope there is a easier way to switch the license.
Currently in my NI license manager, the community license is valid showing the labview is activated for both 2023 and 2021 version. The local license from my academic usage is also installed well. There is no way I can deactive any license, and there is no way for labview to choose a license as the user wanted.
Again I may end up uninstall everything and reinstall everything again just for the license.
Do the two different versions have different licenses - e.g., LV 2021 = academic, LV 2023 = Community Edition? If this is so, just use the appropriate version for each usage.
I'm not sure if the Community licensed version is exactly the same binary as the Commercial licensed one. The licensing mechanisme certainly is not the same. They run on the NI side on different license servers and have different account databases that get used. That is one of the reason that you have to use the same account to activate the Community edition than with which you downloaded it.
So if you registered an installation as Community version it is not as simple as just changing the license. The license backend is different and the most simple solution is likely to completely uninstall the Community version and to reinstall the Commercial version and activate it with the correct license. I suppose that this was not intentional but at the time they made the decision to release a Community version they likely had the choice between changing the entire existing licensing system to allow for the addition of a Community license or tack on a separate licensing system for Community specifically. The fully integrated solution would have likely cost more time and have the huge potential to seriously hamper the licensing of the Commercial versions until all the changes had been implemented, tested, verified and fixed. You do not want to cause such interruption to paying customers just to make life for the non-paying customers a little easier!
@rolfk wrote:
I'm not sure if the Community licensed version is exactly the same binary as the Commercial licensed one. The licensing mechanisme certainly is not the same. They run on the NI side on different license servers and have different account databases that get used. That is one of the reason that you have to use the same account to activate the Community edition than with which you downloaded it.
So if you registered an installation as Community version it is not as simple as just changing the license. The license backend is different and the most simple solution is likely to completely uninstall the Community version and to reinstall the Commercial version and activate it with the correct license. I suppose that this was not intentional but at the time they made the decision to release a Community version they likely had the choice between changing the entire existing licensing system to allow for the addition of a Community license or tack on a separate licensing system for Community specifically. The fully integrated solution would have likely cost more time and have the huge potential to seriously hamper the licensing of the Commercial versions until all the changes had been implemented, tested, verified and fixed. You do not want to cause such interruption to paying customers just to make life for the non-paying customers a little easier!
I only ever installed LV Community Edition on my computer and it says I can activate LV Pro. It says it is available for eval. However, I don't feel like potentially messing up the LV Community Edition licensing by uninstalling it and seeing if I can use LV Pro eval. I had enough of a hard time licensing LV Community Edition the first time around.
@billko wrote:
I only ever installed LV Community Edition on my computer and it says I can activate LV Pro. It says it is available for eval. However, I don't feel like potentially messing up the LV Community Edition licensing by uninstalling it and seeing if I can use LV Pro eval. I had enough of a hard time licensing LV Community Edition the first time around.
Yes the Community Edition license activation seems a bit troubled. The entire mechanisme isn't very transparent and consistent, so it is very easy to get it wrong if you take the wrong door first. Proper license activation is unfortunately quite a difficult problem to solve in any software, and there are many systems that all need to work together completely seamlessly before it works without trouble for the end user. The Community Edition being for free, makes it of course additionally hard to justify extra efforts to fix a process that is not always broken for everybody. It tends to make those support tickets keep moving to the end of the line of open items to fix.
