LabVIEW on VMs

[xxx2]

Hey everyone, I have a basic question but want to check if there are some alternatives. 

After the applications is build, the .exe is put on VM with multiple users. Do I need to put .exe for on every user account or is there some other possibility to put it in some shared folder so everyone can use it (SaaS or something)?
Since this is only the end build of application, is licensing necessary or not? Only thing to be installed on that VM is the right runtime engine?

I also saw a lot of talk recently about LabVIEW subscription model. Is this needed/valid in this situation? Would there been any advantages in implementing it?

[Ajskrim]

Hey xxx2,

When you build an .exe, you don't need to have LabVIEW license to run it. You do need LabVIEW Runtime, as you mention + modules/drivers, which your application is using. Keep in mind, that some of them may require a license even when built - for example Vision.

If have an application for all users, you can place it to Public directory and then have a shortcut on the public desktop as Bob suggest here:
Executable running under a different user? - NI Community

or install the application in ProgramData -> -> Start Menu as Hooovahh suggests here:

Install a LabVIEW application for all users of a system - Application Builder, Installers and code d...

Hope this helps.

[rolfk]

That's pretty independent of using a VM or not but a function of the OS you run in the VM. If you install a LabVIEW application from an administrator account for the Windows OS you run in there, it is installed as a global application and should be available to any user logging into that VM guest OS.

The LabVIEW runtime is royalty free but other runtime licenses may not be (e.g. Vision Analysis, Vision Acqiusition, etc).