The Mac That Won't Update
A media company has 150 Macs. The IT team uses MDM software update commands to push macOS updates. On 30 Macs, the update command returns 'Installation failed' with an error referencing a missing volume or insufficient space. Those 30 Macs are older Intel models with 256 GB drives, and users store large video projects locally. The MDM shows the update as 'Available' but not installed. The company also has a policy that users cannot be forced to restart during business hours. The team wants to standardize on the latest macOS by end of quarter.
1. Diagnose the update failures and describe the constraints the team must respect.
Read the worked answer
The error (missing volume / insufficient space) on 256 GB Intel Macs with large local projects indicates the update cannot stage because free space is below what macOS requires (typically tens of GB for a major upgrade, more for the staging volume). The 'Available but not installed' state means the MDM can see the update but the install command fails at the device.
Constraints:
- No forced restart during business hours (user disruption policy).
- Local project data occupies the disk; deleting it isn't acceptable.
- Older Intel hardware may not support the latest macOS at all - verify model eligibility before assuming the target OS is installable.
2. What is the correct sequence to remediate these 30 Macs?
Read the worked answer
- Verify eligibility: confirm each Intel model supports the target macOS. If not, they are out of scope for 'latest' and need a separate lifecycle plan.
- Free space: identify large local projects, move them to network/shared storage (with user coordination), and confirm free space exceeds the update requirement with headroom.
- Schedule: use MDM to defer/schedule the install outside business hours, respecting the no-forced-restart policy - e.g., a maintenance window with user notification and a deferral countdown.
- Retry and monitor: re-issue the update command, watch for the same error, and confirm success in inventory.
Don't simply re-push the command; the disk constraint will reproduce the failure.
3. How would you handle the Macs that can't run the latest macOS?
Read the worked answer
Treat them as a separate fleet segment. Confirm the maximum supported OS for each model, set a compliance baseline that reflects reality (e.g., 'latest supported for model'), and plan hardware refresh for units that fall out of security support. Communicate to stakeholders that 'standardize on latest' is not achievable on unsupported hardware and that the end-of-quarter goal applies to eligible devices. Document the exception so audit/compliance doesn't flag them incorrectly.