shell-intune-samples VS Installomator

Deploy it via shell scripts instead, use the following for install template https://github.com/microsoft/shell-intune-samples, this is what I do for package where extra config is need after/before the deployment

If not, you can collect logs remotely using the instructions here: link.

Application deployment is Intune's weakest feature currently. If you have apps you want to push out as required then you can see if the native app deployment feature works for that particular app, or install apps via a script. I would recommend the second option, and Microsoft themselves actually have a good selection of sample scripts for doing so

Yep...been a problem for years! Best way is to script it. Put the pkg in a zip file and put it on Amazon S3 or Azure, etc. Then script it to install. Microsoft has some good examples on their github site. https://github.com/microsoft/shell-intune-samples/tree/master/macOS

i recommend you to refer to these samples: https://github.com/microsoft/shell-intune-samples/tree/master/macOS/Apps

Just learn to write simple bash scripts. Intune deploys them quickly and they work better then trying to package up some application. MS offer sample scripts which a monkey could rework for other applicatons. https://github.com/microsoft/shell-intune-samples

Yes, see Microsofts Intune Sample scripts on Github but the question is: should you?

GitHub - microsoft/shell-intune-samples: Sample shell scripts for Intune admins.

If you have access to a Mac, Installomator is a good encapsulation of shell scripting.

I used to use something like the above script but switched to using Installomator for all apps we use that it supports. It can do the initial install as a push or from Self Service, and then you can set it up to patch software as well. https://github.com/Installomator/Installomator

If you want to make things easy for your users and yourself, take a look at Installomator. It'll unlock a lot of nice workflows for your users, since you could put a specific title's install action available in Self Service and thats always gonna be easier than trying to track down the vendor's URL and finding the right download. It also means you don't have to repackage anything.

Munki is not an MDM and I recently learned there's this project called Installomator that might help.

Looks like you’re trying to update/work with version 4 but the installomator version is still on version 3. I’d suggest using build a label for musescore4

Installomator https://github.com/Installomator/Installomator