Automatic Update Explainer
This section provides an overview of Auto Update functionality.
Auto update simplifies client version management for organizations, applies critical security updates as they become available, and will help ensure the Zoom client remains within the rolling 9-month release window once implemented.
Update Schedules
Organizations and customers who use the automatic update feature have the ability to select either a fast or slow update schedule.
Fast updates will upgrade to the latest client version within a few days of release
These releases will have the newest client features and updates available, but may experience occasional client instability.
Slow updates will prompt users to upgrade within a few weeks of release
Zoom will generally promote a new release from the Fast to the Slow audience within two weeks of release, unless the need for a critical fix is discovered during that period.
Users will have different client versions enforced depending on their selected update schedule
As an example, consider a client running version 5.10.0 when version 5.10.1 is released. There are two possible scenarios depending on the selected schedule:
Fast schedule, where there is no minimum version
The client will install version 5.10.1.
Slow schedule, where Zoom’s determined stable version is 5.10.0
The client will retain version 5.10.0
While version 5.10.1 is technically released and available, the slow schedule client will not install it because it has not yet been marked as the stable version by Zoom.
Critical security updates will be deployed to both fast and slow schedules
Zoom will deploy any critical security updates to both fast and slow channels. There is no ability to opt out of this behavior for either schedule.
Client updates trigger when the current version is below the selected update speed’s minimum version
Each update speed has its own minimum version threshold. Client updates trigger when the client’s version is lower than the minimum version for the configured update speed.
Once new updates are released, Zoom staggers the availability of the new client version across an increasing percentage of clients so all users will not receive the update at the same time.
Manage Auto Update
This section details advanced configuration options regarding auto update functionality.
Zoom Recommendation For the best experience, Zoom recommends enabling auto update with no additional configurations.
Windows MSI and macOS PKG installers don't have automatic updates enabled by default
Mass deployment meeting clients for IT Admins, like the MSI and PKG installers, won't automatically install updates unless configured to do so through MSI switches or Group Policy (GPO) for Windows devices, or a PLIST for Mac devices.
Windows EXE and macOS DMG installers do have automatic updates enabled by default
Standard meeting clients, like the EXE and DMG installers, do have automatic updates enabled by default, and users can opt into fast or slow updates at their discretion. Administrators can opt standard meeting clients out of automatic updates using Windows GPO or macOS PLIST parameters.
Administrators can control the automatic update behavior of any installer
Warning
Zoom updated automatic update configuration parameters to support a new system with Zoom client version 5.10.3. All new automatic update keys begin with the prefix AU2_.
Enabling any AU2_ key will disable legacy parameters for: ZoomAutoUpdate, EnableSilentAutoUpdate, SetUpdatingChannel, and AlwaysCheckLatestVersion.
Customers using legacy parameters should update them to the AU2 values to avoid service disruption. Refer to our support documentation on mass deployment for Windows, Group Policy options, mass deployments for Mac devices, and enterprise auto update policies for more information.
Windows MSI deployments can include the AU2_EnableAutoUpdate parameter to enable automatic updates Administrators can configure MSI deployments to enable automatic updates using the parameter AU2_EnableAutoUpdate with a value of true in their install string. Automatic updates will be disabled if the MSI parameter is not included or set to false.
- Windows MSI and EXE deployments both respect the AU2_EnableAutoUpdate GPO setting to control automatic updates
MSI switches will not work on the Windows EXE installer, but both installations will respect the same AU2_EnableAutoUpdate GPO setting. Setting the GPO configuration to a positive string value (e.g., “true” or “1”) will enable automatic updates. Using a negative value (e.g., “false” or “0”) will disable the automatic update function.
macOS PKG and DMG deployments both respect the AU2_EnableAutoUpdate PLIST parameter to control automatic updates DMG-based deployments will have automatic updates enabled by default, but administrators can enable or disable automatic updates for both installers using the parameter AU2_EnableAutoUpdate with respective “true” or “false” values.
Administrators can disable automatic updates and require manual updates, or disable updates completely Administrators can require users to manually update their client or disable client updates completely with the AU2_EnableManualUpdate parameter. If the AU2_EnableAutoUpdate parameter is disabled, configuring AU2_EnableManualUpdate with a positive value (e.g., “true” or “1”) will require users to manually check for and apply updates. Configuring this parameter with a negative value (e.g., “false” or “0”) will not allow the client to update under any circumstance. If this setting is not defined, it will default to true.
Automatic updates can install on a schedule or when devices are idle Administrators can configure devices to look for device updates on a set schedule using the AU2_SetUpdateSchedule parameter with a string value. If this policy is configured with a valid string, the client will download the update package within the specified time period. The format of this string should be HHMM-HHMM, for example: "0900-1800" means 09:00 to 18:00, "1800-0400" means 18:00 to the next day 04:00. Alternatively, administrators can configure devices to update only when they are idle with the AU2_InstallAtIdleTime parameter. This setting is disabled by default and must be configured with a positive value (e.g., “true” or “1”) to enable. The AU2_InstallAtIdleTime parameter can be further defined when paired with the AU2_SafeUpgradePeriod parameter with a string value. If this policy is a valid string, the client will install auto updates within the specified time period when idle. The format of this string should be HHMM-HHMM, for example: "0900-1800" means 09:00 to 18:00, "1800-0400" means 18:00 to the next day 04:00.
Automatic updates will install without user prompt once they are enabled
Enabling automatic updates will passively enable a parameter that quietly installs client updates without requiring user prompt. Updates will install on application restart unless otherwise prompted and will not interrupt ongoing meetings. After an update is applied, users will receive a notification their client was successfully updated.
Administrators can change the client behavior to prompt users to update Windows and MacOS administrators can change automatic background updates and prompt the user to approve the update installations. Using the AU2_EnableUpdateAvailableBanner parameter with a positive value (e.g., “true” or “1”) within the PLIST, install string, or GPO configuration will prompt the user to upgrade the client if an update is available. If this setting is not defined, it will default to false. Additionally, the client can prompt users to update when exiting a meeting or webinar if the AU2_EnablePromptUpdateForAU2 parameter is configured with a positive value (e.g., “true” or “1”) within the PLIST, install string, or GPO configuration. If this setting is not defined, it will default to false.
Post-update notifications can be turned off After an update is applied, users will receive a notification their client was successfully updated. Administrators can disable this feature with the AU2_EnableUpdateSuccessNotification parameter configured with a negative value (e.g., “false” or “0”) within the PLIST, install string, or GPO configuration.
The default update speed is slow, but administrators can enforce either update speed
Administrators can enforce specific update speeds with the AU2_SetUpdateChannel parameter in the install string, GPO, or PLIST settings. A value of “0” will use the slow schedule and a value of “1” will use the fast schedule. If this parameter is not defined, it will default to slow.
Zoom update configuration settings can be hidden within the client
Zoom update settings located within General client settings can be hidden using the AU2_EnableShowZoomUpdates parameter set to a negative value (e.g., “false” or “0”). If this setting is not defined, it will default to true.
Additional Resources
Last updated
Was this helpful?