Greetings Jamf Nation!Many organizations are likely running software
updates on their fleets this week, as well as with new Jamf Pro
versions. As a Jamf who knows a few things about macOS software updates
and their various nuances, I want to share a ...
Could you explain a bit more of what problem you're trying to solve? The
actions of renewing a push certificate and renewing MDM profiles should
not be related.Renewing a push certificate is an annual process, to
ensure Jamf Pro can send push command...
The restart command by the Jamf Pro API is documented here in the
context of managing kernel extensions. If you’re on macOS 11.3 or later,
you can also opt in with a “notify user” flag that makes the process
less jarring to a
user:https://docs.jamf.c...
That method of "automatic" can't take into account volume purchasing
licensing, and the preferred/default method of deploying Self Service is
manually with volume purchasing. You'll want to paste in the App Config
from the admin guide that includes t...
That's expected behavior with User Enrollment, as managed devices don't
share persistent identifier info like serial numbers to MDM servers for
privacy reasons.Because of that, user-based VPP licensing needs to be
used for those devices instead, whic...
@fredrik_virding - Using the MDM commands for the "Download & Update"
workflow uses an `InstallASAP` action, and can work fine. If a standard
user account is logged in, it's best to be on macOS 11.5 or greater
though (or log them out first,) as there...
