After upgrading to macOS Monterey, you might see notifications like the above.
If so, the simple solution is to logout and then back in (or restart).
This seems to correct things, without any deeper delving into the issue.
Many thanks for @nstrauss and @Tyler Sparr for mentioning this on the macadmins slack, and raising an issue for Notifier too.
Over the past weekend in #autopkg Slack channel in the MacAdmins Slack, some fellow admins saw their recipes erroring with a non-zero exit status of 60.
At dataJAR we only run our AutoPkg recipes weekdays, but sure enough we hit the same issue come Monday.
Below is some more details, as well as a proposed fix for at least the short term.
At dataJAR, I recently worked with a customer which wanted to make use of Jamf Pro’s Enrollment Customization option.
However, with everything setup, we were presented with the message “Error <kCFErrorDomainCFNetwork:303>” whenever trying to load any of the defined PreStage Panes.
I reached out to Jamf Support, but they hadn’t see this issue & searching the macadmins Slack didn’t bring up anything either.
Long story short (& in an attempt to not create my own DenverCoder9 moment), we discovered the issue to be down to the environments ingress controller being configured with HTTP/2 support by default.
As soon as we disabled HTTP/2, everything worked as expected.
Hope this helps someone else too.
A week after the recent updated Terms & Conditions, we saw DEP sync errors reappear in our datajar.mobi deployments.
Below is some detail on what has caused these new sync errors & how to resolve.
With the release of iOS 13 last night, new Terms and Conditions were released.
This is an annual update, however your MDM might not have responded as expected.
See below for some more details.
Recently we updated all our datajar.mobi instances to Jamf 10.7.1, for Mojave support.
All went well. Except for a couple of instances where their Jamf Infrastructure Manager was being used as an LDAP Proxy.
Well, turns out this was a change to Java 8 Update 181, which we updated to at the same time. And, that this is an issue not just with Jamf Infrastructure Manager, but could be with LDAPS in general.
Below details these changes, & overcoming this issue.
Earlier tonight, myself & a few others on the #osx-server channel in the macadmins.org Slack started to receive alerts from our macOS Servers running a Caching Service.
Sadly, it was not just the harmless “Caching service unavailable” alerts that you see at times.
Recently, myself & a few folks have been dealing with issues from profiles deployed via the JSS.
Kitzy has a workaround for the issues affecting 9.82 & screen savers asking for passwords, here.
This was seemingly fixed in 9.9, but other issues have since cropped up & I’ve detailed them below.
As mentioned before we have some scripts that access Airwatch’s REST API.
Sadly a recent update to our SaaS instance to 184.108.40.206 lead to our scripts failing.
Below is a little post with the resolution.
After being nerd sniped by @unknown_err in a channel on the MacAdmins.org Slack, I started writing some client side API scripts.
This lead to an issue with 10.8.x clients connecting to my JSS.
The below is why I saw these SSL errors & a two resolutions, one client side & another server side.