Single User license with shared login

[NI_usar]

Hi,

I wanted to know which license type would work well for me. I have 2 computers in the lab and a couple of engineers who will be running labview on these computers. The computers have a shared login.

At one time only 1 engineer will be running labview as they have separate shifts. Also at a  time the engineer will be using only 1 computer. In this scenario, can I purchase a named user license ( as the login is shared) and have it installed on the two machines. I am just trying to find out if something like this is supported by named user license since it will not be used by two engineers concurrently or on two computers concurrently at any given time.

Thanks

[Bob_Schor]

A License is like a Contract, i.e. it is a (legal) agreement between the User and NI.  Anything we tell you is our opinion (since most of us do not work for NI) -- it may be "correct" (that is, it may be what NI would say if you asked them), but you have no way of knowing which opinion is "correct".

If you are really interested in the details of "what is legal" with your License, call NI, or send them an e-mail.  If you go to support.ni.com, you will find links and phone numbers.

Bob Schor

[altenbach]

The general purpose software license agreement can be found here and it spells out the differences quite clearly.

Basically, you want to designate a single "virtual" user named e.g. "LabVIEW programmer of ACME Inc." That has a special company user account and e-mail address registered with NI, while it is a different person depending on time of day. The named user license spells out "designated employee" that can be changed up to 4 times per year. Since you seems to be wanting to change it several times per day, there seems to be a license conflict. (I am not a lawyer!)

Can you explain what you mean by "running LabVIEW". Are they programming (i.e. writing new code) or are they just running a finalized LabVIEW programs?

If they are all writing programs, sharing a single login seems to be very ill advised, because of conflicts in setup (LabVIEW.ini, recent projects, MAX configuration, etc.). If they are just running LabVIEW programs, I would recommend to use the application builder that allows buidling standalone executables that don't require a LabVIEW installation.

I would recommend to talk to your local NI sales engineer. I am sure there is workable solution that makes everybody happy. 😄