In some configurations, the nodes are externally addressable using an internal node IP address. Redirecting a user to their disconnected Terminal Server session, referred to as client re-vectoring, occurs in one of two ways depending on the configuration of the load balancing solution being used. If a user connects with a different initial program specified in the RDP client, then they will not reconnect to their disconnected session. The UserName, Domain and application-type fields are the parameters that the Session Broker uses to determine if a request should be reconnected to a disconnected session. Resolution height - this could be set either at the server or client levelĬolor depth of the session - this could be set either at the server or client levelĪlthough there are a number of fields listed in the Session Broker database, not all of these parameters have to match in order to reconnect a user to their disconnected session. Resolution width - this could be set either at the server or client level Time and date that the session was disconnectedĪ protocol-dependent identifier that differentiates between a desktop session or a single-app session Time and date the session was first created Protocol used to connect the session (RDP, ICA etc) Username of the user logged into the session Session ID - which is determined by the server on which the session originated Name of the server that the session resides on The TSSesdir folder contains the following files: In addition, the tssdis.log file is also created in this folder. Once the service is restarted the database is created in the path you specified in the registry. Once you specify a different path, you will need to restart the TS Session Broker service for the changes to take effect. Select the WorkingDirectory value and modify the database location as needed. HKLM\System\CurrentControlSet\Services\Tssdis\Parameters To change the location of the database, you will need to modify the location by using the registry. ) is located on the machine running the TS Session Broker Service in the The Session Broker stores session state information in a Jet database. Let's briefly go over some of the architecture pieces of Terminal Server Session Broker - specifically the Jet Database on the Session Broker Server and the re-vectoring logic used by Terminal Servers participating in the Session Broker farm that ensures that a client is redirected to the proper node. #MICROSOFT TERMINAL SERVER LOAD BALANCING WINDOWS#Windows 2003 Terminal Servers can also join a Windows Server 2008 Session Broker farm - however, in order to use the Session Broker Load Balancing feature, all of the servers in the farm must be running Windows Server 2008. However, from a brokering technology perspective, this is seamless to the end user. Issues around providing a consistent user experience between different server versions are apparent. Windows Server 2008 servers can join a Windows Server 2003 Session Directory farm. To participate in TS Session Broker load balancing, the TS Session Broker Server and the Terminal Servers in the farm must be running Windows Server 2008 Standard, Enterprise or Datacenter Editions. This solution is easier to deploy than Windows Network Load Balancing (NLB). This feature enables you to distribute the session load between servers using DNS round robin. Windows Server 2008 introduces a new session management feature - TS Session Broker Load Balancing (SBLB). Installation of the TS Session Broker role service installs and starts the TS Session Broker service ( As with the Session Directory service on Windows Server 2003, TS Session Broker stores session state information that includes Session ID's and their associated user names, as well as the name of the server where each session resides. Terminal Server Session Broker (TS Session Broker) is a role service in Windows Server 2008 that allows a user to reconnect to an existing session in a load-balanced Terminal Server farm. #MICROSOFT TERMINAL SERVER LOAD BALANCING SERIES#Only three more days until Launch Day! Our Windows Server 2008 series continues today with an overview of Terminal Server Session Broker. First published on TECHNET on Feb 24, 2008
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |