Installation

On another 32-bit Windows version (for example, Windows XP or Windows 2000 Professional), you can install the remote desktop connection from a source folder on Windows Server 2003. This folder is located at %SystemRoot%\system32\clients\tsclient\win32 and contains all files required for the installation. If need be, this folder can be released, that is, it can be accessed over the network. The installation itself is very easy and is supported by a wizard.

Figure 3-10: Initializing the remote desktop connection installation wizard.

After the welcome screen is displayed, you are asked to accept the license agreement and enter the user name and company. Then you decide if the remote desktop connection should be installed for the current user or for all system users. After you enter that information, the installation takes a few minutes to finish. The necessary files are saved to the local hard drive and the start menu is updated. The ActiveX control Mstscax.dll terminal server client is integrated into the system.

When you are done, the remote desktop connection is operable and its application icon can be found under Start\All Programs\Accessories\Communications.

Connecting

With the help of the remote desktop connection, it is quite easy to launch a user session on a terminal server. All you need is network access and the required access permission. To connect, you can select the computer name and other logon settings on the advanced screen that appears when you click the Options button. In this mode, the remote desktop connection user interface displays five tabs. With these tabs, you can choose several settings in different categories.

The first tab is the General tab, which is an expansion of the initial user interface that you see when you connect. It allows you to set basic logon settings:

• Computer Enter a computer name or select one from a list of identified terminal servers.

• User name A user’s logon name.

• Password Optional input of the password, which is used with the user name to log on, if accepted by the terminal server.

• Domain Name of the domain or the local computer that is responsible for authenticating the user.

If desired, the password can be encrypted and saved in the user’s profile so that it can be used for the next logon. However, this might cause system security problems.

The General tab also allows you to save and open connection settings in files. The corresponding format is described in detail below.

Figure 3-11: The remote desktop connection General tab.

You select Display options in another tab. You can predefine the remote desktop size, which ranges between 640 x 480 and 1600 x 1280 pixels. The highest setting depends on the maximum resolution of the local graphics card. Alternatively, you can select the full-screen mode that covers the entire client screen and completely hides the local desktop.

You also use this tab to select the number of colors used. The range lies between 256 colors and full-color mode (24 bit). As with desktop size, the number of colors depends on the settings of the local graphics card. However, these settings can be overridden by other settings on the terminal server because the server configuration takes precedence.

At the bottom of the tab, you will find the option for displaying the connection toolbar in full-screen mode. The connection toolbar contains window control elements, such as minimize or maximize. These control elements greatly simplify reactivating the local desktop because it is fully covered by the remote desktop in this mode. If you deactivate this option, the toolbar is displayed for five seconds after logon and then disappears.

Figure 3-12: Display settings.

The third tab deals with Local Resources, that is, audio data streams, keyboard, and other local devices. For audio data streams (sounds), you can select options for playing sounds on the remote computer, on the client, or not at all. In a terminal server environment, only the last two options are reasonable, because sound output on the server is either impossible or undesirable.

For the Windows keyboard shortcuts, you select the option of using them locally or remotely and whether you want them in full-screen mode. This is the only way to clearly allocate the keyboard shortcuts to the predefined target devices. Sessions within the remote desktop connection are controlled using the following keyboard shortcuts. They differ from the local desktop shortcuts to avoid colliding with the client system.

In addition to audio output and shortcuts, the third tab defines the automatic connection to local drives, printers, and serial ports. All this helps to integrate the local resources with the remote user session. The user thus gains intuitive access to the client devices even though the user is active only within the terminal server session.

Note

The smart card reader option appears in this tab if the client has a smart card reader. This reader can be used in the terminal server session. Figure 3-13: Local resources configuration.

If you enter two character strings in the fourth tab, called Programs, you can configure an exclusive program that starts automatically when you log on. The string in Program path and file name specifies the desired program, and the string in Start in the following folder defines the default directory assigned to the program.

When you log on, the normal desktop is not displayed; instead, you’ll see the program in full-screen mode within a remote desktop connection window. This lays the foundation for an environment that runs only one application.

Note

This configuration will not take effect if the settings on the terminal server differ. The terminal server configuration always overrides client settings. Figure 3-14: Start options configuration of a selected program.

By using the last tab, Experience, you optimize transmission performance. The higher the available network bandwidth, the more graphical functions can be used. The optional properties are listed in descending order by requirements. Managing a desktop background (wallpaper) requires the most network bandwidth, whereas a slow connection will still support themes. Caching should always be enabled because it significantly reduces the data rate without degrading performance. However, this is valid only if the client’s memory resources are fast and large enough. Otherwise, caching can have a negative impact on system performance.

The last option in this tab allows you to determine whether the connection will be reestablished if it was ended. Selecting this option ensures continuous communication, even if the lines are unstable.

Figure 3-15: Configuring performance parameters.

Within its graphical user interface, the remote desktop connection offers access to all essential settings that you need to configure and optimize communication with terminal servers. However, you have to use the command line to get to a number of expanded options.

Mstsc Command-Line Options

Instead of invoking the remote desktop connection via the Start menu, you can also use the command line to do just that by calling up Mstsc.exe and several arguments. In this way, you can reuse connection options saved in RDP files.

The Mstsc.exe command syntax:

Mstsc File /v:Server[Port] /console /f /w:Width /h:Height /edit /migrate

You can connect to the terminal server’s console session only by using the command-line option. A referenced RDP file, however, offers more flexibility.

Using an RDP File

By using the remote desktop connection General tab, you have the option of saving the configuration settings selected for connecting to a terminal server. The settings are saved in Unicode text files with the extension .rdp. You can use them either in the graphical user interface or with the command-line option of the remote desktop connection.

RDP files are therefore well-suited for defining default configurations to access terminal servers or individual applications on terminal servers. What other information lurks in RDP files? Here is a closer look at a sample RDP file:

Listing 3-1: Contents of a Sample RDP file

screen mode id:i:2
desktopwidth:i:1024
desktopheight:i:768
session bpp:i:16
winposstr:s:0,1,0,0,800,600
full address:s:TRITON-SRV1
compression:i:1
keyboardhook:i:2
audiomode:i:0
redirectdrives:i:1
redirectprinters:i:1
redirectcomports:i:1
redirectsmartcards:i:1
displayconnectionbar:i:1
autoreconnection enabled:i:1
username:s:test
domain:s:TRITON-SRV1
alternate shell:s:C:\Windows\system32\notepad.exe
shell working directory:s:C:\Documents and Settings\tritsch\My Documents
disable wallpaper:i:1
disable full window drag:i:1
disable menu anims:i:1
disable themes:i:0
disable cursor setting:i:0
bitmapcachepersistenable:i:1

Most lines correspond to settings that can be defined via the graphical user interface. Nevertheless, some of these options need to be explained in detail. The following table provides a detailed description of all lines in the RDP file.