Skip to main content
Solved

screenshot MacOS 15

  • May 13, 2025
  • 9 replies
  • 80 views
tdenton
Forum|alt.badge.img+11

Hello

We recently updated our Mac estate to MacsOS 15.

I have noticed issues with taking screenshots

We deploy two base profiles one for staff devices one for shared lab devices.
Both have Allow screenshots and screen recording (macOS 10.14.4 or later) set under Functionality.

The shortcut key just does't seem to do anything but works fine on staff devices using the same setting.

I dont belive Im blocking it elsewhere.

Any idea 

Thanks

Capture a portion of the screen

Press Shift-Command-4, then move the crosshair pointer to where you want to start the screenshot. Press the mouse or trackpad button, drag over the area you want to capture, then release the mouse or trackpad button.



Best answer by tdenton

As I say it works fine on a physical mac I have in my home office with the same build as a lab. So it would suggest its something to do with vnc.

I assume if returns nothing there no conflicts.

tdentonadmin@M-5c1bf48bd781 tdenton % sudo /usr/bin/osascript -l JavaScript << EOS $.NSUserDefaults.alloc.initWithSuiteName('com.apple.screencapture').objectForKey('keyForDisablingScreenshots').js EOS Password: tdentonadmin@M-5c1bf48bd781 tdenton %

 


just been speaking with some of our operations colleagues and they have confirmed it does work in labs. So it appears to be limitation of vnc.

Thanks everyone for there contrubutions @sdagley  @AJPinto 

