Best Practices for Load Balancing Windows Terminal Server

CB,

 

 

This is fantastic! Thank you very much for pointing me in the right direction.

 

 

I've implemented the setup as specified in the document, but I'm still wondering if the Load Balancing mechanism specified (Least Connections (node)) is the best one (the document acknowledges that "different load balancing methods may yield optimal results for a particular network"). My concern is that if by the luck of the draw, more of the heavy resource users are connected to one Terminal Server, they'll serve to drag that server down, while other servers operate with relatively light loads. This is a very real thing in my organization - we've had to manually load balance heavy users by identifying them and asking them to use specific Terminal Servers, so that they don't all end up on the same server.

 

 

This concern is what is leading me in the direction of load balancing based upon real-time server metrics like Active Sessions, CPU, and Memory. Am I overanalyzing this, or is this a valid approach to load balancing the Terminal Servers?

 

 

Thanks again for your help!

 

 

Mark