One domain attached Windows Server 2008 box to host the TS Session Broker role.Server Configurationīelow are the steps for a basic deployment of TS Session Broker Load Balancing. TS Session Broker has the ability to see how many connections there are on each terminal server in a Windows Server 2008 TS farm and direct new remote desktop sessions to the server with the least number of connections. TSSD is able to redirect users back to the appropriate terminal server if they are attempting to reconnect to a disconnected session, but it does not have any logic to even out the load among terminal servers (i.e. Microsoft has also made this feature available in the Standard version of Windows Server 2008 (the TSSD feature required the Enterprise edition of Window Server 2003). This feature has been enhanced and renamed to the TS Session Broker role in Windows Server 2008. Windows Server 2003 introduced the Terminal Services Session Directory (TSSD) feature.

TS Session Broker with load balancing makes it easy to deploy multiple load balanced terminal servers, and even return users to the correct terminal server if they’ve left a TS session open. If these new features entice you to increase the TS footprint at your organization then you will likely want to deploy multiple terminal servers to handle the load and ease maintenance. TS Gateway finally gives us a way to monitor and manage remote desktop connections.

TS Remote Apps lets you present TS based applications to users in a way that is virtually identical to a standard desktop app. Windows Server 2008 has added several very useful enhancements to Terminal Services (TS).

Microsoft terminal services