|
RDP Thin Client Fundamentals
|
| bet | 3/43 | | Sana | 21.03.2017 | | Hajmi | 486,5 Kb. | | #828 |
Introduction
Terminal Services (TS) has been part of the Windows operating system since the release of Microsoft® Windows® 2000 Server.
The Terminal Services version built on Windows NT 4.0 was a completely separate product from standard versions of Windows NT 4.0 Server. This approach presented two major challenges:
-
Customers using standard Windows NT 4.0 Server could not use it in a Terminal Services scenario.
-
Security and other fixes for this product were released on their own schedule, sometimes well after the equivalent releases for the base Windows NT 4.0 operating system.
In Windows 2000, Terminal Services is a selectable option in the Server versions of the OS (Server, Advanced Server, and Datacenter). The multi-user kernel extensions, originally developed for Windows NT Server 4.0, Terminal Server Edition, were enhanced and fully integrated as a standard part of the Windows 2000 Server kernel.
The Terminal Services component of the Microsoft® Windows® 2000 Server operating system can deliver the Windows 2000 desktop, as well as the latest Windows-based applications, to virtually any desktop computing device, including those that cannot run Windows. This capability lets more people in an organization take advantage of the resources provided by a distributed computing environment. Terminal Services can also be used to remotely administer a Windows 2000-based server. You can learn more about specific features and benefits and obtain information to guide your Terminal Services deployment by accessing the Terminal Services home page at http://www.microsoft.com/terminalserver.
This document assumes that you have a general understanding of Terminal Services architecture and implementation practices. The features discussed in this white paper are specific to Windows 2000 Server Service Pack 2 and version 5.0 of the Remote Desktop Protocol (RDP) Terminal Services client.
The purpose of this document is to describe the fundamental workings of local printer redirection in Terminal Services by examining the architecture on both client and server that makes this feature work, as well as to explore best practices and methodologies for troubleshooting and dealing with issues that may arise when using this feature.
|
| |
