Today we are releasing a maintenance version of Jamf Pro; highlights include: Resolved IssuesJamf Pro Server[PI122411] Fixed: After making changes to a user level configuration profile that is made available in Self Service, Jamf Pro unexpectedly redistributes the profile when devices update inventory, sometimes resulting in devices losing network access. [PI134378] Fixed: When attempting to upload a file (e.g., configuration profiles, in-house apps, eBooks, certificates) the page refreshes or the Upload dialog closes before the upload is complete. [PI148308] Fixed: The Jamf Pro API endpoint POST /v1/devices/{id}/erase does not clear Activation Lock for computers, despite clearing Activation Lock when erasing computers with a remote command via the Jamf Pro interface. [PI148751] Fixed: Attempting to create or retrieve patc

To all those who celebrate/observe, may you and your families have a Happy Channukah/Hannukah/Hanukah/Festival of Lights!  

Update 12 December 2025: Standard Cloud upgrades are scheduled for the weekend of 9–10 January 2026 (details below). We appreciate your patience with the revised schedule. Today we are releasing Jamf Pro 11.23; highlights include:New Settings for Privacy Preferences Policy Control and Platform Single Sign-onJamf has expanded support for additional Privacy Preferences Policy Control restrictions and the Single Sign-on Extensions payload with new computer configuration profile keys. This update enables administrators to define and deploy more granular privacy and security permissions for macOS devices while streamlining the user experience.Return to Service EnhancementYou can now add more than one payload to a configuration profile when configuring Return to Service in a PreStage enrollment. Previously, only one Wi-Fi payload could be used. For additional information on what'

Today we are releasing Jamf Pro 11.20; highlights include:Compatibility with Apple Operating SystemsCompatibility and new feature support are based on testing with the latest Apple beta releases of macOS Tahoe 26, iOS 26, iPadOS 26, tvOS 26, visionOS 26, and watchOS 26.   Simplified Setup for Platform Single Sign-OnJamf Pro can now support deployment of a Platform Single Sign-on (Platform SSO) application during the Setup Assistant with macOS 26* using the Simplified Setup for Platform Single Sign-on workflow in a computer PreStage enrollment. This workflow allows for Platform SSO to be enforced thr

I use the API to set an owner and it works fine however, the documentation states that to remove an owner the owner should be set to zero and the message I get back is user not foundhttps://api.zuludesk.com/docs/#api-Devices-Assign_owner 

A couple users updated to MacOS 26.2 over the weekend and are seeing this in Jamf Trust.  I updated my computer and I’m seeing the same.  I’m guessing that Trust just doesn’t recognize 26.2 yet?  Or is there something I need to do on the admin side of things to fix this?  I don’t think I’ve ever had to touch macOS versions in trust before. “MacOS is outdated”MacOS version 26.2 

Hello, We have an issue where iPads running 26.0.1 are working absolutely fine no issues whatsoever however as soon as they upgrade to 26.1 their internet connection stops working. Devices can be connected to the network no issues and appear to be working fine but you are unable to access the internet and they refuse to talk to JAMF.I found the following : https://discussions.apple.com/thread/256182709?sortBy=rank which appears to be the same issue. Wiping the devices hasn’t helped and the problem persists.  

I’m trying to install a driver for a robotics course in our school division.  The teacher says that this is the correct version for their devices:https://www.silabs.com/software-and-tools/usb-to-uart-bridge-vcp-drivers?tab=downloadsUnfortunately it doesn’t seem to have a PKG installer.  The drivers are a system extension and are installed through an app and not a pkg.  There is a pkg in the dmg but it doesn’t install the system extension as far as I can see.I did attempt to package using Composer to monitor for changes but when I run the created pkg afterwards it fails.  I’m assumning due to the system extension needing additional permissions perhaps.I have investigated this and it may be that Sonoma and beyond have the driver installed by default as per an article here:

I am new to Jamf, exploring on webhooks where iam confusing about authentication which we have to use for webhooks and do we need API access for webhooks?

Connect 3.4.0Self Service+ 2.12.0OS 26.1 Tahoe (Many other machines on 26.0.1)I can not get this prompt to close no matter what I do. Everything in the back end seems fine with my machine and my connection to Jamf, self service, connect, everything, it all seems fine. Anyone have any ideas?  I did not see this issue prior to updating OS from 26.0.1 to 26.1 and that is the only thing I can think of that may be triggering it. I have tried deleting associated keys and allowing them to regen, I have tried flushing and re-pulling Config Profiles and Policies. P&S settings are all good. I have fond that if I leave the window there for 30min or more, it will finally close after entering PW and selecting Always Allow, but then comes back up after Reboot.

Hi, kind of new to this and I don't know if there's a better place to post this question.I’m having trouble retrieving and modifying the student device restrictions using the version 4 API. I’ve used version 4 for teacher lessons, and it works fine. However, the  retrieve current student device restrictions API doesn’t provide the correct information. It does not show any restrictions when there are. This is what I get back.[ { "studentId": 142 }, { "studentId": 143 }]https://api.zuludesk.com/docs/#api-Teacher-ModifyProfiles and https://api.zuludesk.com/docs/#api-Teacher-GetProfiles  So, the APIs are executing, but they’re they are not

Friday. Yes. Friday.macOS/iOS 26.2.• https://support.apple.com/en-us/100100

​We currently have our students set an app age restriction of 12+ in our MDM  Today we came across an app, Grammarly Keyboard, that is now 13+ .  That causes the app to install and then immediately remove.   Our only other option in the MDM is 17+ Anyone else running into this issue? Any other apps in the 13+ category?

