Share via


RDP OS Design Development

Other versions of this page are also available for the following:

Windows Mobile Not SupportedWindows Embedded CE Supported

8/28/2008

With support for Remote Desktop Protocol (RDP) in Windows Embedded CE, a user of a Windows Embedded CE powered device can connect remotely to a desktop computer that is running Windows XP Professional, or to a server that is running Windows NT Server 4.0, Terminal Server Edition or in later versions.

With RDP, the Windows desktop UI on a server can be remoted to a Windows Embedded CE powered device, such as a thin client, so that it seems that Windows-based applications run on the target device. The applications are actually running on the remote server.

OS Design Information

The following table shows operating system (OS) requirements for RDP.

Concepts Description

Dependencies

A Terminal Server that is running RDP version 4.0 or in later versions of RDP

Hardware considerations

A serial or Ethernet connection for network communication between the Windows Embedded CE client and the server

Note

Although not required, you should include a keyboard driver whenever possible, even if the device has a software-based input panel. If a device does not have a PS2 port, use the NOP keyboard driver (BSP_KEYBD_NOP=1).

Modules and Components

The following table shows the modules and components that implement RDP.

Item Module Component

Microsoft Terminal Services Client ActiveX Control

mstscax

None

Additionally, there are supporting modules that are used in RDP devices, such as a thin client. In this kind of device, the thin client shell hosts the mstscax control.

Note

In Windows Embedded CE 6.0, during the process, the mstscax module is built as tscaxctrl.dll, and then it is renamed to mstscax.dll during the makeimg phase. If you try to build this module manually, you should be familiar with the naming conventions at the different stages of the build process.

For more information about mstscax and supporting modules, see rdp Modules.

RDP Implementation Considerations

The following Sysgen variables implement the specified RDP functionality.

Sysgen variable Functionality

SYSGEN_RDP

Adds base RDP functionality, including the CETSC executable, the MSTSCAX ActiveX dynamic-link library (DLL), 32-bit color, Secure Sockets Layer/Transport Layer Security (SSL/TLS), Server Authentication, and Network Level Authentication (NLA).

SYSGEN_RDP_AUDIO

Enables audio redirection from the server to the RDP client.

> [!NOTE] > SYSGEN_RDP_AUDIO does not automatically bring in the ACM WMA or MP3 audio codecs. For this, you must add SYSGEN_DSHOW_ACMMP and SYSGEN_DSHOW_ACMWMA.

SYSGEN_RDP_PRINTER

Enables printer redirection from the server to the RDP client.

SYSGEN_RDP_SMARTCARD

Enables smart card redirection for terminal server logon and application usage. OS developers must add the smart card driver appropriate for their system together with a custom CSP provided by the third-party Smart Card reader provider.

SYSGEN_RDP_PORT

Enables serial and parallel port redirection.

SYSGEN_RDP_CLIPBOARD

Enables cut, copy, and paste clipboard redirection.

SYSGEN_RDP_UI

Enables user interface dialog boxes.

SYSGEN_RDP_DRIVE

Enables file storage redirection.

SYSGEN_RDP_FILTERFSD

Enables filtered file storage redirection.

SYSGEN_RDP_LICINFO

Adds the RDP Client Activation License utility.

In This Section

  • TS CAL Maintenance Tool
    Describes the Terminal Services client access license (TS CAL) maintenance tool, a tool that displays TS CAL tokens for devices that connect to a server that runs Terminal Services.

See Also

Reference

RDP Reference

Concepts

RDP Application Development
RDP Security
RDP Best Practices
RDP Samples

Other Resources

Windows Thin Client Design Template
rdp Modules