The old script MSUpdateHelper4JamfPro.sh provided by (which is what we're currently using - we haven't tried the new one. This is where we think most of the issues are occurring with people's deployments. MobileConfig seems to not be updated to the latest security settings that we've determined JAMF, and the AutoUpdate tools need.
With the release of macOS 10.14 (Mojave), there were a lot of security changes namely PPPC restrictions that caused the command-line MSUpdate tool to not be able to communicate with the Microsoft AutoUpdate Daemon, and JAMF not having the correct PPPC permissions to run and interact with everything that it needed to. GitHub repo to our modified script and MobileConfigs:
I imagine a lot of you are here to maybe see if this solution will work with possible issues you've been having on your AutoUpdating for Mac 2019, we've spent quite some time on it on and off, and I think we've come up with a solution that works well (at least in our environment).įirst off I'd like to start by giving credit to the people who've contributed to this for creating resources and utilities and providing the tools and scripts to make this work - And the countless hours of endless support given to the community.ĭuper51 a fellow co-worker of mine who helped immensely with the debugging and solution of this.Ĭarl Ashley for providing some useful documentation on viewing the MacOS TCC log to solve the PPPC violations that no one really knew were happening. Hello, fellow Mac Systems Administrators,
0 kommentar(er)
