Once terminal services has been installed, the next step is to install the client software on systems that you wish to be able to connect. By default, the client software is found in the%systemroot%\system32\clients\tsclient folder.This folder can be shared, which would allow you to install the client over the network (it is not shared by default). Alternatively, Windows 2000includes an administrative tool called the Terminal Service Client Creator, which will create a set of floppy disks containing the client software.
The 16-bit version requires 4 disks, while the 32-bit version requires 2. Once the client software is installed, the user will use the terminal service client to access the server. The client will display a list of accessible terminal servers in the domain or work group, allowing the user to specify a server, as well as the screen resolution, and so forth.
The option to compress data is selected by default,while the option to cache bitmaps to disk is not, but will speed up performance by reducing the amount of data passed over the connection. After the client chooses a server from the list, they will be prompted to log on, just as if they were sitting at a Windows 2000-based system, except that it all happens from within a program window.Once logged on, their session appears within a separate window.
By default, all domain users have the ability to logon to a terminal server. However, it is possible to control who can and cannot, via a the terminal services profile tab, as shown below:
Note a few important points here beyond the ‘allow logon to terminal server’ checkbox. The User Profile section allows you to provide individual profiles to users. If you choose not to, all users will use the same profile, and will be subject to any additions or deletions made by other users.Also, you might consider providing the users with a home directory which is mapped automatically when the log on to the terminal server, since users may not be logging on from Windows2000-based systems.
Since clients are creating a session with the terminal server, it is also possible to control what happens when a session is left idle or disconnected, since sessions will use up server resources. The session tab on a user account controls settings for a given user. These user settings can be overridden at the server level if necessary.