After poking around Jamf Pro and Jamf Protect, it seems that JSC/RADAR/Wandera is the only source of storage for CVE-level details for managed client app inventories. I can plainly see them in the default web dashboard. So I set up a Risk API key, and enabled the option to see user and device details.Both the docs [1] and manual exploration seem to conclude that only “Device risk” can be gathered from the public API, whereas things like “Average CVSS score” (or anything related to CVEs) cannot. Which would be fine if those two had a tight relationship, but I can plainly see things like an endpoint with six (6) high-scoring app vulnerabilities (including a 10 and a 9.8) per CVSS that only has two (2) app vulnerabilities reported per device risk and grading overall as low-risk.I did notice that app vulns as a category can be force-upgraded from low to high to influence device risk more, but it’s possible that device risk will entirely miss the presence of vulne

With Apple recently expanding access to the ABM/ASM API, I set out to recreate the GSX experience. By leveraging Jamf’s new MCP feature, Claude Code, and MUT, I believe I’ve come very close. Additional details are outlined below.I also plan to publish a GitHub repository for anyone interested in contributing or enhancing the project.#!/bin/zsh# ==============================================================================# Script Name: abm_warranty_report.zsh# Author: Brandon Woods# Date: February 23, 2026# ==============================================================================## Pulls device and AppleCare / warranty coverage data from Apple Business# Manager and writes two MUT-compatible CSV files:## ComputerTemplate.csv — Mac devices (productFamily = "Mac")# MobileDeviceTemplate.csv — iPhone, iPad, Apple TV, iPod, Vision Pro, etc.#

Howdy everybody! Time for my annual post about how we all need to get our budgets prepped and ready to go for all the hardware we need to replace that Apple is dropping from its OS Compatibility list!I've modified my previous regex statement to take out the models that were lost to us this year to the latest macOS version. It looks like Apple is taking a big ole axe to the intel macs, minus only a couple of exceptions that seem to tie to the devices that were still being sold at the time of the M1 release. One tricky piece are the specific intel MacBook Pro's that Apple has listed. In that grouping are the MacBookPro16,x models, where x is 1,2 and 4, but not the 16,3 model, so keep that in mind. If anyone has details that contradict that, please let me know here and i'll quickly change the posted regex.I've tested this in my own Jamf instances to verify its returning the data that i'd expect to see, and am confident this will be able to match everything that is no long

Since November 2025 you can find the warranty information for your Mac devices in Apple Business Manager. You can call this information using API calls. Is there any information if Jamf is going to make an Jamf integration? This warranty information would be a cool feature to have in Jamf. As an MSP it would be great for Life Cycle Management for our customers.I’ve seen no information from Jamf jet.Sofar I've been working on local scripting in python to get the ABM warranty information in Jamf as an Extension Attribute. For Computers I've succeeded I'm however not successful yet for mobile devices. The Jamf Classic and Pro API’s won’t let me update Extension Attributes for mobile. So I'm stuc.Anybody there who would like to help? Or can somebody tell me how to update an extension attribute for mobile, if it is possible and not blocked in api.Kind Regard Remco.  

Hello everyone,i wanted to roll out our new custom TeamViewer Host and everything works except that our custom design with the company logo is not displayed. I did it exactly as in the instructions: https://hcsonline.com/images/PDFs/Jamf_Teamviewer_Host.pdf After the custom logo didn't show up, I kept searching and came across these instructions: https://community.teamviewer.com/English/kb/articles/50739-mass-deployment-on-macos#perform-an-assignmentThe groups and the membership works but unfortunately our custom layout does not. Am I missing something or have I done something wrong? 

Unable to complete file upload. fiie contents does not match file type in Jamf when uploading an automated device enrollment token from apple business manager

You got this.  TGIF!Have a great weekend!Feel free to share to your memes or express that you are glad this moment has finally arrived and the weekend will soon be upon us. 

We are currently using a pre-stage created managed account and the LAPS process for passwords on that account. Since we use Jamf Connect, we have ‘skip account creation step’ turned on.I am finding that this account is not getting the bootstrap token escrowed or a secure token after MDM enrollment. Is this intended? How can I change this? Ideally, I’d like to have a hands off option that doesn’t require a manual installation so that we always have the bootstrap token escrowed and a secure token on our managed account. What am I missing in this step? I am finding when we do need to use the local admin account, it’s not able to take some actions, like install a new OS.

