Remote Desktop Services

From Wikipedia, the free encyclopedia
Remote Desktop Services
A component of Microsoft Windows
Details
Other names Terminal Services
Type Remote desktop software
Included with Windows Server
Service name TermService
Related components
RemoteFX, Microsoft App-V

Remote Desktop Services (RDS), known as Terminal Services in Windows Server 2008 and earlier,[1] is one of the components of Microsoft Windows that allows a user to take control of a remote computer or virtual machine over a network connection. Remote Desktop Services is Microsoft's implementation of thin client, where Windows software and the entire desktop of the computer running Remote Desktop Services, are made accessible to a remote client machine that supports Remote Desktop Protocol. With Remote Desktop Services, only software user interfaces are transferred to the client system. All input from the client system is transmitted to the server, where software execution takes place.[2] This is in contrast to application streaming systems, like Microsoft App-V, in which computer programs are streamed to the client on-demand and executed on the client machine.

RemoteFX was added to Remote Desktop Services as part of Windows Server 2008 R2 Service Pack 1.

Overview

RDS was first introduced in Windows NT 4.0 Terminal Server Edition and was known as Terminal Services at that time. Starting with Windows 2000, it became a mainstay of Windows NT family of operating systems and was constantly improved with each version of Windows.[3] The rename to Remote Desktop Services occurred in Windows Server 2008 R2.[4]

Windows includes three client components that use RDS: Windows Remote Assistance, Remote Desktop Connection (RDC) and Fast User Switching. The first two are individual apps that allow a user to take control of a remote computer over the network. In case of Remote Assistance, the remote user needs to receive an invitation and the control is cooperative. In case of RDC, however, the remote user opens a new session on the remote computer and has every power granted by its user account restrictions.[5][6][2] Fast User Switching allows users to switch between user accounts on the local computer without quitting software and logging out. Fast User Switching is part of Winlogon and uses RDS to accomplish its switching feature.[7][8] Third-party developers have created client software for other platforms, including the open source rdesktop client for common Unix platforms.

Although RDS is included with most editions of all versions of Windows NT since Windows 2000, its functionality differs in each version. Windows XP Home Edition does not accept any RDC connections at all, reserving RDS for Fast User Switching and Remote Assistance only. Other client versions of Windows only allow a maximum of one remote user to connect to the system at the cost of the user who has logged onto the console being disconnected. Windows Server allow two users to connect at the same time. This licensing scheme is called "Remote Desktop for Administration" and is meant to facilitate the administration of unattended or headless computers. Only by acquiring additional licenses (in addition to that of Windows) can a computer running Windows Server service multiple remote users at one time and achieve virtual desktop infrastructure.[7][4]

For an enterprise, RDS allows the IT department to install applications on a central server instead of multiple computers. Remote users can log on and use those applications over the network. Such centralization makes maintenance and troubleshooting easier. RDS can be used in conjunction with Windows authentication system to prevent unauthorized users from accessing the applications or data.

Microsoft has a long-standing agreement with Citrix to facilitate sharing of technologies and patent licensing between Microsoft Terminal Services and Citrix XenApp (formerly Citrix MetaFrame and Citrix Presentation Server). In this arrangement, Citrix has access to key source code for the Windows platform enabling their developers to improve the security and performance of the Terminal Services platform. In late December, 2004 the two companies announced a five-year renewal of this arrangement to cover Windows Vista.[9]

Architecture

The server component of Remote Desktop Services is Terminal Server (termdd.sys), which listens on TCP port 3389. When an RDP client connects to this port, it is tagged with a unique SessionID and associated with a freshly spawned console session (Session 0, keyboard, mouse and character mode UI only). The login subsystem (winlogon.exe) and the GDI graphics subsystem is then initiated, which handles the job of authenticating the user and presenting the GUI. These executables are loaded in a new session, rather than the console session. When creating the new session, the graphics and keyboard/mouse device drivers are replaced with RDP-specific drivers: RdpDD.sys and RdpWD.sys. The RdpDD.sys is the device driver and it captures the UI rendering calls into a format that is transmittable over RDP. RdpWD.sys acts as keyboard and mouse driver; it receives keyboard and mouse input over the TCP connection and presents them as keyboard or mouse inputs. It also allows creation of virtual channels, which allow other devices, such as disc, audio, printers, and COM ports to be redirected, i.e., the channels act as replacement for these devices. The channels connect to the client over the TCP connection; as the channels are accessed for data, the client is informed of the request, which is then transferred over the TCP connection to the application. This entire procedure is done by the terminal server and the client, with the RDP protocol mediating the correct transfer, and is entirely transparent to the applications.[10] RDP communications are encrypted using 128-bit RC4 encryption. Windows Server 2003 onwards, it can use a FIPS 140 compliant encryption schemes.[2]