Nice to use some of Jamf 300 bits as custom schemas is covered there

    9 replies

    AJPinto
    Forum|alt.badge.img+26
    • AJPinto
    • Legendary Contributor
    • May 13, 2025
    • What happens when a user manually runs the screenshot.app? 
    • What happens when you remove the Configuration Profile?
    sdagley
    Forum|alt.badge.img+25
    • sdagley
    • Jamf Heroes
    • May 13, 2025

    @tdenton Do you have any other profiles with a Restrictions payload applied? That will cause problems because if you haven't allowed screenshots in another profile being applied it is undefined which profile will end up applying that setting. This is a longstanding problem with the lack of control over exactly what keys will be applied using the Restrictions payload editor in Jamf Pro. You can get much more granular results using the Application & Custom Settings payload and custom schemas to set only the restrictions you want: https://www.jamf.com/blog/profilecreator-manifests-now-available-for-jamf/

    tdenton
    Forum|alt.badge.img+11
    • tdenton
    • Author
    • Valued Contributor
    • May 14, 2025
    • What happens when a user manually runs the screenshot.app? 
    • What happens when you remove the Configuration Profile?

    screenshot app works fine on the handfull of machines I checked.
    Shift-Command-3 capture the whole screen and this work on some machines I tested.
    I removed profile from my test mac and  Press Shift-Command-4 normal bring up crosshair to select what you want to screenshoot. This didnt work with the profile or without it.
    I built a fresh production machine yesterday and keyboardshort cut works no problem machine, its in my home office so much easier to test.
    Im accessing these machine via VNC wondering if this has something to do with it.

    It seems to keyboard shortcut Press Shift-Command-4 which doesnt work.

    Very puzzled 



    tdenton
    Forum|alt.badge.img+11
    • tdenton
    • Author
    • Valued Contributor
    • May 14, 2025

    @tdenton Do you have any other profiles with a Restrictions payload applied? That will cause problems because if you haven't allowed screenshots in another profile being applied it is undefined which profile will end up applying that setting. This is a longstanding problem with the lack of control over exactly what keys will be applied using the Restrictions payload editor in Jamf Pro. You can get much more granular results using the Application & Custom Settings payload and custom schemas to set only the restrictions you want: https://www.jamf.com/blog/profilecreator-manifests-now-available-for-jamf/


    Been looking through all my config and can't locate any clashes.

    Perhaps deploying it through the method you suggusted would be better.

    Thanks

    tdenton
    Forum|alt.badge.img+11
    • tdenton
    • Author
    • Valued Contributor
    • May 14, 2025

    @tdenton Do you have any other profiles with a Restrictions payload applied? That will cause problems because if you haven't allowed screenshots in another profile being applied it is undefined which profile will end up applying that setting. This is a longstanding problem with the lack of control over exactly what keys will be applied using the Restrictions payload editor in Jamf Pro. You can get much more granular results using the Application & Custom Settings payload and custom schemas to set only the restrictions you want: https://www.jamf.com/blog/profilecreator-manifests-now-available-for-jamf/


    I have managed to create a custom schema for allow screenshot  it also meant creating something to allow screensharing so I could reach me machine onsite.

    With both of those applied and removing the orginal profile it still wont work.
    Shift-Command-4 just wont do anything

     

    sdagley
    Forum|alt.badge.img+25
    • sdagley
    • Jamf Heroes
    • May 14, 2025

    I have managed to create a custom schema for allow screenshot  it also meant creating something to allow screensharing so I could reach me machine onsite.

    With both of those applied and removing the orginal profile it still wont work.
    Shift-Command-4 just wont do anything

     


    @tdenton I just reviewed this thread, and I initially missed your comment about being on VNC when seeing this behavior. That definitely could have an impact on the shift-command-4 capture process but short of trying it while hands-on with a Mac it's not working on I don't know how you can be sure.

    I'll also mention this is how you can check for dueling Configuration Profiles applying the same setting (credit to jmahlman posting an example of this query on Mac Admins Slack):

    sudo /usr/bin/osascript -l JavaScript << EOS $.NSUserDefaults.alloc.initWithSuiteName('com.apple.screencapture').objectForKey('keyForDisablingScreenshots').js EOS

    Substitute the actual key name of the Disable Screenshots key for keyForDisablingScreenshots (it isn't an option in the copy of the com.apple.screencapture.json file I'm using.

     

    tdenton
    Forum|alt.badge.img+11
    • tdenton
    • Author
    • Valued Contributor
    • May 14, 2025

    @tdenton I just reviewed this thread, and I initially missed your comment about being on VNC when seeing this behavior. That definitely could have an impact on the shift-command-4 capture process but short of trying it while hands-on with a Mac it's not working on I don't know how you can be sure.

    I'll also mention this is how you can check for dueling Configuration Profiles applying the same setting (credit to jmahlman posting an example of this query on Mac Admins Slack):

    sudo /usr/bin/osascript -l JavaScript << EOS $.NSUserDefaults.alloc.initWithSuiteName('com.apple.screencapture').objectForKey('keyForDisablingScreenshots').js EOS

    Substitute the actual key name of the Disable Screenshots key for keyForDisablingScreenshots (it isn't an option in the copy of the com.apple.screencapture.json file I'm using.

     


    As I say it works fine on a physical mac I have in my home office with the same build as a lab. So it would suggest its something to do with vnc.

    I assume if returns nothing there no conflicts.

    tdentonadmin@M-5c1bf48bd781 tdenton % sudo /usr/bin/osascript -l JavaScript << EOS $.NSUserDefaults.alloc.initWithSuiteName('com.apple.screencapture').objectForKey('keyForDisablingScreenshots').js EOS Password: tdentonadmin@M-5c1bf48bd781 tdenton %

     

    tdenton
    Forum|alt.badge.img+11
    • tdenton
    • Author
    • Valued Contributor
    • Answer
    • May 14, 2025

    As I say it works fine on a physical mac I have in my home office with the same build as a lab. So it would suggest its something to do with vnc.

    I assume if returns nothing there no conflicts.

    tdentonadmin@M-5c1bf48bd781 tdenton % sudo /usr/bin/osascript -l JavaScript << EOS $.NSUserDefaults.alloc.initWithSuiteName('com.apple.screencapture').objectForKey('keyForDisablingScreenshots').js EOS Password: tdentonadmin@M-5c1bf48bd781 tdenton %

     


    just been speaking with some of our operations colleagues and they have confirmed it does work in labs. So it appears to be limitation of vnc.

    Thanks everyone for there contrubutions @sdagley  @AJPinto 

    Nice to use some of Jamf 300 bits as custom schemas is covered there

    sdagley
    Forum|alt.badge.img+25
    • sdagley
    • Jamf Heroes
    • May 14, 2025

    As I say it works fine on a physical mac I have in my home office with the same build as a lab. So it would suggest its something to do with vnc.

    I assume if returns nothing there no conflicts.

    tdentonadmin@M-5c1bf48bd781 tdenton % sudo /usr/bin/osascript -l JavaScript << EOS $.NSUserDefaults.alloc.initWithSuiteName('com.apple.screencapture').objectForKey('keyForDisablingScreenshots').js EOS Password: tdentonadmin@M-5c1bf48bd781 tdenton %

     


    If run as I posted it the command would return nothing because "keyForDisablingScreenshots" was just a placeholder since I could not find the actual key needed in that payload.

    Terms & ConditionsCookie settingsAccessibility statement