Heads up to my fellow Jamf community. We've been seeing iPadOS 15.8.4 iPads when reprovisioned can't be enrolled to Jamf School.  This may affect Jamf Pro too.  The exact error is "Failed to retrieve configuration".  I reached out to Jamf support and they said they have been getting reports of this from others and that this has been observed across different MDM providers.  Jamf reached out to Apple regarding this issue and this is exactly what they told me: Apple did get back to us just a bit ago, and they have identified the issue (they did not elaborate on what the issue was). The release is not ready yet though and at this time they couldn't give me an ETA on when that would release. For now I created an internal Jamf Product Issue so we can track customers and I have attached this case to that ticket (PI136109). Hopefull

👋🏻 Hi everyone!We are organizing a Mac Admin community event on April 30th in Leiden (Netherlands) and wanted to share an early heads-up here.This is not a vendor or company event — it’s very much by the community, for the community, Inspired by established Mac Admin conferences and from years of local community meetups. Expect practical talks, shared experiences, and plenty of time to talk with other Mac Admins.More details coming soon, but feel free to reach out if you’re interested or want to know more. 🙂Website is https://macadmins-eu.org.LinkedIn page is https://linkedin.com/company/mac-admins-europe.Hope to see many of you there! ✌🏻

Hey all - Ran into a thing that has been mentioned before, but it was a year ago and a few Jamf Connect login versions ago. We are now up to 3.6 Had a user who had their Microsoft Authenticator switch from sending them push notification to enter a number to requiring her to enter the 6 digit number. She would get the Jamf Connect Login window and enter her MS login, PW and the 6 digit 2FA code. The Jamf Connect Login window would stay up, but load her profile page. She would also see an error that password needed to be at least 7 characters, and contain one number and one alphanumeric character. It took me a VERY long time (and a computer wipe) to figure out that it looks like the Jamf Connect login window is passing that 6 digit number to the OS for login instead of the users Password.  Once we reset her Authentication Methods in EntraID so that the push notification workflow returned, her login issues on her laptop went away. 

Due to changes being made by our network team we’re required to deploy a new Trusted Root Certificate within our Wifi Configuration Profile.  DigiCert are changing Root Certificates.What I’m encountering is even though I can successfully deploy the Certificate and Trust it within the Configuration Profile if I deploy more than one Root Certificate the Mac will not connect.I’m hoping that I can deploy the new certificate without impacting the existing wifi connection before Networks make the backend change.

Dear community,I am facing a major issue with our Jamf Pro environment.We are running Jamf Pro 11.21 On-Prem and have several working PreStage enrollments—until today.I had a device that was already upgraded to macOS Tahoe. After erasing the Mac, I started the PreStage enrollment. The macOS installation completed normally, and the device enrolled in MDM.However, after the Setup Assistant finished, Self Service never appeared, and only half of the expected configuration profiles were installed.I waited over 30 minutes, thinking it might be a timing or network delay, but nothing happened. I also tried: restarting the Mac running sudo profiles renew -type enrollment manually installing Self Service.pkg and jamf.pkg copied from a working machine Even after manual installation, the agent could not connect to the server.It looks like the Jamf framework does not install

