Skip to main content
Solved

Blueprint Deployment Status

  • March 16, 2026
  • 6 replies
  • 473 views
julixn.lx

I am currently getting to know more about the new Blueprint feature in Jamf Pro. 

Currently I can see that a blueprint has been deployed to 60 devices, 19 devices are pending and 1 device currently has got an error. 

How can I check which devices have already received the Blueprints components and which devices still need them?

Thanks in advance!

Best answer by Ecco_Luke

Currently, anything deeper around Blueprint inspection has to be done via the API (or custom apps that leverage it) - https://learn.jamf.com/r/en-US/jamf-pro-blueprints-configuration-guide/Viewing_the_Status_of_a_Blueprint_Jamf_Pro_API

It will come to the GUI for sure. This is just for now 😊 

6 replies

S
Forum|alt.badge.img+9
  • ScottEKendall
  • Valued Contributor
  • March 17, 2026

You might want to check out my repo..I wrote an app specifically for this (disclaimer...it is still in RC stage...so there might be some bugs in it).  https://github.com/ScottEKendall/JAMF-Pro-Scripts/tree/main/JAMFGetDDMInfo

    Ecco_Luke
    Forum|alt.badge.img+9
    • Ecco_Luke
    • Valued Contributor
    • Answer
    • March 17, 2026

    Currently, anything deeper around Blueprint inspection has to be done via the API (or custom apps that leverage it) - https://learn.jamf.com/r/en-US/jamf-pro-blueprints-configuration-guide/Viewing_the_Status_of_a_Blueprint_Jamf_Pro_API

    It will come to the GUI for sure. This is just for now 😊 

      PE14_2
      Forum|alt.badge.img+8
      • PE14_2
      • Valued Contributor
      • May 26, 2026

      ​@ScottEKendall Hi Scott try your script added Client/Secret account in Jamf but when I run your script I see in the Terminal this:

       

      2026-05-26 16:12:17: JSS connection active!

      <stdin>: Could not extract value, error: No value at that key path or invalid key path: token

      2026-05-26 16:12:31: Classic API token successfully obtained.

      <stdin>: Could not extract value, error: No value at that key path or invalid key path: token

      2026-05-26 16:13:01: Classic API token successfully obtained.

      2026-05-26 16:13:01: Token already invalid

      thanks 

      S
      Forum|alt.badge.img+9
      • ScottEKendall
      • Valued Contributor
      • May 26, 2026

      If you are running this thru terminal commands, then you need to pass in your Client/Secret info in Paramters #4 and #5, so for instance ‘./GetDDMInfo.sh “” “” “” “<ClientID>” “<ClientSecret>”

      PE14_2
      Forum|alt.badge.img+8
      • PE14_2
      • Valued Contributor
      • May 26, 2026

      Thanks missed that will try that first. 

      PE14_2
      Forum|alt.badge.img+8
      • PE14_2
      • Valued Contributor
      • May 26, 2026

      That is working there is connection only the results are not what i am expected yet have to errors in blueprint but when I run Scan Blueprint ID everything is wrong 

      Terms & ConditionsAccessibility statement