Implementing Virtual Channels (Windows CE 5.0)
RDP versions 5.1 and later support virtual channels. Virtual channels are custom data formats handled independently of the RDP protocol. They let you add new technologies without having to modify the RDP protocol.
The following are the most-likely users of virtual-channel services. Others 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.
- Audio devices.
A virtual-channel application requires the following user-written components:
Server-side component
A user-mode application that 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 launch the application manually.
Client-side component
A dynamic-link library (DLL) that must be loaded into memory on the client computer when the Remote Desktop client program runs.
The following topics describe these components:
- Virtual Channel Server Application
- Virtual Channel Client
- Virtual Channel Client Registration
- Remote-Control Persistent Virtual Channels
If you have enabled a virtual channels application in your Terminal Services deployment, the application can also be made available to client computers by means of the Remote Desktop ActiveX Control Interface.
See Also
Send Feedback on this topic to the authors