Skip to main content

Overview

The Wacom Virtual Channel Component allows a signature device connected to a client machine to be used by an application running in a remote Citrix or Windows RDP session. It transmits signature device data between the client and the remote machine over a dedicated virtual channel, so a remote application can capture and display signatures as though the device were connected locally.

Supported environments​

The component is currently supported in the following virtual environments:

  • Citrix
    • Citrix Virtual Desktop & App 2203
    • Citrix Virtual Desktop & App 2402
  • Windows RDP
    • Windows 11
    • Windows 10
    • Windows Server 2019
    • Windows Server 2022

OS support​

MachineSupported OS
ClientWindows 10 or later
Remote machineWindows Server 2019, Windows Server 2022

Installation​

Setting up component requires installing components on both the client and the remote machine:

  • Client-side - the Wacom Remote Component.
  • Remote machine-side - the Wacom Ink SDK for signature for Windows 4.10 (or later).

For Citrix environments, the Wacom Virtual Channel Component must also be allowed through the user's Citrix policy; see Configuring Citrix for the two supported approaches.

Troubleshooting and debugging​

If issues are encountered, enable debugging on the client by setting the following registry key.

For 64-bit systems:

[HKEY_CURRENT_USER\Software\Wacom\SignatureCaptureDVC]
"Logging"=dword:ffffffff
"ServerConsole"=dword:00000001

For 32-bit systems:

[HKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Wacom]
"Logging"=dword:ffffffff
"ServerConsole"=dword:00000001

Once the registry key is set, run the application. A window opens showing the relevant logging information.

note

For general (non-virtual channel) SDK logging, see Troubleshooting and debugging in the SignatureCapture interface guide.

If further assistance is needed:

  • Copy and save the contents of the log file.
  • Describe in detail the steps taken to reach the issue and how to reproduce it.
  • Send this information, with the log file attached, in a support ticket on the Developer Support site.