VDI client registry settings


Registry keys can be used for troubleshooting or customizing the VDI setup you manage. If the registry key or subkey is not present, you can create it, and once created or edited, a quick restart of the Zoom client makes the change take effect. 

Using or editing registry keys for any purposes is not recommended for inexperienced users. For example, changing the LogLevel policy can generate a large amount of unnecessary log files.

All registry keys listed will work in the HKEY_LOCAL_MACHINE (HKLM) and HKEY_CURRENT_USER (HKCU) hives, except where otherwise noted. Zoom will check the current user directory, then check the local machine directory for the key. If the same key is set in both HKLM and HKCU hives, the value in the HKCU hive will take precedence. Keys only need to be configured on a virtual machine's registry table to take effect.

note icon
The VDI client also responds to MSI switches, which provides additional configuration possibilities. Learn more about mass deployment options for MSI installers.

Available templates

The following downloads contain the administrative templates, as well as registry files for specific versions of Zoom:

Windows desktop client 
Standard clientVDI client

Policies for version 5.10.3

 

Policies for version 5.10.6

 

Policies for version 5.11.0

 

Policies for version 5.11.3

 

Policies for version 5.11.3

 

Policies for version 5.12.0

 

Policies for version 5.13.0

 

Policies for version 5.13.5

 

Policies for version 5.13.10

 

Policies for version 5.14.5

 

Policies for version 5.14.10

 

Policies for version 5.15.3

 

Policies for version 5.16.0

Policies for version 5.16.0

Policies for version 5.16.10

Policies for version 5.16.10

Policies for version 5.17.0

 

Policies for version 5.17.5

 

Note: Each download includes .ADM and .ADMX files. If using the .ADM files, the policies will be located under Classic Administrative Templates.

Available VDI registry values

Note: Most of the following values are located at SOFTWARE\Policies\Zoom\Zoom Meetings with the final folder specified below. Any policies located elsewhere have their full location provided.

VDI Registry ValueDescriptionKeyValue type
Network and performance
UDPPortBegin,
UDPPortEnd
Specify port ranges when connecting with UDP. The range for ports are 1700 to 1800 or 64000 to 65000. The specified range cannot be less than 100.

If there are multiple users sharing the same VM machine, reserving 8 ports for each user is recommended.

Port range (7200-17210) is the default range for the Firewall inbound rules used by the Zoom VDI client on the VM side. Before testing UDPPortBegin-End, ensure the following policies are configured as such:
  • DisableUDPBridge is disabled (0)
  • DisableICABridge is enabled (1)
  • DisableMMRDirect is enabled (1)
  • A new Firewall inbound rule, such as Port range (17000-65000)
\VDIDWORD
DisableUDPBridgeBy default, there are no restrictions. Enabling this policy will prevent UDP connections.

 

If your thin client cannot connect to the Virtual Desktop VM by UDP, enabling this policy prevents any UDP connection between VM and thin client, which may in turn speed up the process of joining a meeting.

Note: If this is configured on the thin client, those settings will override the settings on the VM.

\VDIDWORD
DisableICABridge

By default, there are no restrictions. Enabling this policy will prevent ICA connections.

If the MMR is inaccessible for the thin client, the UDP connection from the thin client to the VM is not available, and this policy is enabled, the client will display the "Zoom Plugin can not connect to the server according to your Zoom config and network status" message and attempts to join or start meetings will fail.

Note: If this is configured on the thin client those settings will override the settings on the VM.

\VDIDWORD
DisableMMRDirectBy default, there are no restrictions. Enabling this will prevent direct MMR connections.

If your firewall has blocked the zoom connection process to Zoom MMRs on thin clients, enabling this policy may speed up the process of joining a meeting.

Note: If this is configured on the thin client those settings will override the settings on the VM.

\VDIDWORD
DisableMMRDirect_Phone

By default, there are no restrictions. Enabling this policy will prevent connections between the thin client and Zoom Phone servers.

If your network firewall prevents the Zoom process from connecting to the Zoom Phone Server on the thin client, enabling this policy may speed up the process of connecting to Zoom Phone calls. If this is configured on the thin client, those settings will override the settings on the virtual desktop. 

\VDIDWORD
DisableUDPBridge_Phone

