Windows CE 5.0 Migration Issues for RDP
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
Windows CE 5.0 uses RDP 5.2 rather than RDP 5.1, as used in Windows CE .NET 4.2. For migration information specific to RDP 5.2, see RDP 5.2 Migration Issues.
In Windows CE 5.0, RDP has two modes of operation. By default, RDP runs in Graphics, Windowing, and Events Subsystem (GWES) rather than in its own process space. RDP runs in GWES as a Windows control, and the interface to it is through standard window messages. This means if RDP is configured to run in GWES, it cannot be run inside a Web browser. Optionally, you can configure RDP to run in Microsoft ActiveX Control. Note that in Windows Embedded CE 6.0 R2, RDP has only one mode of operation; ActiveX control mode. For more information, see Thin Client Software Architecture.
In Windows CE 5.0, RDP uses audio codecs found in %_WINCEROOT%\public\directx\oak\lib\<platform>\retail.
Windows CE 5.0 includes filtered file storage redirection (SYSGEN_RDP_FILTERFSD). When local drive redirection is enabled for a session, which allows you to view and manage folders on your local drives in a remote session, you can use filtered file storage redirection to specify the directories that are shared. For more information, see Filtered File Storage Redirection.
The BBarShowPinBtn registry setting was added to prevent spoofing of the client UI at public kiosks. By default, BBarShowPinBtn is set to zero (0); therefore, the pin button is not displayed, the connection bar remains on top, and all server output appears below the connection bar. This behavior differs in Windows CE 5.0 from earlier versions in which the pin button was displayed by default. An OS designer can change the default value to allow the user to unpin the connection bar from the UI.
The following table shows the new names for RDP file keywords.
| Previous keyword | Windows CE 5.0 keyword |
|---|---|
Alternate Shell |
AlternateShell |
AudioMode |
AudioRedirectionMode |
AutoLogon |
None |
Autoreconnection Enabled |
AutoreconnectEnabled |
BitmapCachePersistEnable |
BitmapPersistenceEnabled |
BitmapPersistCache16Size |
None. Use BitmapCacheSize. |
BitmapPersistCache24Size |
None. Use BitmapCacheSize. |
BitmapPersistCacheSize |
None. Use BitmapCacheSize. |
BitmapPersistence |
BitmapPersistCacheLocation |
Compression |
Compress |
Connect to console |
ConnectToServerConsole |
Disable CTRL+ALT+DEL |
None |
Disable Cursor setting |
None |
DisplayConnectionBar |
BBarEnabled |
None |
BBarShowPinBtn |
Full Address |
ServerName |
FullScreen |
StartFullScreen |
KeyboardHook |
KeyboardHookMode |
MRU0 |
None |
None |
BBarPinned |
None |
BBarShowMinimizeBtn |
None |
BBarShowRestoreBtn |
Password 51 |
Password |
PluginLists |
None |
RedirectCOMPorts |
EnablePortRedirection |
RedirectDrives |
EnableDriveRedirection |
RedirectPrinters |
EnablePrinterRedirection |
RedirectSmartCards |
EnableSCardRedirection |
Screen Mode ID |
None. Use StartFullScreen. |
Server Port |
MCSPort |
Session Bpp |
ColorDepthID |
Shell Working Directory |
WorkingDir |
Windows CE .NET 4.2 Migration
In Windows CE .NET 4.2, which uses RDP 5.1, the Remote Desktop client user interface (UI) changed from Microsoft Terminal Services Client (MSTSC) to Windows Embedded CE Terminal Services Client (CETSC) which derives from MSTSC. CETSC is software that enables a thin client that is not using the Windows Thin Client Shell to access Windows-based applications on the Terminal Server. CETSC is included in SYSGEN_RDP. The source code for the UI is now public and can be modified if needed. For more information, see Windows Embedded CE Terminal Services Client (CETSC).
Windows CE .NET 4.0 Migration
In Windows CE .NET 4.0 and later, certain parts of Remote Desktop Protocol functionality were separated from the main RDP Catalog item. In versions earlier than Windows CE .NET 4.0, RDP functionality was represented by a single Sysgen variable, SYSGEN_RDP.
To retain prior functionality, ensure that the following Sysgen variables are set in addition to SYSGEN_RDP.
- SYSGEN_RDP_AUDIO
- SYSGEN_RDP_CLIPBOARD
- SYSGEN_RDP_DRIVE
- SYSGEN_RDP_PORT
- SYSGEN_RDP_PRINTER
- SYSGEN_RDP_SMARTCARD
- SYSGEN_RDP_UI
For more information about RDP Sysgen variables, see RDP OS Design Development.
See Also
Reference
Concepts
RDP 5.2 Migration Issues
RDP 5.1 Migration Issues
RDP Support in Windows Embedded CE