Avoid the single point of failure on your architecture

thinfinity remote desktop

Table of contents

Check this Thinfinity Remote Desktop hint and apply the High-Availability feature to avoid the single point of failure on your Remote Access/Cloud Computing architecture.

Contact us to get the installer License Server Administrator link.

In order to use the High-Availability feature, you’ll need to install the License Server Administrator on two different servers. It isn’t required for both License Servers to be on the same network. If they aren’t you’ll need to ensure the License Server Administrator port is open (by default it’s 7443).

One of the servers will act as the Primary license server and the other as the Backup. You configure each role in the ‘Communications’ tab of the License Server Administrator manager.

Primary Server:

The configuration for this is pretty simple. You just need to select the ‘Server role’ to ‘Primary’:

How to avoid single point of failure

Backup Server:

In the ‘Communication’ tab, change ‘Server role’ to ‘Backup’. The next step would be entering the ‘Primary server URL’ and linking this to the Backup Server address.

How to avoid single point of failure

Bear in mind it isn’t required to have a public address. If everything runs locally you can just enter the local IP address in the URL.

Finally, you have to configure the Thinfinity Remote Desktop server to load the license from a License Server. In order to do so, you just need to configure both License Server URLs in its manager.
If this is the first time you install Thinfintiy Remote Desktop Server on a server, you will be prompted to register the license right after you start the manager. Select ‘Activate a Serial Number online’ and click next.

In the following screen you’ll have to fill the E-mail, Serial, and both License Server URLs, Primary and Backup:

Remote Desktop configuration

If Thinfinity Remote Desktop Server is already licensed, just go to the ‘Licenses’ tab, enable ‘Use Licensing Server’ and fill in the Licensing Servers URLs.

How to avoid single point of failure

Once you configure this and apply the changes you might need to restart the services.

Bear in mind also that if you have multiple Thinfintiy Remote Desktop Servers connecting to a license server, you must configure the same “Network ID” on each of them. You will find this option in the ‘General’ tab:

How to avoid having a unique point of failure

The ‘Network ID’ doesn’t have to follow any special format, you can put anything in there, for instance, “test”.

Have any questions?

Book a call today to learn more about how Thinfinity® can help your organization. We are always available to guide you and provide the best solution based on your specific needs.

Add Comment

Thinfinity_logo

Get a Demo

Experience how Universal ZTNA with Thinfinity® integrates with VDI and DaaS for unmatched security and flexibility.

Table of contents

Blogs you might be interested in

<span>High Availability (HA)</span>, <span>IT Admin</span>, <span>IT Security</span>, <span>Load Balancing</span>, <span>Network Security</span>, <span>Secure Remote Access</span>, <span>Single Point of Failure</span>, <span>Thinfinity Workspace</span>