Skip to main content
Question

Is it just me, or are the jamf binaries slow on Tahoe

  • September 17, 2025
  • 6 replies
  • 193 views

easyedc
Forum|alt.badge.img+16

Now that Tahoe is out of beta, gremlins that I'd noticed earlier now feel more pronounced.  During Build testing I find myself frequently running through 

sudo Jamf recon ; sudo Jamf policy

But since moving to the release of Tahoe they’re just painfully slow to report data. It doesn't matter if it’s an upgrade from Sequoia to Tahoe or fresh install via IPSW.  Wired or wireless. ...S.L.O.W…  Is it just me?

6 replies

ktrojano
Forum|alt.badge.img+20
  • Jamf Heroes
  • September 18, 2025

I’ve been setting up new M4 MacBook Airs this week and haven’t seen any slowness with running recon or policy on them once Tahoe has been installed. 


Shyamsundar
Forum|alt.badge.img+13
  • Jamf Heroes
  • September 19, 2025

I don’t see any delay or slowness in my environment respective to JAMF Binaries on macOS Tahoe , try running sudo jamf recon -verbose


howie_isaacks
Forum|alt.badge.img+23
  • Esteemed Contributor
  • September 22, 2025

I am not seeing any slower inventory or check-in processes since upgrading to Tahoe. When I was having problems with slow inventories last year we tracked down the issue to an extension attribute that was having trouble running. Once I disabled the EA, inventories started working at the normal speed. We didn’t need that EA anymore so I just deleted it.


easyedc
Forum|alt.badge.img+16
  • Author
  • Esteemed Contributor
  • September 22, 2025

When I've run it in verbose it’s hung frequently on 

verbose: Gatekeeper status: App Store and identified developers

Which is I think part of the native recon policy (ie not a custom scripted EA).  After doing a completely fresh wipe and restore via Configurator it seems to have gone away, but for a few days, it was quite noticeable. 


AJPinto
Forum|alt.badge.img+26
  • Legendary Contributor
  • September 22, 2025

I’m still in early testing of MacOs 26, but I figured it worth noting that Jamf 11.20.1 was deployed Saturday and Jamf skipped 11.20 unless you updated yourself. Jamf added support for the OS26 family with 11.20, so behavior may be better today post update.


howie_isaacks
Forum|alt.badge.img+23
  • Esteemed Contributor
  • September 29, 2025

I’m still in early testing of MacOs 26, but I figured it worth noting that Jamf 11.20.1 was deployed Saturday and Jamf skipped 11.20 unless you updated yourself. Jamf added support for the OS26 family with 11.20, so behavior may be better today post update.

Over the last several months, Jamf has released a  .1 update before installing the update for Jamf Cloud customers. I have to submit change requests before every udpate so I have been submitting them for .1 after noticing that Jamf has been doing this a lot.