Thin Client Best Practices (Windows Embedded CE 6.0)
1/5/2010
This topic shows Windows Embedded CE powered thin client operating system (OS) design best practices.
Persist the Registry
The following list shows ways that you can persist the registry.
- You can transfer registry data to and from persistent storage by using WriteRegistryToOEM and ReadRegistryFromOEM, respectively.
- You can persist data by using the hive-based registry. No work is necessary during startup or shutdown to preserve registry data, unless a typical software shutdown is not performed and the OEM has to flush the registry by using RegFlushKey if. For more information, see Data Persistence with the Hive-Based Registry.
- You can persist data with the RAM-based registry. This supports two save-and-restore mechanisms in order to persist registry data when the RAM is not being powered. In addition, the mechanisms can be used to provide protection against invalid data. For more information, see Persisting Data with the RAM-Based Registry.
Note
You can select the type of registry for your OS design in the Catalog in Core OS\CEBASE\File Systems and Data Store\Registry Storage.
Implement IOCTLs and OEMIOCTLs
The OEM Adaptation Layer (OAL) is typically built by the vendor that supplies your BSP. Work with your BSP vendor to make sure that the OAL supports the I/O control codes (IOCTLs) and the OEM-defined I/O control codes (OEMIOCTLs) that are required for communicating with the drivers that are specific to your thin client. For more information, see OEM Adaptation Layer.
The following task should be completed to implement the IOCTLs and OEMIOCTLs that are required by your thin client platform.
- To meet the Terminal Services license requirement, you must call GetUUID. For more information, see Reading a UUID.
Provide OS, OEM, and Terminal Properties
The OS developer should add the OS version, OEM version, and terminal name to %_WINCEROOT%\PUBLIC\RDP\OAK\UIT\ATLPROP\generalproperties.cpp.
See Also
Concepts
Thin Client Overview
Thin Client Security