cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Important updates from Zoom Support:

  • Starting February 3, 2025, Zoom Phone customers must add their phone numbers to an approved 10DLC campaign in order to use SMS/MMS capabilities on their numbers.

  • Introducing more live support options! More Zoom customers now have access to live agent chat support. Sign in and visit our Contact Support page to see all your available support options. We’re here to help!

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

andrewm
Newcomer
Newcomer

‎2024-12-04 01:41 PM

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?

Topics:
0 Likes
0 REPLIES 0