Note: This document is for using standard Microsoft Remote Desktop Gateways with your Workspot deployment. This is recommended in deployments where Workspot Managed Gateways are not supported.
RD Gateways allow your Workspot Client users (end-users) to reach their Workspot desktops and applications. While Workspot recommends the use of Workspot Managed Gateways (Public Cloud Gateways) wherever possible, standard Microsoft RD Gateways are also supported.
Nomenclature
Workspot uses two names for these Gateways: “Private Cloud Gateways” and “Unmanaged Gateways.”
They are called “Unmanaged” Gateways because they are not managed by Workspot Control. Obviously, someone has to manage them.
They are called “Private Cloud Gateways” because deployments with public Cloud providers such as Microsoft Azure and Google GCP usually use our Public Cloud/Managed Gateways instead.
In fact, they are standard Microsoft RD Gateways that you manage according to your normal standards.
Prerequisites
A Microsoft Server instance running Remote Gateway Services, either standalone or in high-availability mode.
RDS Host(s) with applicable licenses and applications installed. That is, Windows desktops and servers running the Workspot Desktop Agent.
(Optional) A Remote Desktop Services (RDS) implementation: RDS Farm with one RDS Broker (or more for high availability).
Creating the RD Gateway
Because the Gateway itself is a standard Microsoft RD Gateway, see the Microsoft documentation for creating it.
Creating an RD Gateway Profile in Workspot Control
Follow these steps:
Sign into Workspot Control as a full Administrator.
Go to “Setup > Gateways > Private Cloud Gateways.”

Click “Add Private Gateway” and fill in the popup form with the Gateway’s Name, URI, Authentication Type (Active Directory or Entra ID), and whether you allow Self-Signed Certificates (definitely “No” for production.)

Click “Add Private Gateway.” The message "RD Gateway created successfully" is shown.

Specifying the Gateway in Workspot Pools and Applications
You can specify Gateway on the “Add” and “Edit” pages for Desktop Pools and Cloud Applications.

Set the “Route through Gateway” to “Always” unless you have both remote and on-premises Client users and have set up local “beacons” so the Clients can tell whether they are running locally or remote. (In that case, see Location Detector.)
Set “Gateway Type” to “Private Cloud Gateway.”
Set “Gateway” to the Gateway you just declared.
If you have set up multiple Gateways for the same network, select all the interchangeable Gateways.
Troubleshooting
Verify transport settings using the RD Gateway manager.

Verify proper RD Gateway deployment by assigning a desktop or Cloud Application that uses the gateway to a Client user and then connecting with the Client.
If this doesn’t work, note the error message provided by the Client, the Control Events, and the connection trace in Workspot Watch.
Related Documents
Workspot Articles
External Documents
Configuring the RD Gateway Server for a 2012 RDS farm with HA enabled for the RD Connection Brokers
Configuring UDP Support on the RD Gateway in Windows Server 2012
Specify Computers That Users Can Connect to Through Remote Desktop Gateway
