I suppose we need more information from you as to what is going on. What I'm reading, you are having issues from "within" a Configuration Profile, but did not mention what the issues are. Then the policy for zoom is not working after an app (figuring update was left off). 

Are you having issues with screen recording, or with the policy deploying zoom itself? If screen recording is breaking after updating the app, I would make sure the code requirement did not get changed assuming it was working before.

Hi @AJPinto , 

Please see my screenshoots below, I can't share a screenshot of the certificate script 

Validate that your Code Requirement is:

identifier "us.zoom.xos" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = BJ4HAAB9B3

Hi @motorcitymike13, 

The only part of the my Certificate that is different is BJ4HAAB9B3, why that make different?

---

@Lion55 wrote:

Hi @motorcitymike13, 

The only part of the my Certificate that is different is BJ4HAAB9B3, why that make different?

---

Yes, it makes a difference. The Code Requirement must be exact, including the bundleID which you suggested is different for you.

I use the app blow to get the code requirements as I am too lazy to remember the terminal commands. 

https://hcsonline.com/support/apps/show-me-your-id 

First thing you can get the code requirement by running this command in terminal : 
codesign -dr - /Applications/Zoom.us.app.
In the Output , Designated part will be your code requirement.

Note : Change the application name based on the requirement.

Second Thing, To create this Config profile, you can utilize PPPC Utility application : https://github.com/jamf/PPPC-Utility
You just need to add/drag the application, it will give you the identifier and code requirement. You can just utilize that or You can perform your changes in that application then save and upload it to jamf pro. 

Hi All, 

The configuration shared by all, The issue still exists after making the changes, are there any other options?

Thanks

Here's a potential pitfall:

If the screen sharing has been denied previously, simply applying the profile doesn't reset the setting that the user declined to permit the feature. This profile will affect all freshly built Macs, and any user encountering the prompt for the first time. However, you may need to push a shell command or script to reset the prompt so it asks again:

tccutil reset All us.zoom.xos

or for screen sharing only:

tccutil reset ScreenCapture us.zoom.xos

That will reset any user-facing prompts, which (in conjunction with the profile) a standard user can be prompted to allow the screenshare.