Wednesday
We are deploying beyond trust jump clients on all of our macs and following the instructions by setting up a configuration profile to enable all screen sharing, disk sharing other settings on the backend through jamf without users being notifiied however still some of the users are presented with this which is annoying for the user as well as IT team . what could have been missing in the configuration profile . any help would be greatly appreciated
Solved! Go to Solution.
Wednesday
Nope, you did not miss anything. This is working exactly as Apple Intended. Note how screen recording says "allows standard users to allow access", MDM cannot grant this permission it can only remove the admin check to grant the access per Apples design. Beyond Trust launches its screen recording agent upon install, so that is when the users will see the prompt.
Wednesday
Nope, you did not miss anything. This is working exactly as Apple Intended. Note how screen recording says "allows standard users to allow access", MDM cannot grant this permission it can only remove the admin check to grant the access per Apples design. Beyond Trust launches its screen recording agent upon install, so that is when the users will see the prompt.
Wednesday
Thanks as always @AJPinto its clearly understood why the prompt is displayed .. Appreciate your swift response.
Thursday
Beyond Trust have an update coming that makes use of new APIs that'll prevent that popup. For software that hasn't been updated yet, that's the expected behavior. It's one of the only things holding us back on deploying Sequoia in our environment. We've got to upgrade our Beyond Trust back-end in steps. 😒
Thursday
The prompt that the OP is showing will not go away even with the update. That is Apple's initial screen recording prompt, requiring the user to intentionally turn on screen recording. As @AJPinto mentioned, it can't be set automatically.
What the new APIs will do is prevent the user from seeing the monthly "XXXX" is using Screen Recording prompt to remind the user.
Thursday
@cwaldrip interestingly none of the users on Sequioa has reported this. i am assuming the latest update from BT has fixed it for OS 15.0 and up . we also had a long hold to update to sequioa for only this reason but recent update might have fixed it .