Skip to main content

How Apple OS Update Management Evolved in FileWave

Apple OS update management in FileWave has moved from client-managed software update catalogs to Apple's MDM commands, Apple Software Lookup Service metadata, and declarative device management (DDM). This article explains that transition. For the current step-by-step workflow, see Apple MDM OS Software Updates.

Legacy macOS software update catalogs

Earlier macOS workflows used /usr/sbin/softwareupdate with Apple sucatalog metadata. FileWave could build and host a custom catalog so the FileWave Client controlled which catalog updates were offered. That catalog-based workflow is retired; current MDM and DDM workflows send management instructions while the device downloads applicable update content from Apple.

Traditional MDM software update commands

Apple added MDM commands for managed OS updates on iPhone, iPad, Apple TV, and Mac. AvailableOSUpdate asks a device which updates are currently applicable, ScheduleOSUpdate requests an installation, and OSUpdateStatus reports progress.

This model has two practical limits:

  • The management service sends an instruction, but the device controls download, preparation, authorization, and installation. Network access, available storage, battery or power state, and the device's current OS can delay or prevent the update.

  • Apple determines update eligibility per hardware model and OS state. Two devices can report different available updates, so a list of updates is not proof that every managed device can install each one.

Apple Software Lookup Service (GDMF)

Apple Software Lookup Service, often called GDMF, publishes update metadata and supported device models. FileWave uses that metadata to present current update choices more clearly, while device reports still determine whether an update is requested for a specific device.

Declarative device management (DDM)

DDM changes the update job from a one-time command into a declared target state. The management service can declare the required OS version and enforcement time; the device downloads, prepares, installs, retries when requirements are later met, and reports more detailed status. Apple's declarative Software Update configuration requires iOS 17, iPadOS 17, or macOS 14 at minimum.

FileWave transition history

  • FileWave 15.3.0: introduced the DDM foundation and application status reporting for compatible Apple devices.

  • FileWave 15.4.0: moved update discovery toward Apple Software Lookup Service metadata and added DDM software update management for compatible devices.

  • Current releases: use the Software Updates view, Software Update Filesets, and MDM or DDM instructions instead of hosting Apple update payloads in FileWave.

Current FileWave workflow

FileWave Central collects Apple update metadata and device reports in the Software Updates view. An administrator creates a Software Update Fileset for the intended release and deploys it to a test or production target. The device downloads the update from Apple; FileWave does not package the Apple update payload inside the Fileset.

For DDM updates, FileWave declares the target version and enforcement timing, and the device reports progress such as the pending OS version. See Apple MDM OS Software Updates for the complete procedure and current FileWave version boundaries.

If an update is missing or stalled

  • Confirm that Apple still offers the update for that device model and current OS. A filtered or complete-looking update list is not a fleet-wide eligibility check.

  • Check the intended Software Update Fileset, Deployment timing, and whether the device reports the update as requested.

  • Check network access to Apple, available storage, battery or power state, and whether the target release is still newer than the installed OS.

  • For DDM, check Pending OS Version after the device begins downloading and preparing the update.

Related content

No comments to display

Back to top