By default, there are no restrictions. Enabling this policy will prevent sending Zoom Phone audio over a UDP connection from the thin client to the virtual desktop

If your thin client cannot connect to the virtual desktop over UDP, enabling this policy may speed up the process of making a call. If this is configured on the thin client, the settings will override settings on the virtual desktop. 

\VDIDWORD
DisableChannelBridge_Phone

By default, there are no restrictions. Enabling this policy will Prevent sending Zoom Phone audio over a channel connection, such as the ICA protocol connection channel.

If your configuration is expected to use Direct or UDP, enabling this policy will prevent Zoom Phone from sending Zoom Phone audio over another protocol channel. 

\VDIDWORD
PingServerFromThinClientChoose how Zoom servers are pinged:
(0) from the VDI virtual machine
(1) from the thin client

When this policy is enabled, determining which Zoom server to connect to for meetings is based on the location of the thin client where the VDI plugin is located. If your thin clients are located in a different geographical location than your virtual desktops, enabling this configuration can reduce join time and latency, as a more local server connection may be chosen instead.

\VDIDWORD
PingServerFromThinClientOffloadConfRequest

By default, the VDI virtual machine uses the plugin’s public IP address to determine and connect to the most suitable Zoom Servers. This requires the PingServerFromThinClient policy to be set to 1.

This requires VDI version 5.14.10 or higher.

(0) - Ping from VDI VM and use the plugin’s public IP address to select the most suitable Zoom Zone Center (Default)
(1) - Ping from thin client.

\VDIDWORD
DisableDirectConnectionPKOnly impacts login/join meeting related requests.\MeetingsDWORD
DisableDirectConnection2WebDisable all direct connections to Zoom web service. This impacts all web services related to REST API.SOFTWARE\WOW6432Node
\Zoom VDI\PerInstall
String Value (REG_SZ)
AllowPluginDSCPMarkingThis policy controls if the plugin can apply DSCP tagging for audio and video traffic. Disabled by default (even if enabled in web settings). Enabling this policy will allow the plugin to include DSCP marking network traffic.

Note: DSCP marking must be enabled in the Zoom web portal for this to function on the plugin side.

\VDIDWORD
DSCPValueForAudio,
DSCPValueForVideo

Applies DSCP tagging for audio and video traffic using the specified values. If using any values besides the default (40 for video, 56 for audio), DSCP tagging requires admin privileges and the EnableIndependentDataPort policy is enabled.

Both values must be set for DSCP tagging to be applied and must be between 1 and 63. Otherwise, the value from the Zoom web portal (account settings) is used. These policies override the account settings if set, and don't require the user to be logged in to an account.

\VDIDWORD
FallbackModeSpecify the fallback mode behavior from the following presets:
(1) (Default) Normal mode (Behaves like the regular Zoom client) (Unoptimized Audio and Video is sent from thin client to virtual desktop using desktop protocol)
(2) Runs as a screen-share meeting (Audio and video are muted by default)
(3) A notification is displayed saying unable to meet and join
(4) A notification will display an error message, and when the user closes the prompt, the Zoom app will also be closed.
(5) Only video is disabled.
(6) Video and sharing are disabled.
(7) Video and computer audio are disabled.
\VDIDWORD
ServiceUnavailableTipMsgDisplay an admin-provided message when the client is in fallback mode 3 or 4. If this policy is not included or undefined, a default message is displayed. The message cannot be longer than 1024 characters.

Note: If a line return is required, "\n" should be used to add the line return.

\VDIString Value (REG_SZ)
FallbackModeTipMsgDisplay an admin-provided message when the VDI plugin is not usable and fallback mode is set to 1, 2, 5, 6, or 7. If this policy is not included or undefined, no message is displayed. The message cannot be longer than 1024 characters.

Note: If a line return is required, "\n" should be used to add the line return.

\VDIString Value (REG_SZ)
DisableBoostPowerScheme

By default, the VDI client will force the thin client power settings to high-performance mode. Enabling this policy prevents high-performance mode from being automatically enabled.

This policy only affects thin clients with a 2-core CPU or less.

\VDIDWORD

PhoneCallTipMsg

This policy disables the audio quality popup message. This requires Zoom VDI client version 5.15.2 or higher

