Jamf and macOS 27: migrate AFP repositories to SMB or HTTPS

Article created October 14, 2026 · Source reviewed October 14, 2026 · Official source: Jamf · Topic: Jamf Pro, macOS 27, and software distribution

Jamf Pro 11.33 records an infrastructure break: Apple removed Apple Filing Protocol support from macOS 27. A Mac running that version can no longer mount an AFP-based Jamf distribution point. The priority is not merely changing a protocol, but ensuring every package remains accessible, controlled, and traceable.

1. What Jamf announced

In the Jamf Pro 11.33 deprecation notes, Jamf states that Macs running macOS 27 or later fail to mount distribution points that use AFP. Jamf recommends moving these repositories to SMB or enabling HTTPS. This does not mean that every Jamf repository is affected: JCDS and points already served over HTTPS or SMB use different delivery paths.

2. The operational risk behind the protocol

A forgotten AFP repository can interrupt an installation policy, a Self Service repair, or a return-to-service workflow even when MDM enrollment and inventory still work. The symptom may resemble a package, network, or permission issue. Teams need to correlate the macOS version, selected distribution point, authentication method, and download result.

3. What changes for a Belgian or French business?

For an SMB whose Jamf environment is run by a partner, the immediate control is to request the distribution-point list, protocol details, and a test from a macOS 27 pilot Mac. For a mid-market organization, large enterprise, or public authority operating across Belgium, France, and Europe, the migration must also cover remote sites, network relays, firewall rules, service accounts, and bilingual support procedures.

Regulated environments should retain evidence of testing, cutover, and AFP credential removal. HTTPS may simplify network traversal, while SMB may remain suitable for an internal repository; architecture should drive the choice.

4. Underside analysis: treat the repository as a delivery chain

The migration should be managed as a software supply-chain change. Apple Business Manager and Automated Device Enrollment bring the Mac under management; Jamf then orchestrates policies; the repository delivers packages. If that final link fails, zero-touch deployment becomes incomplete. The review should therefore cover DNS, TLS certificates, segmentation, capacity, authentication, package integrity, and logging.

This complements the JCDS SHA-256 integrity control and our guide to macOS packages with declarative management: transport, integrity, and orchestration require separate validation.

5. Recommended migration plan

• Inventory every distribution point, protocol, priority, and associated site.
• Identify policies, packages, and recovery scenarios that still depend on AFP.
• Select SMB or HTTPS based on network architecture, exposure, and authentication.
• Test download, installation, retry, and Self Service on a representative macOS 27 Mac.
• Roll out in waves, monitor failures, and temporarily retain a controlled rollback route.
• Remove AFP, its network rules, and credentials once continuity is demonstrated.

Official source: Jamf Pro 11.33 Release Notes — Deprecations and Removals, accessed October 14, 2026.