Remode Desktop not Load Balancing Round Robin

Hi Neeraj, thanks a lot for the update! As far as I understand, the mstshash cookie primarily helps to maintain persistency. So if you apply a msrdp persistence profile, the value of the mstshash cookie should be taken into account to select the poolmember. With this setting I would expect changed output when dumping the persistence table. The UserName provided by the cookie will hopefully show up as persistence key. Regarding the load balancing algorithm: When testing it a couple of weeks on customer site I observed a very similar effect. I assume, the session directory sends a kind of redirect to the mstsc client and due to the one-armed deployment the client connects directly to the target server. The question for me is about kind of load balancing and persistence algorithm on Microsoft side. To figure this out it would be necessary to monitor the connection distribution to the terminal servers as well. One more aspect on the load balancing method on the F5. The deployment guide recommends to use "least connections". In a one-armed deployment (as described above) the client seems to establish a direct connection to the terminal server and bypasses the load balancer. So the load balancer is not able to count current connections per pool member and "least connection" will simply result in always picking the first pool member in the list. That´s why I believe "round robin" fits better for a setup like this. In the next couple of weeks I will probably continue to work with my client on this subject and I will keep you posted. Thanks again, Stephan