Category list

Benefits of Terminal Services

< Day Day Up >

Benefits of Terminal Services

Deploying Windows Server 2003 Terminal Services on servers gives the customer the following general benefits:

Rapid, centralized deployment of applications : Terminal Server is great for rapidly deploying Windows-based applications to computing devices across an enterprise ” especially applications that are frequently updated, infrequently used, or hard to manage. When an application is managed on Terminal Server, and not on each device, Administrators can be certain that users are running the latest version of the application.
Low-bandwidth access to data : Terminal Server considerably reduces the amount of network bandwidth required to access data remotely. Using Terminal Server to run an application over bandwidth-constrained connections, such as dialup or shared WAN links, is very effective for remotely accessing and manipulating large amounts of data because only screen graphics, keyboard strokes, and mouse clicks are transmitted, rather than the data itself.
Windows anywhere : Terminal Server helps users become more productive by enabling access to current applications on any device ”including underpowered hardware and non-Windows desktops. And because Terminal Server lets you use Windows anywhere, you can take advantage of extra processing capabilities from newer , lighter-weight devices such as the Pocket PC, PADs, and intelligent phones.

Terminal Services is Microsoft's implementation of Server Based Computing (SBC), which means that all software resides on the server. Additional benefits of a SBC environment include

IT consolidation
Smooth migrations from non-Windows environments to centralized II- infrastructures
Lower application ownership costs
Elimination of additional development, testing, or deployment procedures for individual applications
Accelerated application deployment
Extended application availability
Enhanced security
Improved data backup and recovery
Improved end user support
Uniform desktop experience from any network access point

< Day Day Up >

Client Features

In Windows 2000 Terminal Services, you could establish a remote connection only by installing the Terminal Services client. This could be done by creating the client floppy disks in the Terminal Services Client Creator in the Administrative Tools, or by drilling down via %systemroot%\system32\ clients \tsclient\win32\disks\disk1 and running setup.exe. This installs Terminal Services client on the server you are logged in to (or via a share) without creating floppy disks.

note

Windows 2000 did not provide a client to permit remote connection to client workstations (that is, Windows 2000 Professional, or downlevel clients such as Windows NT Workstation or Windows 9x clients). Windows Server 2003 and Windows XP clients both provide Remote Desktop clients built into the OS and available by choosing Start, Programs, Accessories, Communications, Remote Desktop Connection.

The new Terminal Services client introduces several features that help manage Terminal Servers and Windows Server 2003-based computers. Called the Remote Desktop Connection (RDC), the Windows Server 2003 RDC client can be used to connect to previous versions of Terminal Services (Windows NT 4.0 Terminal Server Edition and Windows 2000). However, the new features, such as high color and file system redirection, are supported only on Windows XP and Windows Server 2003.

Improved Client Interface

RDC has a simplified user interface (UI). A separate Connection Manager is no longer needed because the functionality of the connection manager is included and enhanced in the RDC.

As shown in Figure 15.1, to initiate an RDC connection, simply enter the computer name and click Connect.

Figure 15.1. Remote Desktop connections.

A connection can be saved in a file that can be stored and used locally or deployed to other users. Passwords that are saved are encrypted and can be decrypted only on the computer on which it was saved.

Remote Connection Options

A number of connection options can be customized according to user preferences. To customize your session, on the Remote Desktop Connection screen, click on Options. These new features are available to any computer that can run RDC.

Under Options there are five tabs that are summarized in Table 15.1.

Table 15.1. Remote Connection Options

Tab	Function
General	Computer, Username, Password, and Domain. There is also an option to Save a Password, to Save Current Settings as a File, and to Open Saved Settings.
Display	Desktop Size, Colors, and Full Screen (A remote session is launched in full screen and with high color by default.)
Local Resources	Remote Computer Sound, Keyboard Combinations, and Local Devices (disk drives , printers, and serial ports.)
Programs	Start a Program on Connection.
Experience	Performance options, including Connection Speed, Desktop Background, Show Contents of Window While Dragging, Menu and Window Animation, Themes, and Bitmap Caching.

Redirected Printer Names

With Windows 2000 Terminal Services, only locally connected printers were redirected. With Windows 2003 Terminal Services, redirected printers are given names that are easier to read. For example, users might see "printername on printserver (from clientname) in session 7," whereas in Windows 2000, they would have seen "_printserver_printername/ clientname/ Session 7." This new naming convention is less cryptic and makes printer identification easier.

Low Bandwidth Optimization

Performance over low bandwidth connections can be optimized by selections on the Experience tab. Modem, broadband, and LAN connection speeds can be selected. Options such as animation and background can be eliminated to improve performance.

Switching to the Remote Session

A connection bar at the top of a full-screen RDC session lets the user switch between the local desktop and a remote session.

Automatic Reconnects

The RDC automatically attempts to reconnect when a faulty network connection causes a session disconnect. This is especially helpful in dial-up or wireless applications.

Resource Redirection Security

Data redirection types can be disabled by either the client or the server. When a file system, port, or SmartCard redirection is requested , a security alert is displayed and the user can cancel the connection or disable the redirection at that time.

SmartCard Sign On

SmartCards can be used to log on to an RDC session. This feature is limited to Windows 2000, Windows XP, and Windows CE .NET clients because the SmartCard must first be recognized by the client OS.

note

Smart Card sign on works only with Windows 2000, Windows XP, and Windows CE .Net clients.

Virtual Channels

Virtual channels, available in both Windows 2000 and Windows Server 2003, are software extensions that can be used to move data between client and server computers. Virtual channels add to the core Remote Desktop protocol functionality and are managed by the Remote Desktop protocol.

Remote Desktop Web Connection

Remote Desktop Web Connection provides computer access over the Internet using Internet Explorer and TCP/IP. Most of the functionality of RDC is offered in the Remote Desktop Web connection. To support this feature, the computer must be using Internet Information Server (IIS) to host a Web site. Remote Desktop Web Connection is a Web application that consists of an ActiveX component and a sample connection page.

To Install Remote Desktop Web Connection on Windows Server 2003, perform the following steps:

1. Go to Control Panel, and click Add/Remove programs

2. Under Add/Remove Windows Components, click Install IIS.

3. Install the World Wide Web Service component of IIS.

4. Install the Remote Desktop Web Connection subcomponent of the World Wide Web Service.

The Remote Desktop ActiveX control and sample Web page are installed in the %systemroot%\web\tsweb directory. The sample Web page will be shared in the tsweb directory on the server: http:// servername /tsweb . The control (msrdp.ocx) and the Remote Desktop Web Connection code are contained in Msrdp.cab.

Web Connections on Other Platforms

Windows 2000 Server, SP1 contained the ValueAdd component Terminal Services Advanced Client (TSAC), which expanded Terminal Services technology to the Internet.

RDC software for other platforms such as Windows 2000, Windows 98, Windows ME, Windows NT, and Windows XP systems is available on tswebsetup.exe, which can be downloaded from Microsoft's download center at http://www.microsoft.com/downloads/details.aspx?FamilyID=e2ff8fb5-97ff-47bc-bacc-92283b52b310&DisplayLang=en.