(0) - (Default) "Poor network connection. Audio quality may be affected" notifications during phone calls will be displayed as needed. 
(1) - "Poor network connection. Audio quality may be affected" notifications during phone calls will be disabled. 

\VDIDWORD

DisableAWSPlatform

This policy disables connection attempts from the VDI meeting client to the VDI plugin for AWS WorkSpaces. 

(0) - (Default) Connections to AWS WorkSpaces platform are enabled. 

(1) - Connections to AWS WorkSpaces platform are disabled. 

\VDIDWORD
Install and update
EnableDifferentVersionTipBy default, no warning message is displayed when there is a version mismatch between the VDI client and VDI plugin. Enabling the policy displays the warning.\VDIDWORD
MinPluginVersionSet the minimum version to match your existing thin client plugin deployment.\VDIString Value (REG_SZ)
EnableVDIPluginAutoUpgrade

Disabled by default, enabling the policy enables the VDI plugin auto-update to install or upgrade VDI plugins if the VDI auto-update component has been installed on the thin client. This feature is currently only supported for Windows devices.

Adding this policy to the Windows Thin Client can be used to disable the auto-update feature for a specific device. For example, adding the policy to managed devices to disable updates internally, while disabling auto-update to update users' personal devices at home.

  • This requires Zoom VDI client version 5.10.0 or higher.
  • VDI Plugin Management software on client
    • Zoom VDI Plugin for Windows version 5.9.6 or higher
    • Zoom VDI Plugin for macOS version 5.12.6 or higher
\VDIDWORD
AutoUpdatePluginVersion

This policy specifies the Auto-update plugin version and will give priority to the specified version. If the specified version is not supported, the web server configuration will be used.

The plugin version must fall within a range of acceptable values that apply to each version of the host client. Values that are out of range will be ignored, and a value best suited for the host value will be used instead.

Note: A complete list of supported versions is available in the VDI plugin and Auto-Update plugin versions article/

  • This requires Zoom VDI client version 5.9.6 or higher
  • VDI Plugin Management software on client
    • Zoom VDI Plugin for Windows version 5.9.6 or higher
    • Zoom VDI Plugin for macOS version 5.12.6 or higher
\VDIString Value (REG_SZ)
UpdatePluginLaterBy default, the update prompt does not include a Later option. Enabling this policy modifies the prompt to include the Later option.

(0) Default (plugin auto-update later option is disabled)
(1) Include the Later option, which closes the dialog. The next time the user connects, the same dialog will be presented if the VDI plugin management software detects an action is still required. This policy requires Zoom VDI client version 5.11.6 or higher.
(2) Include the Later option, which waits until the user disconnects from their virtual desktop(s) and then performs the update. This policy requires the Zoom VDI client version version 5.13.0 or higher.

\VDIDWORD
PluginDLLSignatureCheck

By default for versions 5.16.10 and higher, the VDI client will not check signatures for DLL files in the VDI plugin installation path, in order to start more quickly. This policy can be enabled to force the the signature checks. 

(0) Skip the signature checks. 

(1) Force signature checks. 

\VDIDWORD
Logging, data storage, and data processing
AllowEnableLogBy default, the VDI Log Tool requires Admin privileges to enable logging and set the log level. This policy can be added to allow any user of the virtual desktop to use the VDI Log Tool to configure and collect logs.\VDIDWORD
LogLevelSpecify which logs are provided to Zoom:
(0) No log output
(1) Only output error logs
(2) Only output warning logs
(3) Only output info logs
(4) All output logs

Note: If set to generate no logs (0), there may still be some null log files generated. The log of the initialization process of the VDI plugin will always be generated.

\VDIDWORD
DisableVDIToolFileTransferBy default, the Zoom VDI log tool is unrestricted from retrieving log files from the remote client. When enabled, log file transfers from Plugin to VM are disabled when using the VDI log tool.

This requires VDI version 5.9.6 or higher.

\VDIDWORD
MaxLogFileSizeSet the maximum file size each log file can be. The value is set as a numerical value representing how many MBs a log file size can be, ranging from 1 to 100 MBs.

Note: Available only on the Windows thin client.

\VDIDWORD
MaxLogFileCountSet the maximum number of log files to be stored locally. The value is set as a numerical value representing how many log files are allowed, ranging from 8 to 50.

Note: Available only on the Windows thin client.

