AU2 policies/auto-update not working as expected

[DDIT]

I deployed 6.0.10 to an endpoint with the following...

msiexec.exe /i "ZoomInstallerFull.msi" zConfig="AU2_EnableAutoUpdate=true;AU2_SetUpdateChannel=1;AU2_EnableShowZoomUpdates=true;AU2_InstallAtIdleTime=true;AU2_EnableUpdateAvailableBanner=true;AU2_EnablePromptUpdateForAU2=true;AU2_EnableUpdateSuccessNotification=true" ALLUSERS=1 /qn /norestart /log output.log

Zoom installed successfully. This version was intentionally chosen as it is slightly older than the current version 6.2.5. The option above AU2_SetUpdateChannel=1 was included as I understand this should install the latest available version.

After waiting a few days, nothing happens on the endpoint. Zoom is open and has been running for hours, even overnight. Zoom has certainly been "idle" enough to trigger the update, but nothing is happening.

Separely, we also have GPO's applied to this computer (not user), which are shown below

What am I doing wrong? The documentation is unclear when talking about deprecated policies and the introduction of the newer AU2 policies.

I have read elsewhere that the auto-update won't work if Zoom is installed in the system context (ie C:\Program Files), not the user context (ie %appdata%). Is that correct?

The problem with the user context is when users don't login to that same computer for a few months (our workforce is very mobile) they will have an outdated version of Zoom in their profiles. I know, this isn't a major concern, but it plays havoc with vulnerabilities scanners. 

I would prefer Zoom to be installed in the system context, which is easier to manage on shared workstations. Chrome manages it by having a service or scheduled task to update itself. Heck, even Adobe has worked some black magic to allow users to upgrade Creative Cloud apps installed on the system without needing admin rights.

[snap-rz]

@DDIT Please check this doc:https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0063814

Upon release, every new client version is added to the fast track and is distributed to a percentage of random users on the fast track each day, with the rollout typically accelerating over the course of the week.

6.2.5 was released two days ago, so maybe your machine is not in the scope. Your command is right, just needs to set the channel to Slow for testing. (The Slow channel was set to 6.0.12 a month ago, the percentage should be 100%)

[DDIT]

@snap-rz Thanks for the reply. I will reinstall with the AU2_SetUpdateChannel=0 for the slow channel. I found this article highlights the versions which are current in each channel https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061900 - looks like 6.1.12 is the curent slow channel release.

Regarding my 2nd point in my original post, will these policies work if the app is installed in the System context? ie, will users be able to update the app without needing admin rights? 

[snap-rz]

Sorry for the typo, yes it is 6.1.12.

For "without needing admin rights", yes.

[DDIT]

Hi @snap-rz , my Zoom client is still not updating. I have left the Zoom app running overnight a few times.

I checked my deployment command and compared to others I found on forums online and realised I should have used "1" instead of "true" for boolean values (or maybe it doesn't matter, but others have used 1/0 and reported that as working, so I updated my command to match)...

msiexec.exe /i "ZoomInstallerFull.msi" zConfig="AU2_EnableAutoUpdate=1;AU2_SetUpdateChannel=0;AU2_EnableShowZoomUpdates=1;AU2_InstallAtIdleTime=1;AU2_EnableUpdateAvailableBanner=1;AU2_EnablePromptUpdateForAU2=1;AU2_EnableUpdateSuccessNotification=1" /qn /norestart /log C:\temp\ZoomInstall.log

I see in C:\temp\zoominstall.log that it is picking up the AU2 switches.

I do have some GPO's being applied at the machine level. I have now just disabled those from apply to my test machine, so will wait for that to filter down and check back later. 

[DDIT · Accepted solution]

Ok, turn out my GPO's were interferring. I had "Set to enable auto update = disabled". Although I believe this was the legacy setting, so wasn't sure it would have affect if AU2 policies were also in use, but it seems it does. With this setting set to 'enabled' or 'not configured' my Zoom started prompting for updates now. Thanks for all the help and suggestions.