Hi All,  Does anyone has a script for automate User, Email Address, Position and Department after enrolment?Thanks in Advances

I’m pretty new to JAMF. I’ve got JAMF Connect 3.5.0, Self Service+, and JAMF Connect Launch Agent 3.5.0 deployed on my Mac Mini test device. I deployed these so I could start working on Tahoe support. After upgrading to Tahoe, everything seems to be working fine, except I now have to log-in twice when rebooting. The first login seems to be Filevault for unlocking the disk, and the second is the Entra web sign-in window from JAMF Connect.With Sequoia and the older version of JAMF Connect that most users are on, they only have to log-in once with the Entra web sign-in window.I’m using all the same config profiles as the old machines. Is this expected in Tahoe or is there some config change needed to get SSO sign-in to cover both filevault and OS login? Also, I have to enter the username in the second login as well. I’m pretty sure this was pre-populated before. I’m not 100% sure if this was caused by the new JAMF Connect apps versions, or only after the Tahoe upgrade.

We currently have an instance installed on tomcat and working on getting memcached working.memcached out of the box works fine, but it supports TLS encryption.  When we enabled this, it appears that JAMF doesnt know what to do with the TLS connection.We will firewall off that port as suggested.  But TLS seems like a good idea.

Is there any expectation that the Self Service+ icon will be Liquid Glass compatible when using custom branding? This would be helpful for consistent appearances across the new macOS UI. I created a .icns file using Icon Composer that contains icons using our own branding for Default, Dark, and Mono themes but, I’m unsure if there’s a preferred or supported method to deploy these icons in a way that ensures compatibility with Liquid Glass design standard. 

Hey Jamf Nation! Welcome to another edition of Things to Do for JNUC, 2026 Edition. This JNUC we’re heading to Kansas City, Missouri, so let’s make the most of it. Whether you’re travelling from near or far (I’m still coming from Canada!), here’s a curated list of activities to help you plan your trip. Locals - please share your insider tips! JNUC HighlightsJNUC Party: The Wednesday night bash is always a highlight of great music, food, and networking. Don’t miss it! Vendor Parties: Expect free drinks, tasty bites, and epic giveaways. Jamf Heroes Meetup: Details for 2026 aren’t out yet but keep an eye on Jamf Nation for updates. Official JNUC Info: https://www.jamf

Apple now supports Platform SSO during Automated Device Enrollment (ADE) in macOS 26. This allows users to authenticate with Entra ID directly in the Setup Assistant, create a local macOS account, and gain immediate SSO access to apps and websites.Currently, the Microsoft Platform SSO plug-in does not support this flow, and Microsoft has not announced full support.Could this serve as a workaround for first-time login on a JAMF-managed Mac?A possible setup using Entra ID:1. Start the Mac → Setup Assistant2. Sign in with Managed Apple ID (federated with Entra ID)3. Redirect to Entra ID → authenticate4. Create a local macOS user5. Enroll the device in MDM6. Configure Platform SSO later using the Entra ID user This approach enables initial device setup while allowing Platform SSO to be activated once the local user account is established.

Is there a way to prevent local administrators from removing the JAMF Binary with jamf removeFramework ? We still need local administrator accounts for our professors but don't want them to be able to delete the JAMF Framework.

Hi all,I’m looking for some advice on improving our macOS update workflow. Current setupRight now we’re using a mix of:Restrictions payload with no deferral for our tester group, 1week deferral for everyone else.Nudge -separate config profiles depending on whether we want to push a required update or just remind users.This works, but managing multiple profiles every time there’s a new macOS version isn’t ideal.What I’d like to achieve is: A cleaner process for forced updates for everyone when needed.A standard workflow where users get UI prompts to update (Nudge-style), based on our deferral policy.Ideally: define the update version and handle the user prompts from one place, without juggling several profiles. Does Jamf Pro offer any built-in way to handle both the update logic and user prompts together?Or is Nudge still the best option?If you have a setup tha

I am attempting to roll out Jamf trust for ZTNA. I currently have Crowdstrike falcon installed on all of my fleet. My understanding is a limit of Mac is only one network filter can be active at a time. It seems like Crowdstrike doesn’t play nice with Jamf Trust. Even with the filter disabled I am unable to edit the DNS settings to have default to Jamf. Has anybody successfully deployed both products?

Hi! As my institution's Jamf admin I'm working on developing procedures to manage our to-this-point large pool of essentially unmanaged iOS devices. Prestage Enrollment isn't new to me, but managing iOS very much is. I'm currently working on bringing management to a pool of loaner iPads, but with an eye towards managing personally assigned iOS devices once I've got the loaners under control. I've been playing around with Jamf Reset, Jamf Setup, and Apple Configurator 2, and I'm still confused on a few points. 1) I think I already know the answer to this (No) but... there's no way to wipe an iOS device via Configurator, Jamf Reset, or any other method that wipes everything EXCEPT a wireless profile, right? Doing so would actually allow us to provide the "over the air" functionality everyone likes to talk about. 2) Activation Lock seems to be a sticking point. I definitely want "Prevent user from enabling Activation Lock" since that's burnt us before,

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

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