In fact, the max-session limit is disabled by default. The max-session limit is something that needs to be manually configured - it is not automatically calculated by Terminal Server. The unavailability of servers in the farm should be a short-term phenomenon (hardware replacement, troubleshooting etc). However, if the administrator knows his system(s) well, then this should not be a long-term issue. By protecting the currently connected users' experience, other users may not be able to establish a Terminal Server session at all. This prevents a degraded user experience for the users already connected to a Terminal Server should other servers in the TS farm not be available. The max-session count means that ever server in the farm has determined a maximum amount of sessions that it can host. For example let us assume that the terminal servers are configured to host no more than ten concurrent user logons per server.
The Session Broker itself can guard against the Black Hole effect by limiting the outstanding connections to the same Terminal Server. Once the logon process has finished, the server load returns to normal. The first is to artificially make the server load higher during a logon to prevent a Terminal Server from being inundated by new logins. SBLB has two ways to protect a server against the Black Hole effect. It also has built-in black hole protection (logon throttling) and a max-session count. However, SBLB does more than just count the user sessions. The Session Broker Load Balancing (SBLB) in Windows Server 2008 is managed based on the number of sessions. Windows Server 2008 Session Broker can be run with Session Broker Load Balancing disabled - which would then function in a similar mode to Windows Server 2003 Session Directory. Windows Server 2008 Session Broker provides some additional features such as a load-balancing capability as well as the ability to gracefully "drain" servers prior to scheduled maintenance. Windows Server 2008 Session Broker provides the same cross-server session reconnection capability as Windows Server 2003 Session Directory. So sit back, grab your coffee or tea (or if you're like me, your bottle of water) and let's begin. Yesterday's post on Terminal Server Session BrokerĪnd look specifically at Session Broker Load Balancing. Only two days to go until the launch of Windows Server 2008. It's Monday morning - hopefully those of you returning from your weekends got some time to rest and relax.
First published on TECHNET on Feb 25, 2008ĭay Twenty-Five.
0 kommentar(er)
