Remote-Control Persistent Virtual Channels
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
On Windows CE .NET 4.2 and in later versions of Windows Embedded CE and Windows XP, a DLL can specify one or more virtual channels as remote-control persistent.
Overview
With remote-control persistent virtual channels, computer-support staff can view and control a Terminal Services session. Sharing input and display graphics between two Terminal Services sessions gives a support person the ability to diagnose and resolve problems remotely. When a Terminal Services session is shared, that is, when a user remotely monitors the on-screen operation of another user on a server, a virtual channel with the persistent flag set will not be disconnected from that server. Data continues to be sent and received through this channel.
Virtual channels that are not specified as remote-control persistent will close when a remote-control session connects to or disconnects from the current session.
Create a Remote-Control Virtual Channel
Remote-control persistent virtual channels are specified during the call to VirtualChannelInit.
You can also set a remote-control persistent option on a virtual channel by using the Remote Desktop ActiveX client control interface. For more information, see IMsRdpClient::SetVirtualChannelOptions.