Installomator VS ProfileManifestsMirror

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

You can make custom profiles in Jamf using the same json imazing uses/same repo. This will give you access to all of the keys available in the software. I think the reason they say it’s not enterprise software is there is no central control like chrome or edge. https://github.com/Jamf-Custom-Profile-Schemas/ProfileManifestsMirror

If you are using Jamf, this custom settings json should help with the vast majority of what you are wanting to do.

It might be easier to use a custom settings json. Here is one from a source that Jamf featured on their blog last year.

You should look into using Custom Settings json files to handle this. Here's one from a Jamf recommended source that I use in my environment. It works really well, and it's much easier to understand at a glance than a plist is.

If you're using Jamf Pro, you may be better off using a Custom Settings JSON to apply these settings.

Are you wanting to completely disable it or just skip it during initial sign in? This custom settings json should help with the latter, and if you then restrict access to the "Screen Time" preference pane that should be a roundabout way to fully disable it.

Rather than putting the energy towards this script, you should start working on how to deploy the official one. All of the config settings are available now. If you are using Jamf, you can even use this custom settings json to handle like 90% of the work. The only major thing to know in advance is that the settings "KFMOptInWithWizard" and "KFMSilentOptIn" are looking for your tenant ID.

If you're using Jamf, this custom settings json should help with managing most of those kinds of settings.

One and done setup, though a Custom Settings json file can really streamline any modifications you have to do down the line.

I believe WebAppInstallForceList is the setting you are looking for. It looks like that is included in this custom settings json though I have not verified that it will work.