Thoughts from the EPS Windows Server Performance Team
Useful Microsoft Blogs
TERMINAL SERVER LOAD BALANCING
Description: Terminal Server Load Balancing refers to either Session Directory and Microsoft Network Load Balancing used with Windows Server 2003 Terminal Servers, or Session Broker used with Windows Server 2008 Terminal Servers*. A Terminal Server Farm is often described as two or more Terminal Servers configured to use a Session Directory or Session Broker server and load balanced with either Microsoft NLB, DNS round-robin, or a third-party load balancer.
* Microsoft Network Load Balancing can still be used for Windows Server 2008 Terminal Servers although it is not necessary
Scoping the Issue: There are several common issues that we see with Terminal Server Load Balancing, and scoping the issue will depend on the symptoms that you are experiencing:
Data Gathering: In all instances, collecting either MPS Reports with the General, Internet and Networking, Business Networks and Server Components diagnostics, or a Performance-oriented MSDT manifest must be done. Additional data required may include the following:
Troubleshooting / Resolution: Troubleshooting will depend on which problem you are experiencing:
Event ID 1019, 1016 or 1001
Users are not being re-vectored to a disconnected session in the farm and instead receive a new session on a different server
Users are not load balanced evenly across servers in the farm
Thanks for the overview! I have some same problems for KB955365 but for Windows Server 2008R2 :( Do you know if there is a Hotfix for this issue?