A maintenance release to Mac Admins’ new favorite, MDM-agnostic, “set-it-and-forget-it” end-user reminder for Apple’s Declarative Device Management-enforced macOS update deadlines that further simplifies enterprise-wide deployment and adds user warnings for excessive uptime and low disk space OverviewWhile Apple’s Declarative Device Management (DDM) provides Mac Admins a powerful way to enforce macOS updates, its built-in notification is often too subtle for most administrators.DDM OS Reminder evaluates the most recent `EnforcedInstallDate` and `setPastDuePaddedEnforcementDate` entries in `/var/log/install.log`, and then leverages a swiftDialog-enabled script plus a LaunchDaemon to deliver a more prominent end-user dialog that reminds users to update their Mac to comply with DDM-enforced macOS update deadlines.

Hello everyone,I have a problem in PreStage Enrollment, when passing through the sAMAccountName, maybe someone here has a solution for it.We need user certificates per configuration profile, which is why I set up a new PreStage Enrollment for MDM Enabled Users, but currently the ShortName (sAMAccountName) is not taken over for the AccountName if the value contains capital letters (which is unfortunately often the case here).The other attributes were already in use, which is why we used "Room" for mapping the sAMAccountName/onpremisessamaccountname, which works so far, but in PreStage only as long as there is no capital letter. If there is a uppercase letter in it, the value is not filled in the macOS account setup and the fields are not locked.AD and AAD are set up and Entra ID as IDP for SSO.There are already hundreds of rolled out Macs i

A five-question self-assessment to help you plan your 2026 Mac Admin open source contributions InvitationPlease accept my personal invitation to increase — or, for you Jedi-Ninjas, to maintain — your contributions to the Mac Admin community’s various open-source projects during 2026.Take the self-assessment

Hi everyoneis it possible to get the result of the variable for configuration profile in lower case?Currently I have configured “Lock primary account information” with variables(see screenshot) The result of the variable is always in upper case. it is possible to change it to lower case? if yes then how? 

Has anyone had success deploying Cisco Secure Client XDR with Jamf School? We have a fleet of Macs that we’ve been trying to deploy this out to, but everything either fails, or does not install silently.Is there a guide or anything specific for Jamf School?

So I’ve started seeing an issue with macOS 26.1 trying to set up new machines.The enrollment customization is not passing the user info from the SAML token, which is a known issue but usually sending the workaround profile that sets those attributes works fine. Here is the payload:<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"><plist version="1.0">    <dict>        <key>EnrollmentRealName</key>            <string>$REALNAME</string>        <key>EnrollmentUserName</key>            <string>$USERNAME</string>    </dict></plist>it’s not working now, I’m not even seeing the computer’s username change in Jamf Pro after signing in through the enrollment customization

Your configuration may need to be updated on your iPads.  On their tech call today they mentioned adding the device name to the config so that the name will show in the COS.  The info in their PDF did not make sense to me who is not a coder.  With some help from the Jamf AI this is the config that worked for me.  Make sure to change the ouIds to your COS Org Unit ID <dict>  <key>ouIds</key>  <string>1234567890</string>  <key>deviceName</key>  <string>$DEVICENAME</string></dict>

 We’re a year into Apple shipping Apple Intelligence (though technically still in Beta) but Apple hasn’t shipped a clear matrix of which features are on-device vs. require Private Cloud Compute (PCC). If you haven’t read part 1, then click here and go back and read it. And then follow up and read part 2, by clicking here. But what if… all that information was hiding on your very Mac in a system diagnostics, your Mac quietly generates a Model Catalog inside sysdiagnose that lists feature availability, languages, and — critically — which resources are server-side! For those that do not know, you can run a system diagnostics and explore the zip file created to potentially fi

With 15.6 and beta macos 26The EA I was using for report back a macs SSID is now broken/blocked.Does any happed to have one that will works? Thanks #!/bin/sh# Jamf Extension attribute to return SSID## Check for SSID namewifi_name=$(ipconfig getsummary en0 | awk -F ' SSID : ' '/ SSID : / {print $2}')# Check if SSID is foundif [ -z "$wifi_name" ]; then    result="No Wi-Fi network found."else    result="$wifi_name"fi# Result for Jamfecho "<result>$result</result>"    

Jamf announced in January that the Jamf Pro Classic API will no longer support basic authentication in a future release. Classic API scripts can still run—administrators just need to make a simple change in how they authenticate. Let’s look at why this change is coming and how to convert Classic API scripts to use bearer tokens for authentication instead of usernames and passwords. The token obtained during this workflow will allow authentication to either the Classic API or the more modern Jamf Pro API. We’ll cover: How bearer tokens improve security Request the first token Parse the token Use the token to send an API command Expire the token Renew the token How bearer tokens improve security This change to move away from supplying usernames and passwords as credentials for authenticating to Jamf Pro is a good thing. Bearer tokens improve security by reducing the number of times credentia

We are excited to share that we’ve updated our Privacy Notices across our services to enhance clarity and transparency.Our Privacy Policy has been revised to provide greater transparency regarding our use of AI within our Services, specifically for automated email sentiment analysis, which enables us to better understand and support customer needs while maintaining data privacy standards.Jamf is certified under the EU-U.S. Data Privacy Framework (DPF), the UK Extension to the EU-U.S. DPF, and the Swiss-U.S. DPF — international frameworks that ensure robust data protection standards. In alignment with these frameworks, we have updated our Employee Privacy Notice to reflect our continued commitment to the DPF principles. We have also refined the language and defined terms in the notice.You can access the updated Privacy Policy and

Since the A16 iPad doesn’t have serial numbers engraved anymore, I need a way to identify iPads in cases where the screen has died (water or physical damage). Are there any solutions like this that integrate with JamF School? If not, are there any recommendations?