- How to install labview with disconnected license file software#
- How to install labview with disconnected license file Pc#
A year ago they opened for the possibility to
How to install labview with disconnected license file software#
The software company that I mentioned above, have after several years of customer complaintsĪlso reached the same conclusion.
How to install labview with disconnected license file Pc#
I would strongly support the idea of a dongle, to enable jumping from one PC toĪnother without having to uninstall/reinstall (or unactivate/activate via network) the software. I really hope that's not their intention. So if NI should make this impossibleįor me in the future, and I would have to uninstall/reinstall the LabVIEW softwareĮvery time I move from one computer to another, it would cause a hopeless situation. Work on more than one computer at the time. However, the license is only used on one machine at the time, cause I cannot Programming and automation, and I do NOT work on only one project at a time.
This is because I work full-time with LabVIEW But as they say, I have been there and seen how this can work.Ī potential problem is that I have installed my LabVIEW program on several computers simultaneously. Of course, this is not how NI plans it for their stuff to work. to activate a new license, the vendor in Calefornia has to manually confirm, to activate a license, the computer either needs access to network, or we have to run The license doesn't work any more, cause it is also tied to the computer name when one of our customers receives a computer from us, renames it for his own network, when a computer (HD) crash, basically we have to get a new license from the vendor,Ĭause the license is completely locked to the computer And that is a fact, even though we are paying for all the licenses We are using someĪnalytical instraumentation in our labs, with software that has been using this I have experience on this kind of licensing from before. Maybe many like me, are not completely aware on what's going on, and how it To my big frustration, and I have also been surprised that this not have beenĪn issue in this forum either, before now. I recently got aware of this new regime that NI is going to use on the licensing, I think it would be good if the user community voiced there concerns now before it's too late. I want NI to be profitable and continue to have money for improving LabVIEW, but I don't want this headache! If illegal use of LabVIEW is a real problem, are there other alternatives? How about an option to regulate licenses with a USB dongle? How many of them are using their work license at home for developing those cool tools? I also wonder how this will effect the OpenG community. The only easy solution is to buy a PDS or FDS for each new test system AND yearly subscriptions! That would really add up! There are times when I need to transfer my license between computers temporarily and they will not have network access for license sharing.
Their response was the LabVIEW is the only NI software product not using the license manager and to expect that future versions will use it.Īt my company we have enough licenses to be legal, but I can see where this will be a hassle. I had a meeting with NI sales reps yesterday and I mentioned Otto's remarks. WARNING TO ALL: I dread the day when NI attempts to force this license manager on LV users as well. In any event, anytime you want to install, uninstall, or move licenses around, you have toĭeal with these licensing issues (not very enjoyable when you are in the middle of a production floor in a different country trying to restore a system crash). It for a year) If you don't want to install and administer the license manager software, you can go to NI directly for each license. (Imagine getting a bill for unbudgeted license use, after you've already had You can even 'borrow' licenses you haven't purchased and NI will send you a bill for your extra license usage. This license file determines your license usage and it is given back to NI at the end of your license period. Install it on a PC, server, or whatever, along with a license file provided by NI. The TestStand development system will not run without it. Each TestStand development system must have a unique software key that is obtained from NI's volume license manager utility of from NI itself. Other bothersome issues include NI's volume license manager. In a response to my TestStand question, Otto Dalmandy mentioned following:
0 kommentar(er)
