![]() |
Windows Terminal Server, Virtualization, Application Delivery, Windows Software Development, Market Analysis, Training Classes and more... |
|
|
Navigation |
|
|||||||||||||||||||
|
|||||||||||||||||||||
|
|
Awards |
|
||
|
||||
Posted by Benny Tritsch on December 10, 2003 – updated on May 31, 2005
[Introduction] [General] [System
and User] [Default
User] [Folders] [Printers]
[Network]
The relevant configuration options for terminal servers, terminal server sessions, users, and RDP clients can be found in different places in the registry. Administration tools and Group Policies usually change several registry values. The following chapters of this whitepaper provides you with information on their names, paths and default values.
NOTE: This whitepaper provides a general overview of those registry keys that are essential for Terminal Services. A full documentation of all relevant keys would probably be a book in its own right. However, if you know where to find the interesting locations, there is nothing to prevent you from doing your own experiments on a test system. Experiments have produced many tips for optimizing system performance by modifying the registry, just as described in this book. However, it is clearly neither advisable nor recommended to tweak the registry settings on a production system.
DISCLAIMER: Modifying the registry can cause serious problems that may require you to reinstall your operating system. We cannot guarantee that problems resulting from modifications to the registry can be solved. Use the information provided at your own risk.
Windows Server 2003 offers the option to configure applications or scripts in the registry using different keys. These scripts run automatically if a certain event occurs. This mechanism can be used to perform initialization tasks required on terminal servers. The following list presents the corresponding keys in detail
If an application or a script is to be run when a user logs off, the following key is used: