r/macsysadmin • • 14h ago

MacOS SystemConfiguration: Can you guarantee a network operation has finished after a process crash?

4 Upvotes

I'm developing a macOS network failover controller and looking for advice from developers experienced with SystemConfiguration, networksetup, or configd.

The controller changes network service priority using:

networksetup -ordernetworkservices

I'm also investigating the equivalent native approach using:

  • SCNetworkSetSetServiceOrder
  • SCPreferencesCommitChanges
  • SCPreferencesApplyChanges

The problem

If the process performing the network change hangs, times out, or crashes, how can I reliably determine whether macOS has finished processing that operation?

For example:

  1. The controller requests a network service-order change.
  2. The command hangs or the controlling process crashes.
  3. macOS may already have accepted the configuration change.
  4. A replacement controller starts.

At this point, I don't know whether the previous operation could still affect the network.

I want to avoid issuing another network-changing command while the original operation might still be in progress.

What I've investigated

I've looked at SystemConfiguration preference locks, commit/apply calls, callbacks, notifications, and process termination.

So far, I haven't found a documented mechanism that guarantees all downstream network effects have completed.

My current design uses a single operation authority and a persistent journal. If an operation's outcome becomes uncertain, the controller blocks additional changes rather than attempting an automatic rollback.

My questions

  1. Does a successful SCPreferencesApplyChanges call guarantee that the relevant downstream configuration work has finished?
  2. Can configuration work submitted to configd continue after the original process terminates?
  3. Is there an operation-specific completion acknowledgement or synchronization mechanism I've overlooked?
  4. Is there a supported way to reconcile an interrupted operation before issuing another change?

I'm targeting macOS Sequoia on an Intel Mac mini.

I'm particularly interested in documented API guarantees, relevant Apple documentation, or firsthand experience with this failure scenario.

I don't need a general failover implementation. I'm specifically trying to establish a defensible completion or cancellation boundary.

Any insights would be appreciated.


r/macsysadmin • • 3h ago

Connecting the Dots: Building Integrations with Jamf Pro

1 Upvotes

Explains how to combine Jamf Pro APIs and webhooks with PKI and network access tools, using SecureW2’s certificate-based 802.1X setup as an example. Covers deciding which device data to share between systems and when.

Connecting the Dots: Building Integrations with Jamf Pro


r/macsysadmin • • 8h ago

Software Build WITH CLAUDE free, native app to grab macOS installers & IPSWs in one click

0 Upvotes

Hi everyone !

I manage a fleet of Macs and iPads with Jamf, and I got tired of digging through the Software Update catalog.

I asked Claude to build something more modern and more flexible for my needs.

Yes, it's almost fully vibecoded, welcome to 2026.

To be clear: I’m not a swift app developer, and this isn’t a business or a product. It’s a tool I built for my own work, and I’m sharing it in case it’s useful to someone else. It’s free, open source, and will stay that way.

SUS Fetcher is a free and open-source native SwiftUI app (Universal, macOS 14+, no dependencies).

What it does:

  • macOS installers: reads Apple’s Software Update catalog and downloads InstallAssistant.pkg in one click, with chunklist integrity verification, pause/resume and a download queue, automatic naming files.
  • IPSW firmwares for iPhone, iPad and Apple silicon Macs (ipsw.me, with Apple’s feeds as fallback)
  • Collections of installers/firmwares, with optional auto-sync that fetches new versions and trashes old ones
  • Already-downloaded detection, even for renamed files (matched by size + checksum, only on same folder )
  • Connected devices: iPhone/iPad over USB, and any device in DFU/Recovery (Apple silicon Macs included) shows up in the sidebar with its matching firmwares
  • One-click DFU for an Apple silicon Mac or a USB-C iPad connected to your Mac, no key combo needed (uses Asahi Linux’s macvdmtool). It can be set up once to run passwordless with Touch ID
  • Security & compatibility info from SOFA: CVEs fixed, actively exploited vulnerabilities, and which Macs support each macOS version

Built-in updater, FR/EN UI, MIT license.

Heads-up: it’s ad-hoc signed for now (no Developer ID yet), so you’ll need to remove the quarantine flag once. Instructions are in the README.

GitHub: https://github.com/Matt-uSk/SUSFetcher

Credits — this wouldn’t exist without:

  • SUS Inspector by Hannes Juutilainen, the original inspiration
  • ipsw.me for the firmware data
  • SOFA by Mac Admins Open Source for the security and compatibility data
  • macvdmtool by the Asahi Linux contributors for the DFU command
  • Apple’s public Software Update catalog and firmware feeds

Feedback, bug reports and feature ideas are very welcome, I’ll do my best to prompt the fixes in

Full disclosure: most of the code was written with Claude (Anthropic), and I tested it on real hardware along the way.