Virtual Channels Implementation (Windows Embedded CE 6.0)
1/6/2010
Remote Desktop Protocol (RDP) version 5.1 and later versions of RDP support virtual channels. Virtual channels are custom data formats handled independently of the RDP protocol. Virtual channels enable you to add new technologies without having to modify the RDP protocol.
Virtual Channel Components
The following list shows the most likely users of virtual channel services. Other users are possible. There is no intentional limitation on what the virtual channels mechanism can handle:
- General kernel-mode drivers, such as serial or printer drivers
- File-system redirection
- User-mode applications, such as remote cut-and-paste operations
- Audio devices
A virtual channel application requires the following user-written components:
- Server-side component: This user-mode application runs in a client session on the Terminal Server. You must provide a method to start this application. There are several ways to do this, such as a logon script, a program or script in the Startup folder, or having the user start the application manually.
- Client-side component: This is a dynamic-link library (DLL) that must be loaded into memory on the client computer when the Remote Desktop client program runs.
In This Section
| Topic | Description |
|---|---|
Describes the server component of an application that uses virtual channels. |
|
Provides information on registering the server application. |
|
Describes the client part of a virtual channel application DLL. Describes the functions that the client DLL must implement and call in order to work with virtual channels. |
|
Provides information on registering the client DLL. |
|
Describes remote-control persistent virtual channels. |
If you have enabled a virtual channel application in your Terminal Services deployment, the application can also be available to client computers through the Remote Desktop ActiveX Control Interfaces.