Recently someone asked me how you could handle getting users who are willing to test new software/policies/config profiles, etc, to self enroll their own computers without needing an administrator’s intervention or giving a user access to the Jamf Pro Server.
I happened to have a script I wrote a while ago that allows a user to do just this.
Recently I became aware that you can open Terminal (and Console) from the macOS Setup Assistant via keyboard shortcuts.
When you are in Setup Assistant, you can open Terminal or Console by pressing:
CTL + OPTION + CMD + T (for Terminal)CTL + OPTION + CMD + C (for Console)
Terminal will then launch as _mbsetupuser which is the user that Setup Assistant runs as.
Now that we have Terminal launched, what can we do with it?
In some Jamf environments the Tomcat webapp might need to be hosted on a single machine that is both accessible from inside an organization as well as externally on the public internet.
But what if you don’t want the Jamf admin console visible to the external world but still want to allow your clients to check in, enroll, or access the API? If you were in a clustered environment you could easily change the Limited Access settings for your externally facing webapp to something other than “Full Access”, but this isn’t possible on a single server setup.
Recently someone asked me how you could handle getting users who are willing to test new software/policies/config profiles, etc, to self enroll their
Recently I became aware that you can open Terminal (and Console) from the macOS Setup Assistant via keyboard shortcuts. When you are in Setup Assistan
In some Jamf environments the Tomcat webapp might need to be hosted on a single machine that is both accessible from inside an organization as well as
ProfessionalOh, hello . I didn’t see you standing there. As you may have guessed from the site name, I’m Chris Collins. Currently I am an Apple Platfo