--- title: "Private Cloud (Unmanaged) RD Gateways" slug: "remote-desktop-gateway-rdg-configuration-and-workspot-integration-guide" updated: 2026-05-21T00:07:15Z published: 2026-05-21T00:07:15Z canonical: "docs.workspot.com/remote-desktop-gateway-rdg-configuration-and-workspot-integration-guide" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.workspot.com/llms.txt > Use this file to discover all available pages before exploring further. # Private Cloud (Unmanaged) RD Gateways > **Note:** This document is for using standard Microsoft Remote Desktop Gateways with your Workspot deployment. This is recommended in deployments where [Workspot Managed Gateways](/v1/docs/managed-gateways-gateway-clusters) 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)](/v1/docs/managed-gateways-gateway-clusters) 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: 1. Sign into Workspot Control as a full Administrator. 2. Go to “Setup > Gateways > Private Cloud Gateways.” ![Control panel showing setup options for gateways in a cloud management interface.](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/unmanaged-gw-1.png?sv=2026-02-06&spr=https&st=2026-10-12T12%3A58%3A24Z&se=2026-10-12T13%3A58%3A24Z&sr=c&sp=r&sig=9MrZn3NIIiazEUbNldk6T8T7DqTg3zVSBgQ1VOW2n3M%3D) 1. 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.) ![Form to add a private cloud gateway with fields for name, URI, and authentication type.](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/unmanaged-gw-2.png?sv=2026-02-06&spr=https&st=2026-10-12T12%3A58%3A24Z&se=2026-10-12T13%3A58%3A24Z&sr=c&sp=r&sig=9MrZn3NIIiazEUbNldk6T8T7DqTg3zVSBgQ1VOW2n3M%3D) 1. Click “Add Private Gateway.” The message "RD Gateway created successfully" is shown. ![Private Cloud Gateway created successfully, displaying gateway details and options.](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/unmanaged-gw-3.png?sv=2026-02-06&spr=https&st=2026-10-12T12%3A58%3A24Z&se=2026-10-12T13%3A58%3A24Z&sr=c&sp=r&sig=9MrZn3NIIiazEUbNldk6T8T7DqTg3zVSBgQ1VOW2n3M%3D) ## Specifying the Gateway in Workspot Pools and Applications You can specify Gateway on the “Add” and “Edit” pages for Desktop Pools and Cloud Applications. ![Settings for routing through gateways, highlighting options for gateway types and selection.](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/unmanaged-gw-4.png?sv=2026-02-06&spr=https&st=2026-10-12T12%3A58%3A24Z&se=2026-10-12T13%3A58%3A24Z&sr=c&sp=r&sig=9MrZn3NIIiazEUbNldk6T8T7DqTg3zVSBgQ1VOW2n3M%3D) - 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](/v1/docs/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. ![](https://cdn.us.document360.io/ad9153e1-c8de-4f56-94f2-b717a1fc3a68/Images/Documentation/image-1761785643794.png?sv=2026-02-06&spr=https&st=2026-10-12T12%3A58%3A24Z&se=2026-10-12T13%3A58%3A24Z&sr=c&sp=r&sig=9MrZn3NIIiazEUbNldk6T8T7DqTg3zVSBgQ1VOW2n3M%3D) - 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 - [Control: Desktop Pools](/v1/docs/control-desktop-pools) - [Workspot Application Server Pools (Cloud App Pools)](/v1/docs/workspot-application-server-pools-cloud-app-pools) - [Managed Gateways (Gateway Clusters)](/v1/docs/managed-gateways-gateway-clusters) #### External Document - [Deploy the Remote Desktop Gateway role](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remote-desktop-gateway-role)