Windows Server 2003 Technology Primer - Benefits for Thin Client Terminal Services
(Page 14 of 20 )
Windows Server 2003 released a series of significant improvements to the Terminal Services capabilities for thin client access. A client system working from a browser, a Windows terminal, or running the Remote Desktop Client software from a desktop system can access a centralized Terminal server to gain access to network resources. With Windows Server 2003, these same remote users can now do local drive and audio redirection, have local time zone support, choose the speed of connection to optimize the session performance, and take advantage of a service called Session Directory that provides better redundancy and recoverability in the event of a LAN, WAN, or Internet interruption.
Although all these new capabilities are highlighted here, they are covered in detail in Chapter 27, which addresses their planning, design, prototype testing, implementation, and optimization.
Local Drive and Audio Redirection
An update to Terminal Services in Windows Server 2003 is the ability for a remote client to access local hard drives as well as redirect the audio from a centralized Terminal server to a remote system. In the past, these capabilities required a relatively expensive add-in from Citrix Systems. Now that these capabilities are built into the core Windows Server 2003 Terminal Services, an organization can choose whether it wants to or needs to purchase the add-in.
Local Drive Redirection
Local drive redirection allows a remote user to log on to a centralized Terminal server to access network resources; however, if the user wants to retrieve or save files to a remote system, that system shows up as a drive letter on the session. The user can now drag and drop files between a remote system and the centralized server. The remote file access can include local C: hard drives, CD-ROM drives, floppy drives, or any other device that creates a drive letter for remote system access.
Audio Redirection
Audio redirection allows a remote user to log on to a centralized Terminal server and have sound redirected from the centralized system to the speaker of the remote client system. With organizations integrating voicemail and other audio-integrated tools and utilities into their daily business operations, having the ability to redirect audio to the remote system allows an organization to better support business tools using sound as part of the communication infrastructure.
Local Time Zone Support
With Windows Server 2003 Terminal Services, when a remote user logs on to a centralized Terminal server, the user now can work on either the default time zone on the server or choose the local time zone. This capability is important for organizations that have centralized servers used by employees across the country or around the world.
Earlier versions of Windows had support for only one time zone: the time zone of the Terminal server system. This meant that if the Terminal server was in California and a user from Georgia logged on to the Terminal server, all the individual's email messages or time stamps on file access were based on the Pacific time zone. With local time zone support in Windows Server 2003, now the remote user in Georgia can specify in her remote client access software to use the local time zone. Now when emails are sent, or when files are saved, the time stamp on the communications will be based on the Eastern time zone, where the user resides.
Windows Server 2003 supports all time zones and can have users from all time zones accessing the server at the same time.
 This chapter is from Microsoft Windows Server 2003 Unleashed, by Rand Morimoto, et al. (Sams Publishing, 2004, ISBN: 0672326671). Check it out at your favorite bookstore today.
Buy this book now. |
Next: Specifying Connection Type >>
More MS SQL Server Articles
More By Sams Publishing
/ 8 
