App deployment forcing per-machine install

[trossiter]

I have recently upgraded to VL 14.2, and we are going through application rebuilds to get programs to connect to the server at the new version. Creating a new build number on an existing application goes smoothly enough, however, when building a brand new application, during the install process, it is forcing the application to be installed at a per-machine level instead of a per-user level. This in turn forces the application to be ran as an administrator in order for JIT updates to be attempted. The end users for these applications are not the administrators on their machines, and we did not have this problem in the past.

Does anyone know where this particular setting is found in the deployment tool? Or is it in a generated file somewhere in the application package that can be changed before installation?

[PatrickF]

Assuming you are running msiexec.exe with all the switches to automate the installation as much as possible there is now a ALLUSERS=1 which will install for all users
See the bottom section of https://docs.lansa.com/14/en/lansa022/c ... 9_0030.htm and https://learn.microsoft.com/en-us/windo ... i/allusers for more details

[trossiter]

That's...really dumb. Why was that change made? Is it possible to override Lansa's override? If so, can it be done without installing from the command line?
Also, according to the documentation, it says I have the option to install on a per-user basis when installing with administrative rights, which I have. However, that is not the case.

install_per_machine.png (10.5 KiB) Viewed 54077 times

During the install, it tells me that I have no choice but to install for all users, which then requires the application to run as an administrator in order to get updates correctly.

upgrade_failure.png (10.71 KiB) Viewed 54077 times