What are Extension Attributes? Why were they added to Jamf Pro and why
do they matter? These questions, and others, will be answered in this
short post. Extension Attributes can be a powerful tool in the tool belt
of the Jamf Pro admin, and we will d...
In large enterprises and organizations with thousands of computers, it’s
often necessary to break up software deployments into more manageable
groups. Need to push a configuration profile out to 5,000 devices? You
might want to break that into chunks...
I'm looking for a method of managing the home page setting in both
Firefox and Chrome via Configuration Profile. I know for Firefox this
can be managed using CCK2 to generate an autoconfig.zip file and then an
AutoPkg recipe to create a Firefox insta...
I am in the middle of deploying a centralized Jamf Pro instance for a
large disparate organization. We're talking 5 business units with
multiple sub-organizations, ultimately leading to well over 150
different Active Directory forests with no trust b...
You cannot use an Enrollment Customization with an SSO option. That will
pull from the SSO settings that are configured within Jamf Pro. If you
want 5 different Jamf Connect settings, then you would need: 5 different
Jamf Connect configuration profil...
Not natively in Jamf Pro. You can set a policy to run Once per Month,
but not once every other month. A solution would be to utilize a
LaunchDaemon that ran on the schedule you want that simply used the Jamf
binary to call a specific policy. The poli...
@mmolenda yes, if you change that last line to match your upgrade line,
it should work. Something like this: sudo sentinelctl upgrade-pkg
"/Library/Application Support/JAMF/Waiting Room/$5" Obviously, test the
heck out of that.
Be sure to set the package to Cache not Install. You need the package to
be in the Waiting Room folder or the install will fail. And you might
want to blur out the key value in parameter 4. Don't really want that to
be out in the public.
This is a few years old now, but it worked solid for us. This would be
used as an AFTER script on a single policy that CACHED the installer. $4
would be set to our S1 token and $5 would be the name of the package
that was cached. This way you didn't ...