Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
On Microsoft® Windows Server™ 2003 family operating systems, the Terminal Server feature gives users at client computers throughout your network access to Windows-based programs installed on terminal servers. With Terminal Server, you can provide a single point of installation that allows multiple users access to the Windows Server 2003 family operating system desktop, where they can run programs, save files, and use network resources, all from a remote location, as if these resources were installed on their own computers.
For computers running Microsoft® Windows® XP or Windows Server 2003 family operating systems, the Terminal Services client program (Remote Desktop Connection) is already installed. Remote Desktop Connection can also be installed on other 32-bit Windows-based operating systems.
Terminal Server is not included in Microsoft® Windows Server™ 2003, Web Edition.
Before you begin using Terminal Server, see Checklists: Setting up Terminal Server.
To find features that have been moved in this release, see New ways to do familiar Terminal Server tasks.
For tips about using Terminal Server, see Terminal Server Best practices.
For help with specific tasks, see Terminal Server How To....
For general background information, see Terminal Server Concepts.
For problem-solving instructions, see Troubleshooting Task Scheduler.
- It is not necessary to install Terminal Server for remote administration of your server. Remote Desktop for Administration is installed by default. To use Remote Desktop for Administration, you must first enable remote connections. For more information, see Enable or disable Remote Desktop. For more information about Remote Desktop for Administration, see Remote Desktop for Administration.
- For additional information about deploying Terminal Server, see "Hosting Applications with Terminal Server" at the Microsoft Windows Resource Kit Web site.