VDI installation and connectivity


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, and 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:

Prerequisites for VDI installation and connectivity

How to install or update the VDI Client and Plugin

The VDI Client, known as the Host Installer, is installed on the virtual desktop as an application. It is recommended that the Host Installer always be installed and/or upgraded first to maintain compatibility.

The VDI plugin should never be installed on a VDI desktop, and should only be installed on a device used to access the VDI, such as a thin client or local PC. It is recommended that the plugin be installed and/or upgraded last to avoid a disruption in compatibility with the VDI Client.

Notes:

Install locations

The Zoom VDI client and plugins are installed in the following locations by default. 

Location of VDI client installation

Location of VDI plugin installation

How to verify the VDI Client and plugin are connected

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.

Verify from the Zoom desktop client

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 machine's performance, is displayed in the VDI tab.

For more information, please visit the Support article on accessing VDI statistics.

Verify from the plugin

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.

Frequently asked questions about VDI installation and connectivity

Can I use MSI switches with the VDI Client?

The VDI Host Installer 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, like Intune or SCCM. For a complete list of the MSI switches available, please visit this Support article.

Can I configure Group Policy with the VDI Client?

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.

Are there additional configuration settings available?

The VDI Client behavior can be refined for select situations through registry keys, such as how the client will perform in Fallback Mode or feature enablement and disablement. Additional settings can be configured to create alert messages, restrict data flow, enforce optimizations, and more. For a full account of the registry keys and features we have available, refer to our VDI Client Registry Settings article.

What is the best way to install or update the VDI Client?

With frequent feature improvements to the VDI Client and the VDI Plugin, it is recommended that users always update the VDI Client first. Failure to update the client before the plugin will result in a disconnection between the client and plugin, forcing the VDI Client into Fallback Mode.

Is the VDI Plugin backwards compatible?

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’s version number.