When I run this script as USER, it don't install because it ask for high permissions.
when i run as SYSTEM it does not install properly,
but if i run as Admin it installs.
The point here is, with Intune I am only available to install as System or User.
Another point here is, when i try to install manually in the middle of the installation it ask me for high permissions and it creates a dynamic MSI installer on the folder C:\Windows\Installer.
The best solution here would be to fix the MSI, or berate the vendor to do it, so that it installs in user context without admin rights, or when run elevated as system.
Is there a public link to the MSI available?
Also, you do not need to supply -ArgumentList with /qn like that - we add that by default along with REBOOT=ReallySuppress, so effectively you just took away the REBOOT property, leaving your machine open to an unwelcome instant reboot if the files were in use.
There are many things that could be at play here, firstly check if ALLUSERS is set to 1 or 2 in the Property table, and if not, set ALLUSERS=1 via the -AdditionalArgumentList parameter. Then you need to figure out if the add-in is registered via the Registry or the CustomAction table. If you need to make edits there, you can use Master Packager or similar to create an MST file.
Yes, i added the property ALLUSERS = 1 and i could install it as SYSTEM.
Then another error shows up when i tried to open any excel.. like .NET’s file handling when trying to access the workbook path