Thin Client Software Architecture (Windows Embedded CE 6.0)

1/5/2010

This topic describes the Remote Desktop Protocol (RDP) ActiveX control architecture, provides a thin client software architecture diagram, and describes the software architecture components in the diagram.

ActiveX Control

The RDP client operates as an ActiveX control. Therefore, the RDP client can be hosted in a Web browser or in a custom Component Object Model (COM) container that you create. For example, you can use CETSC.EXE as the container, or you can modify CETSC to create a custom container.

The following architectural illustration shows the RDP architecture when the RDP client is operating as an ActiveX control.

For a description of the components in this illustration, see the following sections, Thin Client Software Architecture and Thin Client Hardware Architecture in this topic.

Thin Client Software Architecture

The following list shows the architecture components in the software layer of a Windows Embedded CE powered thin client.

Architecture component	Description
Shell	The Shell provides the basic framework for the user interface on an operating system (OS) design. The shell works to present a consistent interface throughout the computing experience and can be used to locate files and folders. A thin client can use either the Windows Thin Client Shell. This includes the Thin Client Startup Wizard, or the Standard Shell. For more information, see Thin Client Shell.
Setup wizard	The Setup wizard is used only in the Windows Thin Client Shell and, if the thin client is configured to run without a default connection, the wizard runs the first time that a thin client is turned on. For more information, see Changing the Shell Startup Behavior in Thin Client.
Internet Explorer sample	Internet Explorer sample is the sample browser application. For more information, see The IESample Browser.
Third-party container	A third-party container is a custom COM container that either you or a third party creates.
CETSC executable	Windows Embedded CE Terminal Services Client (CETSC) derives from Microsoft Terminal Services Client (MSTSC). CETSC enables a thin client to access Windows-based applications on a server that is running Terminal Services. The CETSC shell is a sample shell that provides a user interface (UI) for creating connections and changing settings. When the CETSC shell is used, user preferences are saved in either an .rdp file or the registry. For more information, see Windows Embedded CE Terminal Services Client (CETSC).
MSTSCAX	MSTSCAX is a Microsoft ActiveX control that runs in Windows operating systems and handles all communications between the RDP client on the thin client and the RDP component on the server.
ActiveX interface layer	The ActiveX interface layer lets you host RDP in a browser window or in your own COM container. If you have included a virtual-channels application in your Terminal Services deployment, this application can also be made available to client computers by using the Remote Desktop ActiveX Control (MSTSCAX) interfaces. For more information, see Virtual Channel Client and Remote Desktop ActiveX Control Interfaces.
UI layer	The UI layer is the UI for the RDP client core and window management software.
Scriptable virtual channels	Virtual channels can be invoked by Internet Explorer Visual Basic Script or by C/C++ code. For more information, see Virtual Channels Implementation and RDP Functions.
RDP core	This includes the core technologies that are required to support the RDP protocol.
File storage redirection and filtered storage redirection	File storage redirection lets you view and manage folders on your thin client in a remote session. If file storage redirection is enabled, you can use the filtered file storage redirection to specify the directories that are available within the RDP session. File storage redirection works by using an internal virtual channel.
Virtual channels	Client computers and servers that are running Terminal Services can communicate with one another through virtual channels. Virtual channels are custom data formats handled independently of the RDP protocol. They let you add new technologies without having to modify the RDP protocol. For more information, see Virtual Channels Implementation. If you have enabled a virtual channels server-side application in your Terminal Services deployment, the application can also be made available to client computers through the Remote Desktop ActiveX Control Interfaces.

For specific software requirements, see Thin Client Software Requirements.

Thin Client Hardware Architecture

The following list shows the architectural components in the hardware layer of a Windows Embedded CE powered thin client.

Architecture component	Description
RAM, ROM, and nonvolatile memory	RAM, ROM, and nonvolatile memory support the thin client software and provide the space in which to run applications. How much of each type of memory that is required depends on the Catalog items included in the Windows thin client OS design, the software installed, and the number of defined thin client connections. Where multiple RDP sessions are required, RAM becomes important to the operation of a thin client.
I/O devices	I/O devices include a display device, a keyboard, and a pointing device, such as a mouse or a touch screen, audio output hardware (optional), and network connectivity.

For specific hardware requirements and recommendations, see Performance Considerations for the Hardware Components of a Thin Client.

See Also

Concepts

Thin Client Architecture
Thin Client System Architecture