TABLE OF CONTENTS Many organizations choose to run applications on terminal servers rather than installing them locally on each workstation. The advantage to doing so is that the application runs on the server, and only video images are sent to the workstations. This makes it much easier for an administrator to maintain the applications. The terminal services are good for security as well, because applications are much more resistant to user tampering since they do not actually reside on the user s workstations.
In this chapter, you will learn how to configure and monitor the Terminal Services Resources. Next, you ll learn about load balancing. You ll then learn about Terminal Services Gateway, which allows remote users to connect to internal resources securely. You ll then learn about configuring TS RemoteApp, which publishes the applications that can be accessed remotely. Finally, you will learn about managing Terminal Services.
Monitoring any network service is an important task of an IT administrator. Once Terminal Services are deployed, the job of regularly fine-tuning and monitoring them becomes essential to ensure network resources are optimally utilized and the users are getting what they want. Installation of specific server roles, installation of terminal server aware applications and publishing them to make it available to remote users, monitoring user sessions, and deploying load-balancing solutions when the network grows, are the important tasks. In this chapter, we ll discuss the Terminal Services management tools (snap-in/console in Microsoft terms).
Windows 2008 Terminal Services includes the following components:
Terminal Server