Greetings all, We are trying to enforce screen lock time limits (which InfoSec wants), but when we do, it also enforces a particular screensaver module (which InfoSec doesn't care about in the least).  Some of our users don't like "Flurry" and want to set their own.  These two seem joined at the hip in the GUI.  Copilot had a suggestion using a script, but it didn't work for me. Does anybody have these two things functioning, but separately.  It doesn't seem like a big deal to me, but some of our users are really not happy about not being able to set their preferred screen saver.

Hi all I have a fleet of Mac Pros all sitting behind a firewall. All traffic - IPs, ports have been allowed as per the Jamf documentation. All Macs can sync and restart however apps can't be deployed or updated. Am I missing something? I even have the entire APNS IP range allowed but still nothing. Any help or advice would be much appreciated

We are new to Jamf Now. WE have been experiencing issues with deploying apps to some of our phones. I have tried to re-enroll it, restore the phones, re-create the blueprint and create a different blueprint. I also updated the tokens.  Has anyone encountered this issue? If yes, would you tell me what troubleshooting steps did you do? 

I am suddenly having an issue with JAMF deployed apps. I’m only seeing the issue happening on 3 apps that are paid for. The apps deploy properly to the iPads but are now prompting the user to sign in to an Apple Account whenever the app is opened on the iPad. If they hit cancel it allows them to use the app but when they close out of it again, it will prompt the sign in again.Our VPP token in JAMF is not expired, the location is correct, Managed distribution for the app hasn’t changed since it previously been setup and working and we have enough licenses and this issue only suddenly started happening. I’m not seeing it on the free apps. Any feedback or direction would be great, thanks!

Hi everyone, I'm deploying the Global Secure Access (GSA) client on macOS using Jamf, following the official Microsoft documentation:https://learn.microsoft.com/en-us/entra/global-secure-access/how-to-install-macos-client The installation completes successfully, but on first launch, users are still prompted with the message:"Global Secure Access Client would like to add proxy configurations." Does anyone know how to pre-approve or automatically allow this proxy configuration request via a configuration profil

We have had a PolicyBanner installed on our fleet for several years.  We have not had an issue with it until users upgraded to 26.  When the banner pops after user login, the window is stretched to almost full screen, regardless of screen size or resolution.  Screenshot attached of my large screen monitor.I have tried editing the RTF file a few ways to change margins and it will change the text but does not affect how the window sizes.I have also tried changing Desktop & Dock > Windows to Prefer tabs to Always instead of Full Screen This screenshot shows after trying to change margin and text.  I can share another with all the txt centered and nothing on the right of the txt but empty white space.   Thoughts?  Here is the original screen 

Hello all,I just started with an existing system that isn’t really documented.  This means I have to do a lot of jumping around to determine what something does, where it applies, and even if it is working.  I want to create some good documentation for this, but I’m don’t know what the best method for doing this would be.Thank You in advance,-Pat

Anyone running into an issue with the Shared Device SSOe profile failing to install on shared iOS devices? I set up the Intune integration with Jamf Pro for both shared devices and standard iOS devices. Standard iOS devices register with Microsoft just fine, but don’t actually perform SSO with the Microsoft apps but they do show as compliant in Entra. I had the Shared Devices registering for about two days and now after wipe, The “Install Device Compliance Shared Device Profile” command fails every time even with a different device. Previous Entra records have been removed. Any ideas of what I could try to fix it or where I can find more detailed logs? History of failed commands had nothing. 

I get a Lego block icon when trying to login to a Mac on a domain. It doesn’t happen on all computers. I recently wiped a MacBook, that I could log into, however, after enrollment... now I get the Lego block icon. I can log in with other accounts.I believe it has something to do with the AD binding and possible VPP issue (my logs have been flooded with VPP Invitation Usage notifications). I don’t know how to fix it.Any help, would be greatly appreciated.Thank you. 

I have been checking my Change Management logs .. and I have hundreds of VPP Invitation Usage logs - is this normal, is it causing other issues? 

Hi,We're starting to see a number of cases being raised internally about some of our Macs (all on macOS 15.1.1) having intermittent login issues.  Our devices are bound to AD and our users have been logging on fine for some time but now we're starting to get issues.  Sometimes the logins are fine.  Sometimes they take ~10 mins and sometimes they appear to stall completely (waited over 2.5 hours in testing) even on the same device.  The login screen appears to freeze (the time doesn't change) and you eventually get the spinning beachball.  SSH is still working and you can run a "jamf policy" successfully.  "Screen Sharing" reports that the user who has attempted to log into the device is the active user when you connect.Can anyone share some tips as to how we would start to investigate this sort of issue let alone resolve it???ThanksStuart

Morning,Anyone else experienced this issue since updating to Logic Pro 12 - We’ve got Jamf Pro at my org and currently push out Logic Pro via Apps store on Jamf which takes care of the updates and deployment to our various smart groups but since updating to version 12 yesterday we receive this error everytime we launch LP: The application cannot be used because the App Store authentication failed or no Network is available.Any ideas?Any advice or tips is greatly appreciated.