Terminal Services in Windows Server 2003 - Client Connections
Guy Recommends
A solution to monitor, manage and archive thousands of
events that are generated by devices across the entire network. Download FREE
trial
Introduction to Terminal Services - Client Connections
If you have already used XP's Remote Desktop then you will have an
appreciation of the style and power of the Terminal Services interface. Windows Server 2003 has a service called Terminal Services, which provides the XP experience to Windows 95 and even web clients. Just to be clear on Microsoft's terminology, the Terminal Services Client is called Remote Desktop Connection (RDC). Furthermore, under the covers, the RDC client
connects to its server using RDP (Remote Desktop Protocol).
To configure the terminal services session on the local machine, you need to launch the Remote Desktop client. On an XP machine click Start, All Programs, Accessories, and Communications.
Note 1: If you want to be flashy,
click
Start then Run, type mstsc.
For other host operating
systems, locate the folder where the administrator installed the RDC client. If you are that administrator, then you can install the client from Microsoft's XP CD. Note you don't need to install the whole
XP operating system, just seek out the 'Additional Tasks' menu. Still stuck for a client? Go to Microsoft's site and search for 'download remote desktop'.
You will enjoy configuring the client
by pressing the aptly named Options button, which you find on the
Remote Desktop Connection logon interface. (See blue ring on diagram above.)
If you are going to connect to the Terminal Server regularly, click on the General Tab and type in the username and password. I love the box which enables Windows to remember my
password. The only slight difficulty is the 'Browse for server button', however if you remember to type the name of the computer in the first dialog box, there is no problem finding the Windows 2003 Server.
If you are interested in cost effective Thin Client check out the experts: 2X (Guy's Recommendation)
2X ThinClientServer allows you to deploy a thin client OS to low-cost thin client devices and existing PCs, and
centrally manage settings and configure to which terminal servers (Windows or Linux) a user should log on to. More on 2X ThinClientServer
2X LoadBalancer for
Windows Terminal Services Provides load balancing, increased security and redundancy for Terminal Servers.
Microsoft have corrected the biggest problem in previous editions of terminal services, namely improved Color resolution. The Colors menu (opposite) shows how easy it is to choose the
highest resolution that your client's monitor supports. The range now goes from 256 right up to True Color (24 bit).
Microsoft provide a slider to adjust the remote desktop
size, however I find it just as easy to use the normal windows controls once I have connected to the server.
Remote Desktop connection also has a
Programs tab. While I have not found a 'killer' use for this button, if you can think of an application that would help users, then Microsoft have provided the interface for you to launch it on the XP
client.
In some ways this Programs tab is a substitute to the Startup menu found on normal XP clients.
On the Remote
Desktop Options, the Local Resources tab reveals many of the most useful new features. In previous generations of Terminal Services it frustrated me that I could not Alt + Tab, well now I can execute this
trusty keyboard combination.
Local Devices give users a choice of server or local machine for disk drives, printers and COM ports. However, there will always be an element of confusion as to
whether a disk, COM port or printer is on the server or on the client. Users need no invitation to 'lose data'. The danger is that they may think they are saving files locally, whereas the files are
actually saved on the server. To conclude, you may wish to control local devices via Terminal Services Group Policies.
There are enough Terminal Services options to warrant producing a short training document / web page
or even a short course. If you decide to go down this user training route
then looking after files would be a central element in your best practice documents.
There is one more decision with local resources, and that concerns sound. If it were me, then I would want to control the audio
setting, 'Bring to this computer' setting.
However, if you were setting up a Terminal server kiosk, then the option to 'Leave sound on the server' would be preferable.
The Experience tab is gives
you a sense of power and control. Your first decision is to select the most appropriate connection speed. If you need low bandwidth connections,
then you can remove the ticks next to Bitmap caching and
Themes.
Try experimenting with ticking, 'Show contents of window while dragging' and 'Menu and window animation'. If you are going to spend time with the a Terminal Server connection, then its worth spending a
few minutes investigating the variety of setting available.
Here is a surprise. For once Microsoft's Security tab is not about permissions, but about
authenticating the Server to the client. The idea is twofold. Firstly, to ensure that the users on the client are connecting to a know server and not a phishing or fake server. Secondly, to ensure that the
connection, once established is secure.
Technically, security relies on Transport Layer Security (TLS) 1.0; therefore, to provide this level of authentication you must apply SP1 to the Windows 2003 Server. High
security companies rave about the new security, whereas the rest say, 'One more setting to go wrong, we will leave this tab alone'. Guy says, 'The more security you have the more work for you the
administrator,.
Learn more about Terminal Services and VPN. As an MCT trainer, I can thoroughly recommend TrainSignal
because they provide practical hands on training. In particular, I like the way TrainSignal cover all learning methods, instructor lead, video and of course text
material. With TrainSignal you can either take one module, for example Terminal Services and VPN or go for a combination of modules.
See more about Terminal Services
and VPN here
The Remote Desktop Options button opens the door to 6 more tabs where you can control every aspect of the client's Terminal Services (XP) experience. If I could single out two settings to check, make
sure you get high 24 bit color, and decide when you save files, if its to the local machine or the server.
Your first decision is to select the most appropriate connection speed. If you need low bandwidth connections,
then you can remove the ticks next to Bitmap caching and
Themes.
