Zoom Update is requiring Admin Credentials in Self Service

@cvangorp, my understanding from other discussions here (I haven't personally tested) is that configuration profiles only work with the Zoom IT package.

@talkingmoose , I just wanted to add my thanks for the Zoom JSON manifest. The installation of the ZoomIT package (5.2.1) I deployed this morning is working as expected with my configured settings on macOS Catalina.

Same experience as @timgep mentioned. ZoomInstallerIT520.pkg deployed with /Library/Preferences/us.zoom.config.plist that has ZAutoUpdate set to True. User gets Update Zoom notification "To avoid problems caused by this version of macOS, please update Zoom to the version compatible with your device." User also has the Update to the version compatible with your device banner in the app and Update button for user to click. However, Update basically downloads the install file zoom_x9.pkg into the hidden /var/folders and its installation still requires admin privilege. This does not match Zoom's documentation: Allow updates through the client by users.

After some further testing, we most likely will be using the jamf new policy deferral function for managing Zoom updates instead of the app's autoupdate feature (which doesn't seem to work without admin privilege) or the patch management policies.

So it will be one single ongoing check-in policy to deploy the latest ZoominstallerIT package with the deferral duration set to 1 day. The users will get the prompt when the policy runs to start the installation now, in 1 hour, 2 hours, 4 hours or 1 day. The target will exclude the machines already got the latest versions we deploy so the policy should only run once on each machine. For the ongoing maintenance, this means there will be only two things to be updated: the package in the policy and the zoom-latest-installed smart group criterial application version number. No flushing log, No patch management, No forced application quit or sudden interruption to the user's Zoom meeting.