autopkg VS ProfileManifestsMirror

Would it be Autopkg https://github.com/autopkg/autopkg or autopkgr https://github.com/lindegroup/autopkgr by any chance?

I’d recommend you look into AutoPkg (https://github.com/autopkg/autopkg). It can do exactly what you ask - check the repo for new releases, and download them. It can even package them up if needed, or customise the package for you. Depending on the MDM you use, and/out your scripting ability, you could even have it upload the package to the MDM.

AutoPkg (Terminal app, takes recipes from GitHub to build packages) https://github.com/autopkg/autopkg

Something fancier would be setting up an autopkg build box a + munki server to deploy applications like a real macadmin.

Autopkg https://github.com/autopkg/autopkg

If anyone comes across this with the same question I found a helpful utility is autopkg. https://github.com/autopkg/autopkg Instead of a simple notification, I created a daily job that runs an autopkg update on selected apps I care about and adds it to my Testing Manifest Munki Repo. The Manager Software Center app notifies me when a package has an update the next time the client checks in.

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.