Windows Server 2008 Terminal Services

Over the past decade, SBC (Server Based Computing Services) has
become an integral part of enterprise IT systems.

The key deliverables that terminal services provides are saving
the need to upgrade end stations, centralized management and ability
to connect branches using narrow band lines.

All terminal server farms have three basic services that make
management and user experience simple and user friendly.

Until the Server 2008 version was released, one had to use third
party programs to help manage the farm, but the features that were
added to this edition gives flexibility and simplicity in terminal
farm managing.

In this article, I discuss two key features of Terminal Services 2008
and explain how to use them effectively in the organization.

One of the important issues in the terminal farm is the issue
of load balancing. This ability is integral to the Windows 2008
operating system, using the Session Broker TS mechanism,
or the Session Directory, as it was referred to in Windows 2003.
Its purpose is to support TS session reconnection.

There are 4 steps for achieving this goal:

1.    Installing TS Session Broker

2.    Adding the servers to a local group – Session Director Computers

3.    Attaching the servers to TS Session Broker

4.    Adding DNS entries and load balancing using a round robin
mechanism

Step 1

Like all installations of roles in Server 2008, this service is also installed
as part of the roles of Terminal Services.
After the service is installed, a local group named "Session Directory
Computers” is created on the server.

Step 2

Adding the TS servers to a local group – Session Director Computers

Step 3

Adding the servers to Session Broker (the previous step allowed the servers to be connected to Session Broker)
TS Configuration is accessed by typing tsconfig.msc in the command line and double clicking the line “Member of farm in TS Broker”.

In TS Session Broker, the server is prioritized by selecting a weight. The higher the weight, the more sessions the server receives, and vice versa.

·         Note that there are a wide range of configuration options that relate to Session Server by GPO.

·         Joining TS Session Broker allows the user to define whether TS should join Session Broker

·         TS Session Broker Farm Name – allows one to define a name for the farm that will be attached to the Session Broker

·         Using IP Redirection – allows one to define the reconnection process for an open existing session

·         Configuring TS Session Broker Server – allows the user to set the name or IP address of the broker server (192.168.1.200 is the address mentioned above) that TS servers use for routing users’ sessions

·         Using TS Session Broker Load Balancing – sets option of feature use.

One can put a server into maintenance mode by using the Change Logon command, such as Disable New Connection, but still allow entries of open sessions

Step 4

After choosing a logical name for the farm, TS Window 2008 (ts-farm), this name will be used by the computers during the login process and when the DNS server is accessed.

First, it must be verified that every server is registered in the DNS and has an A Record.
Secondly, to use a round robin, one creates additional A Records (ts-farm) for the TS servers, each entry pointing to a different IP address

Do not forget to take the TTL in the 0 records.

The Session Broker’s load balancing process starts by contacting the DNS, resolving the server address (in this example 192.168.1.52), contacting the same server, receiving “confirmation” from Session Broker that the server is available and then it is ready to receive the session and connect to the client.

 The second feature I wish to show is Ts RemoteApp.

This service allows distribution of applications in two ways:

·         Saving the application run settings to RDP file.

·         Saving the application run settings to MSI file.

In addition, applications may be “published” at the TS Web Access interface (which can remind other management application services) that applications that can be run from any station with a browser and ActiveX.

This also applies to the RemoteApp interface.

At the top of the interface, one can add an application by clicking the link Add RemoteApp Programs 

After creating the application, one can choose distribution or publication.     

At the bottom of the interface you can choose the way to “pack” the connection settings of the application that has been created.

Publishing to the Web interface is performed by selecting the application and selecting whether to show or hide it to the portal.

In sum: There is no doubt that a significant management, maintenance and distribution of applications in Terminal Services 2008 has taken place.

There are additional features that make life much easier and provide printing ability and secure remote access without a client and more.

In the future, I guarantee to continue updating you about additional features in a series of articles on Terminal Services 2008.