Zoom workspace requires admin credentials to update, clients are managed by ZDM

Forum|Forum|1 year ago
January 15, 2025
3 replies
0 views

Hi everyone,

We recently enabled ZDM to manage Zoom workspace on our Windows desktop computers, I managed to add 2 desktops by appending the Token string to the msi file during the client deployment

msiexec /i C:\Windows\Temp\ZoomInstallerFull.msi /quiet /qn /norestart /log install.log ZConfig=SetEnrollToken4CloudMDM=xxxx-xxxx-xxxx-xxxx

the only issue that I am currently facing is that when the end user trying to upgrade to a newest version of Zoom client they would be asked for the admin credentials, is there any way to do the update without having to enter the admin credentials or adding any switches to the ZConfig during the deployment?

I also have a question, why there is an icon next to any update setting in the portal with the symbol v. and I hover over it it would display 5.13.5?

the current Update Channel set to Slow,

the Zoom client at the desktops is Version: 6.2.5 (48876)

Allow users to configure auto-update for Zoom desktop client = ON

Update notifications - Zoom desktop client (Windows and Mac only) = ON

Allow users to manually check for updates - Zoom desktop client (Windows and Mac only) = ON

"Update to Auto Update defined version" is checked

please see the attached screenshots.

Thanks

Integrations

S

snap-rz

Employee

This should be a bug. Installing MSI will cause the cptService files to be deleted after the machine restarts.

Please check if there are any files under "C:\Program Files\Common Files\Zoom\Support" or "C:\Program Files (x86)\Common Files\Zoom\Support".

The root cause of the problem is that after installing this version of MSI, the deletion commands of the above directories will be written to the PendingFileRenameOperations of the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager. These commands will be executed after the machine is restarted.

This issue has been resolved in versions 6.3.1 and above.

M

MSaeedAuthor

Newcomer

Thanks for the reply, I checked the C:\Program Files\Common Files\Zoom\Support and it was empty, is there any way to grant the end user the privilege to update their Zoom clients without installing the version that overcomes this bug? is there any registry tweak for example?