Why doesn't Zoom standardize their VDI application version numbering format?

[andrewm]

Zoom VDI application version numbering is all over the place. This adds complication when automating version checking/updating rules and creates confusion when trying to explain to users which plugin versions are compatible with a specific VDI desktop version.

As an example, the current Zoom VDI client version is listed on the website with four numbers separated by dots: "6.1.14.25530", but in the Zoom application, it's the build number is in parentheses, such as "6.1.14 (25530)" and in Windows Programs and Features the patch number "14" is dropped and  only the major, minor, and build number are included, separated by dots, i.e. "6.1.25530"

Meanwhile, the non-VDI Zoom Desktop application uses more consistent version numbering which always lists the major, minor and patch versions separated by dots, followed by the build number in parentheses.

Is there some reason for the inconsistency in the numbering format for the VDI components?

[tommy]

Hello  , happy to answer your question, 

This is due to the difference between the exe installer and MSI installer. For the VDI client, a reliable way to check the VDI client and plugin version is to use ZoomVDI WMI: https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0063903 uing the command Get-WMIOb...

Best,

Tommy

@andrewm