The VDI client host installer is a MSI file type that can be deployed through standard software and device management tools, like Microsoft Intune or Microsoft Systems Center Configuration Manager. The plugin installers are available as a MSI for Windows, PKG for macOS, and DEB, RPM, or a zipped package for Linux platforms, which can be similarly deployed through device management software.
Note: The VDI client and plugin are two separate programs with their own respective physical install locations.
This article covers:
The VDI client, known as the host installer, is installed on the virtual desktop as an application, while the VDI plugin is installed on devices used to access the VDI, such as a thin client or local PC.
When installing for the first time, Zoom recommends admins install the VDI plugin on thin clients first, then install the VDI client on the virtual desktop environment. This initial installation will ensure your virtual desktop users experience optimized performance when using the Zoom the first time they start the application because the VDI plugin is already installed and ready to connect to the Zoom application.
When updating the VDI client and plugins, however, admins should update the VDI client on the virtual desktop environment first, then update the VDI plugin on thin clients. The client host installer should always be upgraded first to maintain compatibility and avoid issues with an incompatible VDI client, and if the VDI plugin is updated before the client, the client will not connect to the plugin, forcing the VDI client into Fallback Mode.
Notes:
The Zoom VDI client and plugins are installed in the following locations by default.
Location of VDI client installation
Location of VDI plugin installation
The VDI client and plugin each contain ways of identifying if they are connected to each other, as well as the type of connection established.
Users can confirm connectivity by accessing the VDI statistics in the Zoom desktop client. The diagnostic information available between the VDI client and plugin’s connection, in addition to the VDI server’s and the plugin device’s performance, is displayed in the VDI tab.
The Windows plugin contains its own connection status, which can be viewed by inspecting the icon from the system tray.
A pop-up box will appear. In the bottom left corner, you can verify VDI connectivity by checking the displayed connection status.
If neither the client nor plugin are showing a Connected status, the VDI client will operate in Fallback Mode without any media optimization.
The VDI client is an MSI file type that is capable of utilizing the same switches as the standard client MSI program and can be deployed through normal software and device management tools, such as Intune or SCCM.
Learn which MSI switches are available.
The VDI client is responsive to standard GPO settings through the same registry location as the standard client (HKCU\Software\Policies\Zoom\etc). Any preconfigured GPO settings for the standard Zoom client will work with the VDI Client.
Learn which GPO options are available.
The VDI client behavior can be refined for select situations through registry keys, such as controlling client performance in Fallback Mode or feature enablement and disablement. Additional settings can be configured to create alert messages, restrict data flow, enforce optimizations, and more.
Learn which VDI-specific registry settings are available.
The plugin is not backwards compatible with older versions of the Zoom Meeting client. The plugin must always be equal to or lower than the VDI client version.