Using Remote Desktop Services virtual channels

To implement a virtual channel, you provide the server and client modules of a virtual channel's application. The server module can be a user-mode application or a kernel-mode driver. The client module must be a DLL.

For descriptions of these modules, see the following topics.

In this section

Virtual Channel Server Application

The server module of an application that uses virtual channels must be a user-mode application running in a client session on the Remote Desktop Session Host (RD Session Host) server. Note that you must provide a method to start the server application.

Virtual Channel Client DLL

The client of a virtual channels application is a DLL that is loaded during the Remote Desktop Services initialization on the client computer. The DLL must be registered on the client computer.

Virtual Channel Client Registration

You must store the name of the client DLL in the registry.

Remote Control Persistent Virtual Channels

A remote control persistent virtual channel is not closed when a remote control connects or disconnects for the session connected to the client. Data will continue to be transmitted and received through this channel.

Dynamic Virtual Channels

Dynamic virtual channel (DVC) APIs extend the existing virtual channel APIs for Remote Desktop Services, known as static virtual channel (SVC) APIs.

If you have enabled a virtual channel's application in your Remote Desktop Services deployment, you can also make the application available to client computers that access the RD Session Host server by means of the Remote Desktop ActiveX control. For more information, see Using the Remote Desktop ActiveX Control with Virtual Channels.

 

 

Show: