Using Remote Desktop Services
The following sections describe how to program in the Remote Desktop Services environment and how to extend Remote Desktop Services (formerly known as Terminal Services) technology to the web by using Remote Desktop Web Connection. If you are looking for user information for Remote Desktop connections, See Connect to another computer using Remote Desktop Connection.
Note
This topic is for software developers.
In this section
-
Detecting Whether the Remote Desktop Services Role Is Installed
-
C# code example that shows a method that returns True if the Remote Desktop Services server role is installed and running or false otherwise, beginning with Windows Server 2008.
-
You can extend TS Session Broker by using the IWTSSBPlugin COM interface.
-
Beginning with Windows Server 2008 R2, you can implement a custom remote audio endpoint enumerator as part of a Remote Desktop protocol provider.
-
Distributed COM (DCOM) enables object activation on a per-session basis by using a system-supplied session moniker.
-
Using the ADSI Extension for Remote Desktop Services User Configuration
-
Administration of Remote Desktop Services-specific user properties is possible by using the methods implemented by the Active Directory Service Interfaces (ADSI) extension, which is packaged with the dynamic-link library Tsuserex.dll.
-
Describes how you can use the Remote Desktop Services API to enable applications to perform tasks in a Remote Desktop Services environment.
-
Developers can use this API to customize the logic that Remote Desktop Connection Broker (RD Connection Broker) uses to determine the best destination for an incoming client connection.
-
Developers can create custom web services that manage virtual desktop infrastructure (VDI) solutions.
For more information, see Remote Desktop Services Programming Guidelines.
Related topics