Once a client initiates a connection and is informed of a successful invocation of the terminal services stack at the server, it loads up the device as well as the keyboard/mouse drivers. The UI data received over RDP is decoded and rendered as UI, whereas the keyboard and mouse inputs to the Window hosting the UI is intercepted by the drivers, and transmitted over RDP to the server. It also creates the other virtual channels and sets up the redirection. RDP communication can be encrypted; using either low, medium or high encryption. With low encryption, user input (outgoing data) is encrypted using a weak (40-bit RC4) cipher. With medium encryption, UI packets (incoming data) are encrypted using this weak cipher as well. The setting "High encryption (Non-export)" uses 128-bit RC4 encryption and "High encryption (Export)" uses 40-bit RC4 encryption.[11]

Terminal Server

Terminal Server is the server component of Terminal services. It handles the job of authenticating clients, as well as making the applications available remotely. It is also entrusted with the job of restricting the clients according to the level of access they have. The Terminal Server respects the configured software restriction policies, so as to restrict the availability of certain software to only a certain group of users. The remote session information is stored in specialized directories, called Session Directory which is stored at the server. Session directories are used to store state information about a session, and can be used to resume interrupted sessions. The terminal server also has to manage these directories. Terminal Servers can be used in a cluster as well.[2]

In Windows Server 2008, it has been significantly overhauled. While logging in, if the user logged on to the local system using a Windows Server Domain account, the credentials from the same sign-on can be used to authenticate the remote session. However, this requires Windows Server 2008 to be the terminal server OS, while the client OS is limited to Windows Server 2008, Windows Vista and Windows 7. In addition, the terminal server can provide access to only a single program, rather than the entire desktop, by means of a feature named RemoteApp. Terminal Services Web Access (TS Web Access) makes a RemoteApp session invocable from the web browser. It includes the TS Web Access Web Part control which maintains the list of RemoteApps deployed on the server and keeps the list up to date. Terminal Server can also integrate with Windows System Resource Manager to throttle resource usage of remote applications.[3]

Terminal Server is managed by the Terminal Server Manager Microsoft Management Console snap-in. It can be used to configure the sign in requirements, as well as to enforce a single instance of remote session. It can also be configured by using Group Policy or Windows Management Instrumentation. It is, however, not available in client versions of Windows OS, where the server is pre-configured to allow only one session and enforce the rights of the user account on the remote session, without any customization.[2]

Remote Desktop Gateway

The Remote Desktop Gateway service component, also known as RD Gateway, can tunnel the Remote Desktop Protocol session using a HTTPS channel.[12] This increases the security of Remote Desktop Services by encapsulating the session with Transport Layer Security (TLS)[13] This also allows the option to use Internet Explorer as the RDP client. The official MS RDP client for Mac OS X supports RD Gateway as of version 8. This is also available for iOS and Android.

This feature was introduced in the Windows Server 2008 and Windows Home Server products.

Remote Desktop Server Roles

Remote Desktop Gateway enables authorized users to connect to virtual desktops, Remote-App programs, and session-based desktops over a private network or the Internet.

Remote Desktop Connection Broker allows users to reconnect to their existing virtual desktop, RemoteApp programs, and session-based desktops. It enables even load distribution across RD Session Host servers in a session collection or across pooled virtual desktops in a pooled virtual desktop collection, and provides access to virtual desktops in a virtual desktop collection.

Remote Desktop Session Host enables a server to host RemoteApp programs as session-based desktops. Users can connect to RD Session Host servers in a session collection to run programs, save files, and use resources on those servers. Users can access Remote Desktop Session Host server by using the Remote Desktop Connection client or by using RemoteApp programs.

Remote Desktop Virtualization Host enables users to connect to virtual desktops by using RemoteApp and Desktop Connection.

Remote Desktop Web Access enables users to access RemoteApp and Desktop Connection through the Start Menu or through a web browser. RemoteApp and Desktop Connection provides users with a customized view of RemoteApp programs, session-based desktops, and virtual desktops.

Remote Desktop Licensing enables a server to manage Remote Desktop Services client access licenses (RDS CALs) that are required for each device or user to connect to a Remote Desktop Session Host server. RDS CALs are managed using the Remote Desktop Licensing Manager application.[14]

RemoteApp

