Remote Desktop Services
Purpose
Windows Server 8 Beta, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, or Windows 2000 Server with Remote Desktop Services (formerly known as Terminal Services) allow a server to host multiple, simultaneous client sessions. Remote Desktop uses Remote Desktop Services technology to allow a single session to run remotely. A user can connect to a Remote Desktop Session Host (RD Session Host) server (formerly known as a terminal server) by using Remote Desktop Connection (RDC) client software. The Remote Desktop Web Connection extends Remote Desktop Services technology to the web.
Where applicable
A Remote Desktop Connection (RDC) client can exist in a variety of forms. Thin-client hardware devices that run an embedded Windows-based operating system can run the RDC client software to connect to an RD Session Host server. Windows-, Macintosh-, or UNIX-based computers can run RDC client software to connect to an RD Session Host server to display Windows-based applications. This combination of RDC clients provides access to Windows-based applications from virtually any operating system.
Developer audience
Developers who use Remote Desktop Services should be familiar with the C and C++ programming languages and the Windows-based programming environment. Familiarity with client/server architecture is required. The Remote Desktop Web Connection includes scriptable interfaces to create and deploy scriptable virtual channels within Remote Desktop Services web applications.
Run-time requirements
Applications that use Remote Desktop Services require Windows Server 8 Beta, Windows 8 Consumer Preview, Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, or Windows 2000. To use Remote Desktop Web Connection functionality, the Remote Desktop Services client application requires Internet Explorer and a connection to the World Wide Web. For information about run-time requirements for a particular programming element, see the Requirements section of the reference page for that element.
In this section
| Topic | Description |
|---|---|
|
Remote Desktop Services (formerly known as Terminal Services) provides functionality similar to a terminal-based, centralized host, or mainframe, environment in which multiple terminals connect to a host computer. | |
|
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. | |
|
Documentation of property methods that you can use to examine and configure Remote Desktop Services user properties. Remote Desktop Services functions, structures, and Remote Desktop Web Connection scriptable interfaces are also documented. | |
|
The Remote Desktop Services WMI provider provides programmatic access to the information and settings that are exposed by the Remote Desktop Services Configuration/Connections Microsoft Management Console (MMC) snap-in. | |
|
Describes how to use the Remote Desktop ActiveX control. | |
|
A new version of the Remote Desktop ActiveX control is available for use with Windows 8 and Windows Server 8 Beta. These topics document the usage of this control. | |
|
Virtual channels are software extensions that can be used to add functional enhancements to a Remote Desktop Services application. | |
|
The RemoteFX Media Redirection API is used in a Remote Desktop session to identify areas of the server that are displaying fast changing content, such as video. This content can then be video encoded and sent to the client in encoded format. | |
|
Describes how to use the Remote Desktop Connection Broker client API. | |
|
A list of the Remote Desktop Services shortcut keys. |
Related topics
Send comments about this topic to Microsoft
Build date: 3/7/2012
