Skip to main content

Remote Desktop for Windows: Connect with RustDesk

Updated yesterday

This article explains how Swif lets you remotely access Windows devices using RustDesk, alongside Splashtop. It also covers how status and actions work in the Remote Desktop dropdown and what you’ll see when connecting.

For Linux RustDesk details, see the changelog.

1. What changed?

On Windows devices:

  • The Remote Desktop button is now:

    • Always enabled (clickable) for Windows devices.

    • A dropdown where you can choose your remote desktop provider.

  • You can:

    • See both Splashtop and RustDesk options on supported Windows devices.

    • See whether each provider is Configured or Not Configured.

    • Either Connect or Configure from the same menu.

  • When you connect:

    • Swif calls the remote desktop backend.

    • You’ll see a screen with Connection ID and Password (no dynamic link yet), or a friendly error with a Retry button if details aren’t ready.

  • Admins also get download buttons for remote desktop controller apps (macOS, Windows, Linux).

2. Remote Desktop entry point on Windows

Where to find it

  1. Go to Devices in the WebApp.

  2. Open a Windows device.

  3. In the device details, locate the Remote Desktop area.

Behavior

  • The Remote Desktop call-to-action (CTA) is always enabled for Windows devices:

    • It does not get disabled even if no remote desktop policy is configured yet.

  • Clicking the CTA opens a dropdown with provider options.

3. Choosing a Remote Desktop provider

Provider list on Windows

On supported Windows devices, the dropdown shows:

  • Splashtop (Deprecated Soon)

  • RustDesk

Each row displays:

  • Provider name

  • Policy Status

    • Configured

    • Not Configured

  • Action

    • Connect (when configured)

    • Configure (when not configured)

Splashtop is clearly marked as “(Deprecated Soon)” to encourage migration to RustDesk.

4. Understanding “Configured” vs “Not Configured”

The status label and action are based on your team and device policy configuration.

When you see Not Configured

You’ll see Policy Status: Not Configured and a Configure action in these cases:

  1. No team-level remote desktop policy exists for that provider

    • Example: your team never set up any RustDesk or Splashtop policy.

    • The row appears grayed out with Not Configured.

  2. Team policy exists, but the device is not associated with it

    • The provider is set up at the team level, but this specific device has no assigned policy.

    • Clicking Configure will:

      • Take you to the policy creation page if a policy doesn’t exist, or

      • Open an assign policy flow if a policy exists but isn’t assigned, or

      • Prompt you to enable configuration if the policy exists but is disabled for this device.

  3. Device-level policy exists, but provider is disabled on this device

    • The policy is there, but enableSplashtop / enableRustdesk is set to false for that device.

    • The row shows Not Configured with a Configure button to enable it.

When you see Configured

  • Requirements:

    • A team and/or device-level policy exists for that provider, and

    • enableSplashtop / enableRustdesk is true for that device.

  • The row will show:

    • Policy Status: Configured

    • Action: Connect

Click Connect to start a remote session.

5. Connecting to a device (ID and password flow)

When you click Connect for a configured provider (Splashtop or RustDesk):

  1. Swif calls the remote desktop backend (e.g., remote-desktop/open) with:

    • Device ID

    • Provider type (Splashtop or RustDesk)

    • Other necessary metadata

  2. The WebApp then shows one of two outcomes:

A. Success – Connection details available

  • You see a Remote Desktop screen that includes:

    • Connection ID

    • Password

  • The layout follows the “Remote Desktop 1.1.0” design:

    • Clear labels for ID and password

    • No dynamic “click to connect” link yet (you use these credentials in the controller app).

  • Use these values inside your RustDesk or Splashtop controller to start the session.

B. Temporary failure – Details not available yet

If the backend returns an error or empty values (missing connectionId or password):

  • The UI shows a notice that connection details are not available.

  • A Retry button is displayed.

  • No partial or broken credentials are shown.

Clicking Retry:

  • Triggers a new call to the remote desktop API.

  • If the next call succeeds, the screen switches to the success layout and shows a valid ID and password.

6. Slow provisioning and the Refresh layout

Sometimes, the remote desktop connection may take a bit of time to become available.

In that case:

  • Instead of just using a tooltip, Swif shows a dedicated status screen (design “Remote Desktop 1.0.1”).

  • The screen:

    • Explains that the connection may take time to be ready.

    • Includes a Refresh CTA.

  • Clicking Refresh re-checks the backend for updated connection information.

7. Tooltip behavior

The Remote Desktop tooltip has been updated to be more helpful:

  • New message:
    ​“Choose a Remote Desktop provider to connect to this device”

  • Focus is on how to resolve (what action to take), rather than blocking the user.

  • This tooltip appears where Remote Desktop is available and follows the “1.0.2” design.

8. OS behavior & consistency

While this article focuses on Windows & RustDesk:

  • The overall behavior is consistent across OS types:

    • Configured → Connect button

    • Not Configured → Configure button

  • On some Windows devices, you may see only Splashtop (with the “Deprecated Soon” label) depending on rollout or policy state.

  • Visual styling of Remote Desktop is aligned across macOS, Windows, and Linux to avoid surprises for admins managing mixed fleets.

9. Downloading Remote Desktop controllers (admins)

Team admins can download controller apps directly from Swif:

  • Available controller platforms:

    • macOS

    • Windows

    • Linux

  • Each button:

    • Download the correct installer for that OS.

    • Uses OS-appropriate file names and formats.

Visibility:

  • Download buttons are scoped to admins according to product rules:

    • Admins: see and can use the download buttons.

    • Non-admins: may not see these options, or see them disabled, depending on configuration.

10. Troubleshooting

If Remote Desktop isn’t working as expected on a Windows device:

  • Remote Desktop dropdown is empty or missing a provider

    • Confirm a team-level policy exists for that provider.

    • Ensure the device is assigned to that policy.

  • Status always shows “Not Configured”

    • Check that enableSplashtop / enableRustdesk is set to true.

    • Verify the device is correctly associated with your remote desktop policy.

  • No ID/password after clicking Connect

    • Wait a moment and use Retry.

    • If it still fails, confirm that:

      • The Remote Desktop agent is running on the device.

      • The device has an active internet connection.

Related Articles
Introduction to Remote Desktop Feature
How to Run the Splashtop Windows Viewer Client on Linux
Windows Microsoft Remote Desktop Policy
Windows Remote Desktop (Splashtop) Policy
Apple Remote Desktop (Splashtop) Policy
Did this answer your question?