In Terminal Server mode, the Terminal Services server enables administrators to deploy and manage enterprise applications from a central location. The server's graphical user interface is transmitted to the remote client (the thin client), and the client sends keyboard and mouse signals to the server. Users log on through any client on the network and can see only their individual session. Terminal Services manages unique client sessions transparently. Many different types of hardware devices can run the thin client software, including Windows-based terminals and computers.
You can deploy applications by installing them directly on the server or you could use Group Policy and Active Directory to publish Windows Installer application packages to a Terminal Services server or a group of Terminal Services servers. Applications can be installed by an Administrator—only on a per-server basis, and only if the appropriate Group Policy setting is enabled.
It is necessary to use a license server; each client computer that will connect to the Terminal Services server must have a Terminal Services Client Access License as well as a Client Access License for the appropriate version of Microsoft Windows. Terminal Server licensing is covered in detail in the section "Determining Proper Licensing Requirements," later in this chapter.
In Windows 2000, Terminal Server mode was called Application Server mode.
Was this article helpful?