Physical Managed Gateways are Workspot RD Gateways running on a bare-metal Windows Server device. They must be configured manually but after that operate as Workspot Managed Gateways, which means they are managed and monitored by Workspot Control and can be arranged in clusters for increased scalability and uptime.
This document covered features specific to Physical Managed Gateways. See Managed Gateways (Gateway Clusters) for general information.
Physical Gateways are listed in their own section in Workspot Control under “Setup > Gateways > Physical Gateway Clusters.” When the section is expanded it shows the same columns as Public Cloud Gateway Clusters.
Requirements
A dedicated bare-metal server running Windows Server 2019 or 2022.
Remote Desktop Services and RD Gateway roles installed.
This is a selective feature introduced in Workspot Control 18.5. Contact Workspot to have it enabled.
A valid DNS entry for the Gateway Server.
A valid certificate for the Gateway Server.
Limitations
Entra ID (Azure AD) Client authentication only. (Active Directory desktop/app authentication issupported.)
Currently not supported on VMs.
Imaging the Gateway from Control is not currently supported
Rebooting the Gateway from Control is not currently supported.
Certificate installation from Control is not currently supported.
Installation
Installing the Gateway Server
Create your Gateway device using Windows Server 2019 or 2022.
Install Remote Desktop Gateway Services.
Restart the device.
Upload valid certificates on Remote Desktop Gateway Manager.
If you are creating a multi-Gateway cluster, repeat for the other servers.
Declaring the Gateway Cluster in Control
Sign into Workspot Control.
Go to “Setup > Gateways > Physical Gateway Clusters” and click the “Create Physical Gateway Cluster” button. The “New Gateway Cluster” screen appears.
Fill in the Region and Cluster Name.
(Optional) Add a description for the Cluster.
Select Authentication Type used for Client authentication (currently, only “Azure Active Directory” (Entra ID) is supported
Add Region, Name and Description for the Gateway Cluster.
Authentication mode will default to “Azure Active Directory,” Which as of Control 18.5 is the only supported mode.
Select a Gateway Policy under “Default Authorization Policy.” This is usually “Default Gateway Policy.”
Press “Create.” The Gateway Cluster record will be created in Control with a status of “Preview.”
Declaring Individual Gateway Servers in Control
“Setup > Gateways > Physical Gateways,” press the “Add Gateway” button under the entry for the Gateway Cluster you just declared.
Add the hostname, URI, and MAC address for the Gateway Server. It will be shown on the list of Gateways as being in “Setup” mode.
Repeat for any additional Gateway Servers in the Cluster.
Press the “Agent Token” button under the Cluster and copy the Agent Token for use in registering the Workspot Gateway Agent on the Gateway devices.
Installing the Gateway Agent
Sign into the Gateway device.
Download the Workspot Gateway Agent Installer from https://download.workspot.com.
At the time of this writing, the newest version is Workspot_Gateway_Agent_onprem_Installer_v2.4.0.ps1.
Run the following command from the directory to which you downloaded the installer:
.\gateway_agent_installer_v2.4.0.ps1 [-token agent_token] [-companyIdentifier company_identifier] [-skipHardening]
Where
agent_token is the Agent Token you got from Control in the previous section.
company_identifier is your Company Identifier (shown in Control on “Setup > Configuration”).
-skipHardening disables some services that may interfere with Agent installation and operation.
After the script runs successfully, the Gateway registers itself with Control and is set to Ready status.
Change the state to “Enabled” from the Actions menu.
This will enable normal Gateway operation.
It will also cause the Agent to search for its DNS hostname. It should have a valid DNS record.
Repeat for any other Servers in the Cluster.
Assign the Gateway Clusters to desktop and application pools in the “Add Pool” or “Edit Pool” page under “Resources > Cloud Desktop Pools” or “Resources > Cloud App Pools.”