RemoteApp (or TS RemoteApp) is a special mode of Remote Desktop Services, available in Windows Server 2008 R2 and later, where remote session configuration is integrated into the client operating system. The RDP 6.1 client ships with Windows XP SP3, KB952155 for Windows XP SP2 users,[15] Windows Vista SP1 and Windows Server 2008. The UI for the RemoteApp is rendered in a window over the local desktop, and is managed like any other window for local applications. The end result of this is that remote applications behave largely like local applications. The task of establishing the remote session, as well as redirecting local resources to the remote application, is transparent to the end user.[16] Multiple applications can be started in a single RemoteApp session, each with their own windows.[17]

A RemoteApp can be packaged either as a .rdp file or distributed via an .msi Windows Installer package. When packaged as an .rdp file (which contains the address of the RemoteApp server, authentication schemes to be used, and other settings), a RemoteApp can be launched by double clicking the file. It will invoke the Remote Desktop Connection client, which will connect to the server and render the UI. The RemoteApp can also be packaged in a Windows Installer database, installing which can register the RemoteApp in the Start Menu as well as create shortcuts to launch it. A RemoteApp can also be registered as handler for filetypes or URIs. Opening a file registered with RemoteApp will first invoke Remote Desktop Connection, which will connect to the terminal server and then open the file. Any application which can be accessed over Remote Desktop can be served as a RemoteApp.[16]

Windows 7 includes built-in support for RemoteApp publishing, but it has to be enabled manually in registry, since there is no RemoteApp management console in client versions of Microsoft Windows.[18]

Client software

Remote Desktop Connection

Remote Desktop Connection
A component of Microsoft Windows

Remote Desktop Connection client on Windows 8
Details
Type Remote desktop software
Included with Windows XP and later
Also available for Windows 2000, Windows 9x, Windows NT 4,[19] Mac OS X[20]
Related components
Windows Remote Assistance
Picture
Remote Desktop Connection client on Mac OS X

Remote Desktop Connection (RDC, also called Remote Desktop, formerly Microsoft Terminal Services Client, mstsc or tsclient)[21][22] is the client application for Remote Desktop Services. It allows a user to remotely log into a networked computer running the terminal services server. RDC presents the desktop interface (or application GUI) of the remote system, as if it were accessed locally.[2] In addition to regular username/password for authorizing for the remote session, RDC also supports using smart cards for authorization.[2] With RDC 6.0, the resolution of a remote session can be set independently of the settings at the remote computer.

With version 6.0, if the Desktop Experience component is plugged into the remote server, remote application user interface elements (e.g., application windows borders, Maximize, Minimize, and Close buttons etc.) will take on the same appearance of local applications. In this scenario, the remote applications will use the Aero theme if the user connects to the server from a Windows Vista machine running Aero.[3] Later versions of the protocol also support rendering the UI in full 32-bit color, as well as resource redirection for printers, COM ports, disk drives, mice and keyboards. With resource redirection, remote applications can use the resources of the local computer. Audio is also redirected, so that any sounds generated by a remote application are played back at the client system.[2][3] Moreover, a remote session can also span multiple monitors at the client system, independent of the multi-monitor settings at the server. RDC can also be used to connect to Windows Media Center remote sessions; however, since WMC does not stream video using Remote Desktop Protocol (RDP), only the applications can be viewed this way, not any media.

RDC prioritizes UI data as well as keyboard and mouse inputs, as opposed to print jobs or file transfers. so as to make the applications more responsive. It redirects plug and play devices such as cameras, portable music players, and scanners, so that input from these devices can be used by the remote applications as well.[3] RDC can also be used to connect to computers which are exposed via Windows Home Server RDP Gateway over the Internet. Finally, RDC can be used to reboot the remote computer with the CTRL-ALT-END key combination.

Windows Desktop Sharing

Windows Vista onwards, Terminal Services also includes a multi-party desktop sharing capability known as Windows Desktop Sharing. Unlike Terminal Services, which creates a new user session for every RDP connection, Windows Desktop Sharing can host the remote session in the context of the currently logged in user without creating a new session, and make the Desktop, or a subset of it, available over Remote Desktop Protocol.[23] Windows Desktop Sharing can be used to share the entire desktop, a specific region, or a particular application.[24] Windows Desktop Sharing can also be used to share multi-monitor desktops. When sharing applications individually (rather than the entire desktop), the windows are managed (whether they are minimized or maximized) independently at the server and the client side.[24]

