Terminal Server Settings
|
This short guide applies to most popular terminal server settings configurations, including Windows Server versions 2003 to 2003 R2 with the Microsoft Service Packs 1 and 2. Firstly, let’s go through a brief top down view: There are a number of applications which you can use to configure your terminal servers, which includes everything from user settings, session management and connection set up. Some of these are Terminal Services WMI provider, the extension for local users and the Terminal Services Group Policies. Some settings can also be configured each session by the application on the server in question.
When it comes to choosing the right app for the job, you should consider the one which gives you the best control over your set up, while minimizing the initial cost. As an example, if you are running just a single Windows Server 2003 on a terminal server, using the application, Terminal Services Group Policies will permit the configuration of all services and settings throughout the entire section and all users. By using the Active Directory Service Interfaces (ASDI) extension, you can expand this to include all local users and machines by permitting you to write and apply scripts specially designed for your Terminal Services set up needs. There are times when this is not sufficient though, and where Group Policy will not do the job. In these instances, such as when multiple versions of Windows are running, it is recommended you use a mix and match set of tools, e.g. using the Windows Server 2003 with Group Policies, whilst also making use of the Terminal Services Config tool to manage configurations on a once per connection rule.
In general, the hierarchy of config settings is as follows, with the highest coming first:
|
|||
|
|
|||
No Responses to Terminal Server Settings