SpecificVersionUnavailableForDeviceModel

[Chris_Cover]

Running a long standing (and working) script to do updates on Macs and got this error today with a Jamf cloud client:

Install action:Download and schedule to install (2025-01-15T15:00:00)

Update action:Specific version (15.2)

Current state:PlanFailed

Error reasons:SpecificVersionUnavailableForDeviceModel

Part of my script verifies that the Jamf Cloud client recognizes the requested version (like sometimes the trailing ".0" is not recognized). So that shouldn't be it.

The plan is actually created but is "immediately" rejected:
{ "events" : [ { "type" : ".PlanCreatedEvent", "managementUUID" : "e163182f-ea49-440e-967c-b5840bcf0366", "processManagerUUID" : "85980caf-557a-411e-99b9-94a07a478ead", "id" : 2469, "deviceObjectId" : 1, "eventReceivedEpoch" : 1736956458301 },

{ "type" : ".PlanRejectedEvent", "managementUUID" : "e163182f-ea49-440e-967c-b5840bcf0366", "processManagerUUID" : "85980caf-557a-411e-99b9-94a07a478ead", "id" : 2470, "deviceObjectId" : 1, "eventReceivedEpoch" : 1736956463479 } ] }

Target is a MBP M3. 

Running softwareupdate -l from the terminal shows the update as available.

Cloud client is v 11.12.1-t1734365229835

[bella964]

Hello,

The error SpecificVersionUnavailableForDeviceModel indicates that the version you are trying to deploy (macOS 15.2) may not be marked as compatible with the specific device model (MacBook Pro M3) in Jamf's database. Despite the update appearing in the softwareupdate -l output, Jamf may have additional constraints or metadata that causes the plan rejection.

Here are steps to troubleshoot and resolve the issue:

1. Verify Compatibility in Jamf
Ensure that macOS 15.2 is explicitly marked as compatible with the MacBook Pro M3 in Jamf's configuration.
Check if Jamf’s compatibility matrix or ruleset requires additional actions for M3 devices.
2. Update Jamf Cloud Client
The cloud client version you’re using (11.12.1-t1734365229835) may not have updated compatibility mappings for newer hardware or macOS versions. Check if an updated client version is available.
3. Double-Check Update Naming
Sometimes Jamf has strict naming conventions or mismatches that cause rejections. Run:
bash
Copy
Edit
softwareupdate --list-full-installers
to confirm the exact version identifier.
Verify your script is properly identifying 15.2 as the desired version.
4. Check Jamf Logs for More Details
Review Jamf server logs to get more information on why the plan was rejected.
Look specifically for logs tied to PlanRejectedEvent to identify whether the issue is compatibility, permissions, or another constraint.
5. Manual Deployment Test
As a workaround, try manually installing the update using softwareupdate or a downloaded installer:
bash
Copy
Edit
softwareupdate --fetch-full-installer --full-installer-version 15.2
sudo softwareupdate --install --all
6. Ensure Device Information Sync
Confirm the MacBook Pro M3's inventory in Jamf is fully up-to-date:
bash
Copy
Edit
sudo jamf recon
Re-sync the inventory and retry creating the update plan.
7. Update Jamf Patch Definitions
Check if the Jamf Pro Patch Management definitions for macOS 15.2 are up-to-date and include the MacBook Pro M3. If not, contact Jamf support or manually update the definitions.
8. Contact Jamf Support
If the issue persists, reach out to Jamf support with the full error logs and context, including:
MacBook Pro model and macOS version.
Jamf Cloud client version.
Full logs for the failed plan creation.

Best Regards