RD Connection Broker redirection modes
RD Connection Broker can use either IP address redirection or routing token redirection to redirect a client to the Remote Desktop Session Host (RD Session Host) server where their session exists. When you configure RD Connection Broker settings in the Remote Desktop Session Host Configuration tool, you can choose the client redirection mode.
IP address redirection
By default, an RD Session Host server uses IP address redirection, where a client queries RD Connection Broker and is redirected to their existing session by using the IP address of the server where their session exists. To use this redirection method, client computers must be able to connect directly by IP address to RD Session Host servers in the farm. If clients can connect directly to the RD Session Host servers, we recommend that you accept the default behavior. For example, you must use IP address redirection if you use any of the following as your load-balancing solution:
- RD Connection Broker Load Balancing, using DNS round robin
- Network Load Balancing (NLB)
- A hardware load balancer that does not support RD Connection Broker routing tokens
RD Connection Broker routing token redirection
You can configure an RD Session Host server to use RD Connection Broker routing token redirection instead of IP address redirection. However, only use this mode when your network load-balancing solution supports the use of RD Connection Broker routing tokens.
If you configure an RD Session Host server to use RD Connection Broker routing tokens as the redirection method, the IP address of the RD Session Host server is not sent to the client. Instead, the IP address is embedded in a token. When a client reconnects to the load balancer, the routing token is used to redirect the client to their existing session on the correct RD Session Host server in the farm.
If you switch to token redirection mode, you can select only one IP address for reconnection. The address that you select must meet both of the following criteria:
- It must be the IP address of the network adapter that is connected to the load balancer.
- It must be the address that is configured on the load balancer as the IP address for the RD Session Host server.
Only select an IPv6 address if your load-balancing solution supports the use of IPv6.