Remote Desktop Services (formerly known as Terminal Services) in Windows Server environments, such as Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, and Windows Server 2008, empower a server to concurrently host multiple client sessions. This technology, often referred to as terminal services, allows users to access a single session remotely. By utilizing Remote Desktop Services technology, a user can connect to a Remote Desktop Session Host (RD Session Host) server, previously known as a terminal server, using Remote Desktop Connection (RDC) client software. Furthermore, the Remote Desktop Web Connection extends the reach of terminal services technology to the web, enabling browser-based access.
It’s important to note that while this information is geared towards software developers seeking to understand and utilize terminal services, users looking for guidance on Remote Desktop connections can find helpful resources in the Remote Desktop Connection: frequently asked questions.
Broad Applicability of Terminal Services
The versatility of a Remote Desktop Connection (RDC) client is significant within terminal services environments. These clients can take various forms, accommodating diverse hardware and software needs. Thin-client hardware devices, often running embedded Windows-based operating systems, are capable of running RDC client software to establish connections with an RD Session Host server. This allows them to participate fully in a terminal services setup. Moreover, computers running Windows, macOS, or UNIX-based operating systems can also utilize RDC client software to connect to an RD Session Host server. This cross-platform compatibility ensures that users can access Windows-based applications from virtually any operating system through terminal services. This broad compatibility is a cornerstone of the flexibility offered by terminal services.
Target Audience: Developers Utilizing Terminal Services
The primary audience for in-depth information about Remote Desktop Services, or terminal services, is developers. Those working with terminal services should possess a strong foundation in C and C++ programming languages, alongside a solid understanding of the Windows-based programming environment. Furthermore, familiarity with client/server architecture is essential for effectively developing and deploying applications within a terminal services framework. The Remote Desktop Web Connection component of terminal services also includes scriptable interfaces. These interfaces are designed to enable developers to create and deploy customized, scriptable virtual channels within web applications that leverage Remote Desktop Services, expanding the capabilities of terminal services in web-based scenarios.
Run-time Requirements for Terminal Services Applications
Applications designed to utilize Remote Desktop Services, or terminal services, have specific run-time requirements. They necessitate operating systems such as Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008 R2, Windows 7, Windows Server 2008, or Windows Vista. To leverage the Remote Desktop Web Connection functionality within terminal services, the client application requires Internet Explorer and a stable connection to the World Wide Web. For detailed information regarding the run-time requirements of specific programming elements within terminal services, developers should consult the “Requirements” section available on the reference page for each element. This ensures compatibility and proper functioning within a terminal services environment.
Key Components and APIs within Terminal Services
Remote Desktop Services, building upon the foundation of terminal services, encompasses a range of components and APIs that developers can utilize:
Remote Desktop ActiveX control
The Remote Desktop ActiveX control is a crucial component, and detailed documentation exists on how to effectively use the Remote Desktop ActiveX control within terminal services applications.
Remote Desktop Protocol Provider API
For developers seeking to create custom communication protocols, the Remote Desktop Protocol Provider API is essential. It enables the development of protocols that facilitate communication between the Remote Desktop Services service and numerous clients in a terminal services environment.
Remote Desktop Services virtual channels
Virtual channels are software extensions that significantly enhance the functionality of terminal services applications. Learn more about utilizing Remote Desktop Services virtual channels to add custom features.
RemoteFX Media Redirection API
Optimizing media delivery in terminal services sessions is possible with the RemoteFX Media Redirection API. This API is designed to identify areas displaying rapidly changing content, like video, within a Remote Desktop session. This allows for efficient video encoding and transmission to the client in an encoded format, improving performance in terminal services environments.
Remote Desktop Connection Broker client API
For managing connections and sessions, the Remote Desktop Connection Broker client API is a valuable tool. Documentation is available on how to effectively utilize this API within terminal services deployments.
Personal desktop task agent API reference
Managing scheduled updates in personal virtual desktop environments within terminal services is facilitated by the personal desktop task agent API. Reference documentation is available for developers working with this API.
About Remote Desktop Services
For a foundational understanding of terminal services and its evolution into Remote Desktop Services, the About Remote Desktop Services section provides valuable insights. It explains how Remote Desktop Services, inheriting from terminal services, offers functionality akin to traditional terminal-based systems, enabling multiple terminals to connect to a central host.
Remote Desktop Management Services Provider
In virtual desktop infrastructure (VDI) environments, the Remote Desktop Management Services (RDMS) Provider plays a critical role. It is responsible for managing and orchestrating VDI deployments within terminal services.
Remote Desktop Services reference
Comprehensive Remote Desktop Services reference documentation is available, detailing property methods for examining and configuring user properties within terminal services. It also covers functions, structures, and Remote Desktop Web Connection scriptable interfaces relevant to terminal services development.
Remote Desktop Services Shortcut Keys
For users and administrators working with terminal services, a handy list of Remote Desktop Services shortcut keys is provided to enhance efficiency and navigation.
Remote Desktop Services WMI provider
Programmatic access to information and settings within terminal services is facilitated by the Remote Desktop Services WMI provider. This provider exposes data managed by the Remote Desktop Services Configuration/Connections Microsoft Management Console (MMC) snap-in, allowing for automated management and configuration of terminal services.
Using Remote Desktop Services
Practical guidance on development within the terminal services environment and extending terminal services technology to the web using Remote Desktop Web Connection can be found in the Using Remote Desktop Services section.
Related Information
For historical context and understanding the evolution of terminal services, the article Terminal Services Is Now Remote Desktop Services provides valuable background information. It clarifies the renaming and continued development of terminal services into the modern Remote Desktop Services platform.
