load balance MSRDP traffic

sure. One of the few things available in the clear is the username or routing token for session mapping. If session directory is enabled, this presents as msts=.... where the value can be extracted into an IP:port. Without session directory, the user credentials are available as mstshash=...... If the clients are on controlled builds, you can force them (or request them) to use old, reallyold, or new as the username so you can balance accordingly. Here's an old thread that approaches this from the persistence angle, but could be modified to switch pools as necessary:

 

 

http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&postid=25271 Click here