Load Balancing Configuration for Thinfinity VirtualUI

Important: This article is closely linked with other 4 articles. You should check this post to see the full picture.
Right after you installed the Gateway and the broker using the previous guide, you need to work out the configuration.
To guarantee that the load balancing configuration will perform properly, the main configuration items we have to look at are:

  • The Network ID.
  • IP Bindings (in the Gateway Manager).
  • The Gateway URL (in the Broker Server).

Set up the the Network ID
The ‘Network ID’ must be the same across all gateway(s) and broker(s) components. You can modify the Network ID to any value, it doesn’t follow a specific format.
In the Gateway Manager we will find two different tabs: General and Internal Broker Server. In the General tab, we will configure the port and bindings for the user’s (browser client) to reach Thinfinity VirtualUI. For instance ‘https://Server_IP:6580’ based on the settings below:
Load Balancing Configuration for Thinfinity VirtualUI
IP Bindings
The Gateway and Broker components communicate over a different port. This is configured in the Internal Broker Server tab:
Load Balancing Configuration for Thinfinity VirtualUI
By default, the IP Binding will be ‘’. When working with load balancing you should set the IP Binding to ‘All unassigned’ or select the internal IP of the server. Otherwise, the Broker Server won’t be able to reach the Gateway Server.
We strongly recommend adding all the Broker Servers IP addresses in the ‘Authorized IP Addresses’ box.
The Gateway URL (in the Broker Server)
Open the Thinfinity VirtualUI Server Manager, and you’ll be prompted to activate a License, for the moment just press “Cancel”:
Load Balancing Configuration for Thinfinity VirtualUI
Now that the Gateway is configured all we need to do is add the Gateway URLs in the Broker Server Manager.
Load Balancing Configuration for Thinfinity VirtualUI
As explained before, you will have to add the URL referencing the port in the Internal Broker Server tab. Keep in mind the communication between the Gateway Server and Broker Server is not encrypted, so you have to use ‘HTTP’ in the URL (e.g.
It is important to mention that when you have one server acting as gateway and broker, Thinfinity Remote Desktop Server will automatically set the right localhost address. Do not modify this setting and do not add a second URL referencing this server.
To verify if the Broker Servers are connected to the Gateway Servers you can check the log file ‘Thinfinity.VirtualUI.Server.log’ located in:
‘C:\ProgramData\Cybele Software\Thinfinity\VirtualUI’
It should say something like:

    2017-11-14 17:22:56 Connecting to
    2017-11-14 17:22:56 Registered on

There are a few things to take into account when using load balancing:

  1. All the Broker Servers have to share the same profiles. To do so, you can copy the database file ‘profiles.bin’ and distribute it in all the servers, you will find this in:
      C:\ProgramData\Cybele Software\Thinfinity\VirtualUI\DB
  2. You can also share the database path so all the Broker Servers read the same database:Load Balancing Configuration for Thinfinity VirtualUI
  3. If you are using One Time URL, you must share the ‘Root Path’ for Temporary Folders. This will also ensure the users have consistency with their intermediate disk (ThinDisk) when they access to files from the file manager or upload/download files:Load Balancing Configuration for Thinfinity VirtualUI

Finally, you must share the license between the Broker Servers. In order to do this, we must install the License Server Manager on one of our servers.
Your next step would be: Pool your VMs and add Windows instances on-demand
IMPORTANT: This article is closely liked with other articles:

Have any questions? Contact us at [email protected] or leave a message on this same post.

Related Posts

Leave a comment