Skip to main content

I saw this on a blog this morning, posting here to raise visability.

Much has already been written about the new monthly screen recording prompt in macOS 15 Sequoia. After a bit of research, there is a way to get rid of the prompts; kinda tacky, but does work.

The good news is that there's a way to stop the prompts forever

defaults read ~/Library/Group\\ Containers/group.com.apple.replayd/ScreenCaptureApprovals.plist
This file is protected by TCC, so to access it you'll need to grant Full Disk Access to Terminal app.

{ 
 "/Applications/Shottr.app/Contents/MacOS/Shottr" = "2024-09-21 12:40:36 +0000"; 
}

In the plist file, the keys are the paths of the executable files with screen recording permission, and the values are dates. I'm using the Shottr screenshot tool as an example.

To stop the prompts forever—for the rest of your life, anyway—set the date to far in the future, for example, the year 3024 instead of 2024.

defaults write ~/Library/Group\\ Containers/group.com.apple.replayd/ScreenCaptureApprovals.plist "/Applications/Shottr.app/Contents/MacOS/Shottr" -date "3024-09-21 12:40:36 +0000"

You'll need to do this for each app, and afterward logout and login again so that the replayd process recognizes the new defaults.

Not gonna do this, but good to have the knowledge; we will see if Apple provides something better.

 

To the above, once the profile is deployed on 15.1 and MacOS os upgraded afterwards to 15.2, all seems to work fine. But when one deploys the profile AFTER the upgrade to 15.2, it doesn't seem to suppress screen capture alerts.


Are you using a Jamf restrictions profile? The new keys were added to the Restrictions profile options in Jamf Pro 11.12.x. In our case, we had already created and deployed custom profiles for four options that were added, resulting in duplicate keys with opposing values. I can elaborate on how we fixed this issue, if it is pertinent.


Are you using a Jamf restrictions profile? The new keys were added to the Restrictions profile options in Jamf Pro 11.12.x. In our case, we had already created and deployed custom profiles for four options that were added, resulting in duplicate keys with opposing values. I can elaborate on how we fixed this issue, if it is pertinent.


Actually, I did test Restrictions profile options in Jamf Pro 11.12.x. which did seem to work for me on 15.2 but problems is this payload comes with lots of default keys I don't want within my payload.
So guess a custom profile would be best, problem is it doesn't seem to work for me when deploying it on 15.2


Are you using a Jamf restrictions profile? The new keys were added to the Restrictions profile options in Jamf Pro 11.12.x. In our case, we had already created and deployed custom profiles for four options that were added, resulting in duplicate keys with opposing values. I can elaborate on how we fixed this issue, if it is pertinent.


While it may not be pertinent I would be happy if you can elaborate on how you handled those duplicate keys.


While it may not be pertinent I would be happy if you can elaborate on how you handled those duplicate keys.


This is specific for our environment:


1. Change scope of “Restrictions” profile from “All Targets” to “Specific Computers” and scope targets:

Targets:

- Add 12.0 Machines

- Add 13.0 Machines

- Add 14.0 Machines

Exclusions:

- Remove “15.0 and Newer Machines”

 

2. Clone Configuration Profile “Restrictions-Sequoia” and name it “Restrictions-Sequoia 15.2”

- Update version date in Description

- Update Category if needed

 - Remove any scoped groups so that it has only a target of a test machine.

- Edit Restrictions > Functionality

- Check box for “Bypass screen capture alert (macOS 15.1 or later)”

- Uncheck box for “Allow Apple Intelligence: Mail Summaries (macOS 15.1 or later)”

- Uncheck box for “Allow users to log in to external intelligence services (macOS 15.2 or later, supervised)”

- Uncheck box for “Allow integration with external intelligence services (macOS 15.2 or later, supervised)”

- Save “Restrictions-Sequoia 15.2”

 

3. Find the profile identifier from the test machine’s record.

 

4. Create a Smart Group “Profile - Restrictions-Sequoia 15.2 Installed” based criterion (example ID): Profile Identifier “is” ABCD1234-EF56-449F-9573-6BB705410C9D

 

5. Edit  “Restrictions-Sequoia”

- Edit Scope to Exclude “Profile - Restrictions-Sequoia 15.2 Installed”

- Save “Restrictions-Sequoia”

 

6. Exclude “Profile - Restrictions-Sequoia 15.2 Installed” from:

AI-Disable External Intelligence Integrations

AI-Disable External Intelligence Logins

AI-Disable Mail Summary

Disable Screen Access Request User Notifications

 

7. Edit “Restrictions-Sequoia 15.2”

- Scope to Smart Group “15.2 and Newer Machines”

- Save “Restrictions-Sequoia 15.2”