On the local client, the VDX Plugin is initiated automatically every time a remote session starts. By hovering over the VDX Plugin taskbar icon, the following information can be viewed:

  • The server or virtual machine where the session started
  • The session number
  • The version number of the VDX Plugin

Similarly, on the remote desktop, when a remote session starts, right-click the VDX Engine taskbar icon to view the status of VDX. This status overview shows:

  • The VDX Engine version running on the machine that hosts the remote desktop
  • The VDX Plugin version running on the local client
  • The VDX Mode
  • Whether VDX is licensed
  • Whether VDX is integrated with Ivanti Workspace Control

Clicking on the VDX Engine taskbar icon opens the Client Start Menu. This window shows items from the local start menu, the local desktop and the local notification area of the client. The window remains open until an item is opened. A Search option is included to search for items included in the Client Start Menu.

Universal Windows Platform (UWP) Apps are not added to the Client Start Menu.

Tackling VDX connectivity problems

If the VDX Plugin taskbar icon does not appear at all on the local client, the VDX Plugin might not be registered correctly. In this case, re-install the VDX Plugin MSI by using the Repair option. If this does not solve the issue, please check the following:

Changing the Start Menu Behavior on Windows Server 2019

When VDX is used on machines running Microsoft Windows Server 2019 or Windows 10 build 1809 or higher, the following intended behavior can be observed:

  • When the Windows Start Menu is opened, the window managing mode is disabled, which results in VDX extended applications to disappear from the session.

  • At the beginning of the session, the Windows Start Menu is opened and closed. This occurs only once.

The behavior previously described was introduced to resolve the following issues:

Create the following registry key on the machine where the VDX Engine is installed to disable the opening and closing of the Windows Start Menu at the beginning of the session:








0 or 1

Setting the DisableMenuTrigger registry key to 1 reintroduces the two previously mentioned issues.