The functionality is only provided via a public API, which can be used by any application to provide screen sharing functionality. Windows Desktop Sharing API exposes two objects: RDPSession for the sharing session and RDPViewer for the viewer. Multiple viewer objects can be instantiated for one Session object. A viewer can either be a passive viewer, who is just able to watch the application like a screencast, or an interactive viewer, who is able to interact in real time with the remote application.[23] The RDPSession object contains all the shared applications, represented as Application objects, each with Window objects representing their on-screen windows. Per-application filters capture the application Windows and package them as Window objects.[25] A viewer must authenticate itself before it can connect to a sharing session. This is done by generating an Invitation using the RDPSession. It contains an authentication ticket and password. The object is serialized and sent to the viewers, who need to present the Invitation when connecting.[23][25]

Windows Desktop Sharing API is used by Windows Meeting Space for providing application sharing functionality among peers; however, the application does not expose all the features supported by the API.[24] It is also used by Remote Assistance.

See also

References

  1. ↑ "Windows Remote Desktop Services spotlight". Retrieved 2010-11-18. 
  2. ↑ 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 "Technical Overview of Terminal Services in Windows Server 2003". Retrieved 2007-07-23. 
  3. ↑ 3.0 3.1 3.2 3.3 3.4 "Whats new in Terminal Services in Windows Server 2008". Retrieved 2007-07-23. 
  4. ↑ 4.0 4.1 Russel, Charlie; Zacker, Craig (2009). "4: Remote Desktop Services and VDI: Centralizing Desktop and Application Management". Introducing Windows Server 2008 R2. Redmond, WA: Microsoft Press. Retrieved 11 January 2014. 
  5. ↑ "How to change the listening port for Remote Desktop". Retrieved 2010-11-18. 
  6. ↑ "Frequently Asked Questions about Remote Desktop". Retrieved 2007-07-23. 
  7. ↑ 7.0 7.1 Russinovich, Mark; Solomon, David A.; Ionescu, Alex. Windows Internals (6th ed.). Redmond, WA: Microsoft Press. pp. 20–21. ISBN 978-0-7356-4873-9. 
  8. ↑ "Architecture of Fast User Switching". Support. Microsoft. 15 January 2006. Retrieved 11 January 2014. 
  9. ↑ "Citrix and Microsoft Sign Technology Collaboration and Licensing Agreement". 
  10. ↑ "How Terminal Services Works". Microsoft. 2003-03-28. Retrieved 2007-07-23. 
  11. ↑ Microsoft Knowledge Base, 2006-11-01, Connection Configuration in Terminal Server, http://support.microsoft.com/kb/186566/en-us
  12. ↑ "Terminal Services Gateway (TS Gateway)". Microsoft TechNet. Retrieved 2009-09-10. 
  13. ↑ "Remote Desktop Protocol". Microsoft Developer Network (MSDN). Retrieved 2009-09-10. 
  14. ↑ TechNet: Remote Desktop Licensing
  15. ↑ "Description of the Remote Desktop Connection 6.1 client update for Terminal Services in Windows XP Service Pack 2". Retrieved 2010-11-18. 
  16. ↑ 16.0 16.1 "Terminal Services RemoteApp (TS RemoteApp)". Retrieved 2007-07-23. 
  17. ↑ "Terminal Services RemoteApp Session Termination Logic". Retrieved 2007-10-02. 
  18. ↑ "How to enable RemoteApp (via RDP 7.0) within VirtualBox or VMWare running Windows 7, Vista SP1+ or Windows XP SP3". Retrieved 2010-11-18. 
  19. ↑ "Windows XP Remote Desktop Connection software (system requirements)". Retrieved 2010-07-10. 
  20. ↑ "Description of the Microsoft Remote Desktop Connection Client for Mac 2.0.1". Retrieved 2010-11-18. 
  21. ↑ "Why doesn't the New Folder command work in the root of a redirected drive resource in a Remote Desktop session?". The Old New Thing. Microsoft. 17 December 2013. Retrieved 18 December 2013. 
  22. ↑ Savill, John (1 October 2008). The Complete Guide to Windows Server 2008. Pearson Education. p. 1752. ISBN 978-0-13-279758-0. Retrieved 1 June 2012. "Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 all contain the RDC tool, mstsc.exe [...] MSTSC in the filename mstsc.exe stands for Microsoft Terminal Services Client." 
  23. ↑ 23.0 23.1 23.2 "Windows Desktop Sharing". Retrieved 2007-10-11. 
  24. ↑ 24.0 24.1 24.2 "Windows Desktop Sharing API". Retrieved 2007-10-11. 
  25. ↑ 25.0 25.1 "About Windows Desktop Sharing". Retrieved 2007-10-11. 

External links

Management tools
Applications
Shell
Services
File systems
Server
Architecture
Security
Compatibility
API
Discontinued
Computer games
Others
General
Implementations
This article is issued from Wikipedia. The text is available under the Creative Commons Attribution/Share Alike; additional terms may apply for the media files.