Skip to main content
All CollectionsIntegrationsClientless RDP
How to start with Clientless RDP
How to start with Clientless RDP
Updated over 3 months ago

Introduction

In this article, we explain what Clientless RDP is, how it works, and what you need to get started with Clientless RDP.

Prerequisites

  • Users must have the Hybrid module to use CRDP apps.

  • The RDS server(s) must be connected to an Active Directory, CRDP does not work with standalone servers.

  • To configure CRDP in your environment, a CRDP gateway is required.

    • As a partner or direct customer of Workspace 365, contact Support (trough the support widget on the partner portal) for the possibilities to get a CRDP gateway if you don’t have one yet.

    • If you have purchased Workspace 365 via one of our partners or resellers, contact your Workspace supplier. They may already have a CRDP gateway and if not, the partner will have to contact us to request one.

What is Clientless RDP?

With Clientless RDP (or CRDP), remote applications can be accessed without having to install a client, logging in or searching for the right application within the remote desktop. It’s possible to create Clientless RDP applications for either remote desktop environments or specific remote applications, making it a good solution for companies that still use legacy applications but want to use the full potential of Workspace 365 as an adaptive digital workplace.

How does Clientless RDP work?

Clientless RDP works via a Clientless RDP gateway; a Linux server hosting our CRDP solution, which is based on the guacamole software. CRDP gateways are available for our partners and direct customers.

As a partner, this gateway works for your entire instance; for each customer/environment that wants to use CRDP, you create a service account to make the connection between the workspace and the CRDP gateway. After setting this up, you can configure CRDP apps in the workspace using information from RDP files retrieved from your RD web environment. Users can then access the app using their integration credentials to login to the remote server. This is why the remote server must be connected to an Active Directory.

The full technical setup is explained step by step in the documentation linked below.

Configuration

Follow the steps below to configure Clientless RDP for your legacy applications:

Did this answer your question?