\VDIDWORD
UniqueDataDirBy default, user data is stored in the main data folder, located at %appdata%\zoomvdi\data. Enabling this setting, creates unique data folders for each user profile on that device.

Using the string "YES", will enable a unique folder within the path %appdata%\zoomvdi\data

SOFTWARE\WOW6432Node
\Zoom VDI\PerInstall
String Value (REG_SZ)
Audio and video
DisableSyncDesktopVolumeToTerminalThis policy will sync changes made for the Virtual Desktop volume slider in the OS taskbar to the Thin Client device, if the VDI speaker output selection is configured as Same as system. This policy requires VDI version 5.14.10 or higher.

Note: Changing the volume on the Thin Client directly will not sync to the Virtual Desktop and change the volume slider in the taskbar.

(0) - Sync volume changes made to the Virtual Desktop volume slider in the OS taskbar to the Thin Client device.
(1) - Volume changes are not synced (Default)

\VDIDWORD
AudioAECLevelBy default, standard echo cancellation is used. Advanced echo cancellation offers higher-quality audio, but requires more CPU usage on the thin client.

(1) Standard
(2) Advanced

\VDIDWORD
CheckHdxMediaOptimization

This policy determines if Zoom takes control of connected HID devices.

By default, the VDI client will check if Skype for Business or Teams are running (based on if lync.exe process is running), and, if either are active, the client will not force HID redirection. If enabled, the client will take control of HID devices. This policy requires Zoom VDI client version 5.10.6 or higher.

\VDIDWORD
HideAdvancedSettingsBy default, the advanced settings under Audio and Video in the Settings panel can be accessed by users. Enabling this will hide those Advanced settings.\MeetingsDWORD
DoTComplianceModeBy default, this mode is disabled and meetings will appear and operate as normal. Setting the following values have the associated in-meeting impact.
  • (1) Video is required to be on during the entire meeting and the user cannot disable it. Audio can still be muted/unmuted as needed.
  • (2) Video and computer audio are disabled, and only connecting to audio through phone dial-in or call-me is allowed. For a PMI meeting, the host still needs to check the telephone and computer audio settings before starting. The VDI client will enable computer audio if the host has enabled it on the PMI.

     

Note: This key must be used in the HKLM hive.

\MeetingsDWORD
DisableWallView7x7By default, Gallery view can display up to 49 video participants, if hardware and version (5.9.6 or higher) requirements are met. Enabling this policy limits gallery view to a maximum of 25 video participants.\VDIDWORD
ForceWallView3x3By default, Gallery view can display up to 25 video participants, if HD video is enabled. Enabling this policy limits gallery view to a maximum of 9 video participants.\VDIDWORD
DisableScreenshotOptimization

(Beta) This policy can be used to offload screen capture commands to the plugin side, where the screenshot can capture video received by the VDI plugin. This requires VDI version 5.14.10 or higher.

Currently, the default is disabled (1), but may be changed in a future release.

\VDIDWORD
Sharing
EnableShareAudioSoundBy default, the Share Sound option is disabled and hidden. Enabling this policy provides users with this option when starting a share and during a live share.\VDIDWORD
EnableOptimizeForVideoBy default, the Optimize for video clip option is disabled and hidden. Enabling this policy provides users with this option when starting a share and during a live share.\VDIDWORD
ShareSubscribeFpsDefine the maximum frame-rate when viewing shared content. Values can range from 1 to 5.\VDIDWORD
ShareCaptureFpsDefine the maximum frame-rate when capturing and sharing content. Values can range from 1 to 5.\VDIDWORD
DisableShareOffloadBy default, processing of incoming shared content is offloaded to the local device. Enable this policy to disable offloading.

(0) VDI view share offloads processing.
(1) VDI view share does not offload processing.

Note: When Share Offload is disabled, the share window is rendered locally on the virtual desktop. This will increase the updates to the share session when moving the share window, but will also use more processing on the virtual desktop to display the share session video.

\VDIDWORD
EnableWMIProviderThis policy controls the use of the WMI provider for the VDI client, allowing admins to gather information about the VDI plugins.

(0) Disable the WMI provider.
(1) Enable the use of the WMI provider.

\VDI

DWORD

The VDI client also responds to MSI switches, which provides additional configuration possibilities. Learn more about mass deployment options for MSI installers.