Rdp user has not to go to the next server HAPROXY

Help!
1

Hello everyone
We will be happy to receive your help

We have several servers with a login limit of 10 users, the 11th user has to move to the next server in today’s mode it doesn’t work
Attach the code

global
log 127.0.0.1 local0
log 127.0.0.1 local1 notice
pidfile /var/run/haproxy.pid
maxconn 4096
user haproxy
group haproxy
daemon
stats socket /var/run/haproxy.stat mode 600

defaults
log global
mode tcp
option tcplog
option dontlognull
retries 3
option redispatch
maxconn 3000
timeout http-request 10s
timeout queue 5s
timeout connect 4s
timeout client 3h
timeout server 3h
timeout http-keep-alive 10s
timeout check 10s

userlist UsersFor_HAProxyStatistics
group admin users haproxy
user haproxy insecure-password pAssW0rd
user stats insecure-password letmein

listen stats *:1936
mode http
stats enable
#stats scope http
#stats scope www
#stats scope static
#stats scope static_httpclose
#stats realm Haproxy\ Statistics
stats uri /haproxy?stats
#stats auth haproxy:HA@VmView5
stats refresh 20s
stats show-node
stats show-legends
acl AuthOkay_ReadOnly http_auth(UsersFor_HAProxyStatistics)
acl AuthOkay_Admin http_auth_group(UsersFor_HAProxyStatistics) admin
stats http-request auth realm HAProxy-Statistics unless AuthOkay_ReadOnly
stats admin if AuthOkay_Admin

frontend inbound-rdp
bind :3389
mode tcp
default_backend view_rdp

backend view_https
mode tcp
option tcplog
option ssl-hello-chk #make sure we can talk SSL, not just TCP
balance source

backend view_rdp
mode tcp
option tcplog
balance roundrobin
stick-table type ip size 200k expire 4h
stick on src

server 16Ts112 192.168.201.112:3389 check maxconn 10
server 16Ts111 192.168.201.111:3389 check maxconn 10
server 16Ts110 192.168.201.110:3389 check maxconn 10
server 16Ts99 192.168.201.99:3389 check maxconn 10
server 16Ts98 192.168.201.98:3389 check maxconn 10
server 16Ts97 192.168.201.97:3389 check maxconn 10
server 16Ts96 192.168.201.96:3389 check maxconn 10
server 16Ts95 192.168.201.95:3389 check maxconn 10
server 16Ts94 192.168.201.94:3389 check maxconn 10
2

balance roundrobin
Requests are routed sequentially to each server in the pool until the cycle repeats itself. This is a Eeny, meeny, miny, moe type of balancing. First user goes to first server, second user to second server, etc. When the first server reaches the 10th user, all other servers will have 9 users.

What you want is first.

balance first
The first server with available connection slots receives the connection. The servers are chosen from the lowest numeric identifier to the highest (see server parameter “id”), which defaults to the server’s position in the farm. Once a server reaches its maxconn value, the next server is used. It does not make sense to use this algorithm without setting maxconn.

The purpose of this algorithm is to always use the smallest number of servers so that extra servers can be powered off during non-intensive hours.