Terminal Services allows you to deliver Windows-based applications, or the Windows desktop itself, to virtually any computing device, including those that cannot run Windows.

Terminal Services Licensing Server Required for Windows Server Terminal Services Clients
Microsoft Knowledge Base Article - 291807 - According to the end-user license agreement (EULA), if you are using a licensed version of Windows 2000 or Windows Server 2003, you do not have to purchase a Windows Server Terminal Services Client Access license to connect to a server that is running Windows Server Terminal Services. However, you must still deploy and activate a server that is running Terminal Services Licensing.

Maximizing the Windows Server 2003 Terminal Services Evaluation Period
Microsoft Knowledge Base Article - 813052 - This article describes how to maximize the Windows Server 2003 Terminal Services evaluation period.

Changes to the Terminal Services Installation in Windows Server 2003
Microsoft Knowledge Base Article - 278513 - This article describes changes to the Terminal Services installation in Windows Server 2003.

How to Change the Listening Port in the Windows Terminal Server Web Client
326945 - By default, Windows Terminal Server uses TCP port 3389 for client connections. As a security option, you may want to change this port. This article describes how to change the default listening port in the Terminal Server Web Client

How to Configure Terminal Services Session Directory Service
Microsoft Knowledge Base Article - 301923 - This article describes the different methods you can use to configure the Terminal Services Session Directory service.

HOW TO: Connect Clients to Terminal Services in Windows Server 2003
Microsoft Knowledge Base Article - 814585 - For a Microsoft Windows 2000 version of this article, see This step-by-step article describes how to connect a Windows Server 2003-based terminal services client to a terminal server by using Remote Desktop Connection

How to Connect to and Shadow the Console Session with Windows Server 2003 Terminal Services
Microsoft Knowledge Base Article - 278845 - This article describes how to use Windows Server 2003 Terminal Services to connect to and shadow a console session.

HOW TO: Connect to Terminal Services with a Color Resolution of Greater Than 256 Colors in the Windows Server 2003 Family
Microsoft Knowledge Base Article - 323353 - This step-by-step article shows you how to use a color resolution of greater than 256 colors when you connect to a Windows Server 2003-based Terminal Services computer.

HOW TO: Deactivate or Reactivate a License Server By Using Terminal Services Licensing
Microsoft Knowledge Base Article - 814593 - This step-by-step article describes how to either deactivate or reactivate Terminal Services Licensing on a server that is running Windows Server 2003. You must activate a license server before it can issue licenses to Terminal Services client.

HOW TO: Install the Terminal Services Client in Windows 2003
Microsoft Knowledge Base Article - 816590 - For a Microsoft Windows 2000 version of this article, see This article describes how to install the Windows Terminal Services, Remote Desktop Connection client from a Windows 2003 Server computer that is running Terminal Services.

Installing Office 2000 on Terminal Server on a Windows Server 2003-Based Computer
Microsoft Knowledge Base Article - 283675 - If you try to install Microsoft Office 2000 on Terminal Server on a computer that is running Microsoft Windows Server 2003, you receive the following error message: Some default settings in Microsoft Office 2000 setup do not work properly on a Windows Terminal Server. To install Office on Terminal Server you must use the instructions and tools available in your Office 2000 Resource Kit or at http://www.microsoft.com/Office/ORK

HOW TO: Secure Communication Between a Client and Server with Terminal Services
Microsoft Knowledge Base Article - 816594 - For a Microsoft Windows 2000 version of this article, see This step-by-step article describes how to secure communications between a client computer and a server by using Windows Server 2003 Terminal Services

How to Turn On the Terminal Services Session Directory Logging Service
Microsoft Knowledge Base Article - 327508 - To troubleshoot Session Directory for Terminal Services servers, you can use the Terminal Services Session Directory logging feature. This article describes how to turn on this feature.

How to Use Earlier Versions of Terminal Services Client in Windows XP and Windows Server 2003
Microsoft Knowledge Base Article - 320493 - In Windows XP and the Windows Server family, Remote Desktop Connection is already included in the operating system. You can install and run earlier versions of Microsoft Windows Terminal Server 4.0 client and Microsoft Windows Terminal Services 5.0

How to Shadow a Terminal Server Session Without Prompt for Approval
292190 - This article describes how to shadow a Terminal Server session without a prompt for approval

HOW TO: Use IPSec Policy to Secure Terminal Services Communications in Windows Server 2003
Microsoft Knowledge Base Article - 816521 - You can use Windows Server 2003 Terminal Services to access programs in a multiple-user Terminal server environment. Communications between the Terminal Services client computer and the server that has Terminal Services enabled may contain sensitive information. Therefore, you may want to optimize security between the Terminal Services client and the Terminal server. This step-by-step article describes how to secure Terminal Services communications by configuring the Terminal server to require varying degrees of encryption by using the RC4 algorithm. Many organizations use standardized Internet Protocol security (IPSec) for network security. You can configure IPSec policies on Terminal servers to make sure that IPSec protects all the Terminal Services communications. This article assumes that you are configuring computers that are a part of a domain structure. If the computer is not part of a domain structure, you may also have to configure encryption and authentication services

HOW TO: Use Group Policy to Configure Automatic Logon in Windows Server 2003 Terminal Services
Microsoft Knowledge Base Article - 324807 - This step-by-step article describes how to use Group Policy to configure automatic logon in Microsoft Windows Server 2003 Terminal Services. When you use Remote Desktop Connection to connect to a Windows Server 2003-based computer running Terminal Services

HOW TO: Use Group Policy to Permit Users to Redirect and Play Audio in a Remote Desktop Session to Terminal Services in Windows Server 2003
Microsoft Knowledge Base Article - 818465 - This article discusses how to enable the Allow audio redirection Group Policy setting in Windows Server 2003 so that users who connect to the server in a Windows Terminal Services session by using Remote Desktop Connection can configure how they want to play audio output.

Session Directory and Load Balancing Using Terminal Server
The session directory keeps a list of sessions indexed by user name. This enables a user, after terminating a session, to reconnect to the terminal server where the previous session resides to resume working in that session. This white paper discusses how to plan and deploy a load balanced terminal server farm using session directory, and how the session directory operates in a load balanced environment

Terminal Services and Printing
Microsoft Knowledge Base Article - 818758 - Windows Server 2003 Terminal Services allows access to Windows-based including both earlier software and the latest programs for client computers. It also allows remote access to your desktop and installed programs. This white paper describes how to use Terminal Services with printers.

How to Override the License Server Discovery Process in Windows Server 2003 Terminal Services
Microsoft Knowledge Base Article - 279561 - This article describes how to override the license server discovery process in Microsoft Windows Server 2003 Terminal Services

Terminal Services Licensing Server Discovery
Microsoft Knowledge Base Article - 301932 - This article describes the Terminal Services Licensing service discovery methods that are used by Windows Server 2003-based servers

Windows XP and Windows Server 2003 Are Not Advertised as Terminal Services Servers
Microsoft Knowledge Base Article - 281307 - When you browse for computers by using the Remote Desktop tool or the Terminal Services Client tool, Windows XP-based and Windows Server 2003-based computers with Remote Desktop enabled may not appear in the list of available computers.