About Remote Desktop Services

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. Each terminal provides a conduit for input and output between a user and the host computer. A user can log on at a terminal, and then run applications on the host computer, accessing files, databases, network resources, and so on. Each terminal session is independent, with the host operating system managing conflicts between multiple users contending for shared resources.

The primary difference between Remote Desktop Services and the traditional mainframe environment is that the dumb terminals in a mainframe environment only provide character-based input and output. A Remote Desktop Connection (RDC) client or emulator provides a complete graphical user interface including a Windows operating system desktop and support for a variety of input devices, such as a keyboard and mouse.

In the Remote Desktop Services environment, an application runs entirely on the Remote Desktop Session Host (RD Session Host) server (formerly known as a terminal server). The RDC client performs no local processing of application software. The server transmits the graphical user interface to the client. The client transmits the user's input back to the server.

For more information, see the following topics.

In this section

TopicDescription

What's New in Remote Desktop Services

Topics that describe the changes in each release of the Remote Desktop Services API.

Resources on a Remote Desktop Session Host Server

Multiple users can log on simultaneously to a single RD Session Host server, sharing the hardware and software resources of the server.

Modify Device Redirection Default

Because Remote Desktop Gateway servers attempt to enforce secure device redirection policies before passing the client connection through to a Remote Desktop Session Host server, you may need to disable this default in some cases.

Remote Desktop Sessions

Because each logon to a Remote Desktop Connection (RDC) client receives a separate session ID, the user-experience is similar to being logged on to multiple computers at the same time; for example, an office computer and a home computer.

Remote Desktop Protocol

The Microsoft Remote Desktop Protocol (RDP) provides remote display and input capabilities over network connections for Windows-based applications running on a server.

Remote Desktop Services API

The Remote Desktop Services API is primarily useful to client/server applications and applications for Remote Desktop Services administration.

Remote Desktop Services programming guidelines

Topics that provide guidelines for developing applications in a Remote Desktop Services environment.

Remote Desktop Web Connection

Describes how to install a Remote Desktop Web Connection.

Remote Desktop Services management applications

Describes the management applications that Remote Desktop Services supports.

 

 

 

Show:
© 2014 Microsoft