Thoughts from the EPS Windows Server Performance Team
Day Nineteen. There are only eight more days to go till the big day. The excitement is definitely building. Today's topic for discussion - Remote Desktop Connection Architecture.
The Remote Desktop Connection 6.1 client is comprised of the following four functional layers containing individual objects that interact through a common set of core components. The function layers that make up RDC Architecture are:
The following diagram illustrates the relationship between the components of the RDC client application - we will go over each of them briefly:
The shell layer uses the interfaces exposed by the ActiveX layer to provide the Remote Desktop Connection Client (MSTSC.EXE), a web based shell (TSWeb), the Remote Desktops MMC snap-in (TSMMC.MSC) and Remote Assistance (MSRA.EXE).
The ActiveX layer provides secure interfaces to enable the different types of shells in the Shell layer. The ActiveX control that is used for Remote Desktop Web Access is now included with the Remote Desktop Connection application. In order for the Terminal Services ActiveX control to run properly, you must ensure that the ActiveX control is enabled in Internet Explorer. The Terminal Services ActiveX Client control is implemented in mstscax.dll in the RDC 6.x client using the following Class ID: 4eb89ff4-7f78-4a0f-8b8d-2bf02e94e4b2.
The Core layer is the main "engine" for the RDC client. It provides all of the protocol-related functionality and has the following functional layers:
The Transport Layer provides the connection functionality for the client. A TCP-based transport and an RPC / HTTPS (proxy) based transport are provided in the RDC 6.x application.
And that brings us to the end of this post. Tomorrow is Day Twenty, and we'll take a look at some RDC Enhancements. Until next time ...
- CC Hameed
PingBack from http://www.msitproblog.com/2008/02/25/the-performance-team-countdown/
When is the release of the RDC 6.1 standalone?