Hello! Any tips on how to deploy a windows app using MSI? The MSI needs elevated privileges/admin but I need to be able to install the software silently whether or not a user is logged in.
I tried a couple of msiexec commands, see below. MSI is uploaded in Meraki cloud storage.
msiexec /norestart /quiet /package "<full path to msi>"
msiexec /norestart /quiet /package "<full path to msi>" NM_ADDRESS_VALUE=255.255.255.255 REBOOT=ReallySuppress
Meraki MDM dashboard's Activity log does say "success" but the software is not installed.
You shouldn't need to be specifying the msiexec command. Check out this article.
https://documentation.meraki.com/SM/Apps_and_Software/Installing_Software_on_Windows_and_Mac_Devices
Thanks for pointing me to that link. Still did not work when I removed msiexec. Also, I completely removed the arguments still won't install. How do I tell MDM to install using the local admin user??
I *think* it installs it using the SYSTEM account - so no issue with rights there.
I think what I would do is get it working manually with the msiexec command yourself from the command prompt. When you get the right set of options and can install it manually you should be able ot come back to the MDM and then set it up from there.
Some things that have caught be before - installs getting blocked because of a pending reboot from another update.
That's what I did, I manually run msi. If I manually run using local user it's asking for admin. If I manually run using admin, it works fine. And yes restarted the computer several times.
What does the event viewer say?
No errors at all. No information/warning related to the install.
@iamHueMan wrote:MSI is uploaded in Meraki cloud storage.
What do you mean by this? We deploy the Meraki SM via group policy with the MSI without any issue. What tool are you using to deploy it?
@BHC_RESORTS I think what they want to do is deploy another app using the Systems Manager agent on Windows.
@PhilipDAth Aha! That makes more sense.
@iamHueMan Well, in that case, lots of data was lost in the S3 loss a while back - any chance the MSI you have predates that? Some of the files we had "looked" like they were OK, but weren't when we tried to access them.