Configuration Profile to Set Meraki Agent to Allow in Accessibility

[tschwartz]

I created a Configuration Policy to set the Meraki Agent to Allow in Accessibility so my team can get the Remote Desktop functionality of Meraki's System Manager to work without end users needing Admin credentials.

I used this thread as a reference:
https://www.jamf.com/jamf-nation/discussions/35175/enabling-privacy-accessibility-setting-for-ms-tea...

Then, I got the App Identifier and Code Requirements for the Meraki agent here:
https://documentation.meraki.com/SM/Profiles_and_Settings/Privacy_Preferences_Policy_Control_(PPPC)_...

I deployed the configuration policy but it didn't work. The agent is still unchecked. The config policy log still shows that is successfully completed.

I have attached screenshots for reference. Any suggestions? What am I missing?

[erichughes]

We are running into the same issue did you find a resolution?

[perren]

Looks like you have Identifier Type set to Path, but specify a Bundle ID.

Try changing it and see if that does the trick.

[erichughes]

Both Path and Bundle ID claim to complete in the log but I never see anything in Accessibility, Checked or Unchecked. However it does seem to work as Path, even though it isn't visibly listed in Accessibility. The Meraki Screen sharing is a two part enable, though, and the second part of enabling the Screen Recording does still have to be done by the user. There is only the option for Deny via Profile. But this at least takes admin credentials out of the precess.