Terminal services client for windows 2003 server

Within Windows environments there are several key combinations used to focus Windows or bring up the security menu. By default, these key strokes are captured locally on the client device and are not sent to the Terminal Server session. In some environments, users might need these keystroke combinations within their RDP sessions.

How would the user do that from her Terminal Server session? This is truly a client side setting that cannot be configured on the server. You can configure it to use the key combinations on the local client only default , the remote server only, or send to the remote server while you are connected to it in a full screen mode. One advancement of Windows Server is the introduction of support for up to bit color in RDP sessions.

The new client supports 8-, , and bit color. In general, the higher color depths add overhead to the bandwidth used by the client. The amount of overhead varies greatly depending on the types of applications being run, but testing shows it's about a kbps increase each time you increase color depth. In addition to the various features they support, several of the RDP clients also have capabilities to increase the performance of the RDP session.

This is done in several ways. Full performance tuning details are discussed in Chapter Some RDC clients have the ability to cache bitmap images from the Terminal Servers increasing the performance of a session since popular screen objects can be retrieved from the local cache instead of from the Terminal Server. Bitmap caching is generally beneficial, especially with applications that have a few main screens that most users flip through. It also works well in WAN environments.

As you can see by this path, the bitmap cache is stored under the "local Settings" folder, meaning that it's not replicated as part of a roaming profile. Writing this chapter via a Terminal Server session with Microsoft Word created two cache files that were 8 and 19MB in size. You can also adjust how the Terminal Server shell draws its menus and windows.

By default, Windows "rolls" the menus down. While pretty to look at, it also means that more graphic data would be sent to the client device in Terminal Server environments. Most RDP clients allow you to disable menu and window animations for their sessions, potentially saving bandwidth.

As the name implies, you can choose to not show window contents while dragging causing window dragging to look as it did in the old days—a simple wire-frame outline is drawn instead. Just like the other animation-related client performance options, disabling this option can increase performance since less graphic data is sent to the client. Maximum time in seconds after which disconnected sessions are ended. This value becomes effective only if you set the fInheritMaxDisconnectionTime flag to 0.

Maximum idle time in seconds for user sessions. This value becomes effective only if you set the fInheritMaxIdleTime flag to 0. Remote control configuration. This value becomes effective only if you set the fInheritShadow flag to 0. Set a phone number for modem callback. This value becomes effective only if you set the fInheritCallbackNumber flag to 0.

Initial program that is started when a user logs on. This value becomes effective only if you set the fInheritInitialProgram flag. Set a default password when logging on to a user session. The password is encrypted and saved here. However, do not change these attributes. The keys you find there include, for example, the display name, description, complete path, or start options as also listed under services administration. The subkeys show license settings and parameters for the performance indicator object of the system monitor.

Windows Server no longer needs this key. It remains in the registry for compatibility reasons only. If you log registry access in a focused manner during logon of a user session, you will gain interesting insights into the corresponding initialization processes.

For example, which areas relevant for terminal servers does the Winlogon. One piece of information needed during logon concerns creating or loading the user profile. These keys contain the default paths for a default user DefaultUser , general user AllUsers , and individual user profiles.

Furthermore, you can find a list of all users who have logged on to the system here. If a user logs on to the terminal server for the first time, he or she inherits both the normal default user settings and the default values for the terminal server session.

It includes the AppSetup key that defines a special script file called UsrLogon. This script file is executed along with a possible logon script on startup of each terminal server session.

See Chapter 7. The same location also contains the WinStationDisabled key that either denies 0 or allows 1 new terminal server users to log on, regardless of the protocol. It defines a specific logic as a response to system events. When a user logs on, even driver configuration is accessed. The video driver configuration plays a certain role for the user session, too. For instance, Explorer. If local Group Policies for Terminal Services settings were established, these must be loaded at the right time, of course.

Your local drives appear as driveletter on tsclient , where tsclient is the name assigned to your local computer. Locate the file that you want to copy, right-click the file, and then select Copy. Skip to main content.

This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. If necessary you can send those users messages and even take control of their machines. Sometimes users do not logoff, and so you may wish to delete old sessions to free up resources. All I want to do here is point out that each client needs a Microsoft licence.

Users who connect from an old Windows 9x machine cannot expect to get the XP experience interface for nothing, so they must buy a licence. The two exceptions, which do not require a licence, are remote administrators mode, and XP machines. The precise cost of the licences will vary. I wish that I could be more definite, but there are so many deals and rule changes that it is impossible to give an accurate up-to-date figure.

Thankfully the utilities are displayed logically: monitoring, network discovery, diagnostic, and Cisco tools. It is virtually identical to the remote desktop of XP. You can also allow the user to tune the performance and the resources.

Perhaps most of these settings are best controlled by a Group Policy.