Customizing a Thin Client (Windows CE 5.0)

  • Article

Send Feedback

After you create the Thin Client OS design, you can customize it by changing the registry settings. For more information about altering the OS design, see Adding an Item from the Catalog or Removing a Catalog Item from an OS Design.

You can change the Thin Client registry settings in the following ways:

  • Modify the Project.reg file before building and downloading the run-time image. For more information, see Terminal Services Client Configuration through the .rdp File.
  • After downloading the run-time image to the CEPC and then connecting to a device, use the Remote Registry Editor. Using the Remote Registry Editor changes the image registry, but the changes are not persistent to the registry files in Platform Builder. The next time you download the image, you must configure the registry again. For information about how to use the Remote Registry Editor, see Remote Registry Editor.

For more information about how to configure the Terminal Services Client in the Thin Client registry, see Configuring the Terminal Services Client.

The following topics discuss ways in which you can customize the Windows Thin Client:

In This Section

The following table shows the behavior that you can change by further altering registry settings.

Area Customization
Audio
  • Specify where the audio plays.
Bitmap caching
  • Enable or disable bitmap caching.
  • Specify the size and location of the bitmap cache in memory.
Connection
  • Enable or disable automatic reconnection to the host if a connection is lost.
  • Specify the maximum number of reconnection attempts to the host after a connection is lost.
Display
  • Specify the color depth.
  • Specify the height or width of the display.
  • Specify what to display when ALT-TAB is pressed on the keyboard.
File management
  • Enable or disable file and directory compression.
  • Indicate whether the user has access to the local file system.
Non-Windows-based Thin Client
  • For non-Windows-based Thin Client run-time images, indicate the console to connect to from the command line.
  • For non-Windows-based Thin Client run-time images, indicate the alternate Winsock port for the RDP.
Redirection
  • Enable or disable drive redirection.
  • Enable or disable COM port redirection.
  • Enable or disable printer redirection.
  • Enable or disable redirection of smart cards.
Shell
  • Specify the alternate shell or startup application.
Start up
  • Specify the IP address of the remote device.
  • Indicate whether to start the terminal service session starts in full screen.
  • Specify the folder that contains the alternate shell or startup application.
UI
  • Display or hide the connection bar.
  • Enable or disable full window drag capability.
  • Enable or disable menu animation.
  • Enable or disable themes.
  • Enable or disable wallpaper.
User
  • Indicate the password of the person identified in the UserName value.
  • Indicate the user name of a person who can log on to the remote device.
  • Indicate the domain of the person who can log on to the remote device.

An example of how you might use this information is to change the default behavior of caching the user name. To change this behavior, you must open the .rdp file or registry, delete the user name from it, and then save your changes.

For more information about changing these registry settings, see RDP Registry Settings.

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.