Devolutions Gateway configuration with Devolutions Server

This topic describes how to configure Devolutions Server to connect with Devolutions Gateway. There are two ways to install a Devolutions Gateway: the Side-by-side Installation and the Standalone Installation.

Steps for Side-by-side Installation

This method supports more sessions if there is an available Devolutions Gateway license(s). This installation process is the easier of the two. However, this method is recommended for simpler network layouts, and only one Side-by-side installation can be done per machine.

1. From the Devolutions Server Console, click on the Companions tab.
   

   

2. In the Devolutions Gateway section, click on Install.
3. Choose Side-by-side Installation.

   

4. If default values don't work for your environment, enter the desired settings.
   1. HTTP Listener: HTTP(s) port to reach the Gateway. (7171 is default)
   2. TCP Listener: port used for the RDP sessions. (8181 is default)
5. Click Ok.
   

   

6. Go to the Devolutions Server web interface, connect with an administrator account.
7. Go to Administration – Devolutions Gateway.
   

   

8. Click on the Ping button for the desired gateway in the list to see if a connection can successfully be made. If the page was already open, refresh it first.
   

   

Steps for Standalone Installation

Installing by using the Standalone method will allow to install Devolutions Gateway on a separate server than Devolutions Server. It could be for performance purposes or access networks that Devolutions Server can't access. Many Devolutions Gateway can be used by Devolutions Server, but only one Devolutions Gateway can be installed on a machine.

1. From the Devolutions Server Console, click on the Companions tab.
   

   

2. In the Devolutions Gateway section, click on Install.
3. Choose Standalone Installation.
   

   

4. Choose between Download version & Install from msi file.

5. Click Next.
   

   

6. Enter the Access URI information, for example https://gateway.example.com.
7. Choose the Devolutions Gateway Listeners ports (by default they are 7171 and 8181).
   1. If HTTPS is chosen instead of HTTP in the step above, the Certificate Configuration will be needed.
   2. Certificate file: Needs to be a full chain certificate (.pfx, .p12, .pem, .crt).
   3. Certificate password: Only needed if a .pfx or .p12 certificate was used.
   4. Private key file: Only needed if a .pem or .crt was used as a certificate.

8. Click Next.
   

   

9. Choose between:
   • Use public key from DVLS instance 'Devolutions Server': this option is used if the installed Devolutions Gateway is on the same server as the Devolutions Server;
   • From file: If installing Devolutions Gateway on another computer, download the public key from the Devolutions Server you want to pair with that Devolutions Gateway. It is located under Administration – Devolutions Gateway.
     

     

10. Click Next.
    

    

11. Click Install.
    

    

12. Click Close.
    

    

13. On the Devolutions Server web interface, connect with an administrator account.
14. Go to Administration – Devolutions Gateway.
    

    

15. Click on the Add button on the top right corner.
    

    

16. Enter the following information.
    1. Name: Name of the gateway that will be displayed in Remote Desktop Manager.
    2. Description: Description of the gateway.
    3. Set as default: If enabled, this gateway will be selected by default when configuring Remote Desktop Manager.
    4. Devolutions Gateway URL: The Devolutions Server URL that the gateway will connect to.
    5. TCP Listening Port: Set the port with the same TCP port value configured in the console.
17. Click on Save.
    

    

The gateway should now be visible in the list. It is possible to verify the status of the gateway with the Ping button.