Migration · Updated May 2026

From RustDesk to WinDesk

Swiss hosting instead of US/SG public servers, signed builds, hardware-bound tokens, DPA out of the box — and a contract partner with a Swiss VAT invoice. Here's what the switch looks like.

Why switch at all?

RustDesk is a technically strong project. Three reasons evaluators typically give us:

  • Public server compliance hurdle. The free rendezvous servers rs-ny and rs-sg run in US/SG jurisdiction. For Swiss law firms, fiduciaries, medical practices, insurance carriers or data processors whose customers require GDPR-compliant EU/CH residency, this is a no-go.
  • Server operation wastes time. Self-hosting on Hetzner CX22 plus 2–3 hours of admin time per month (updates, TLS cert renewal, backup, monitoring) is realistic. For MSPs with 5+ technicians, switching to managed service often pays off after 6 months.
  • Signing gap. RustDesk builds are not EV-signed — end customers see SmartScreen warnings, Mac customers see Gatekeeper dialogs. WinDesk delivers EV-signed Windows builds and Apple-notarised macOS builds.

Step by step

01

Open a Pro account

Create a Pro account at app.windesk.ch/register. 14-day free trial without credit card. Swiss legal entity, Swiss VAT invoice.

02

Export the address book from RustDesk Server

From RustDesk Pro web console or self-hosted server: Address Book → JSON export. Concierge onboarding (CHF 490) handles the import including groups and tags.

03

Install WinDesk Host alongside RustDesk

Install WinDesk on target devices next to RustDesk. Both daemons reserve different ports and do not interfere. Cross-platform: Windows + macOS + Linux + Raspberry Pi 4/5 (arm64).

04

Pilot phase 2–4 weeks

Gradually move sessions to WinDesk. RustDesk stays active as a fallback. Test reliability, feature parity and audit trail on your real use cases.

05

Cutover

Cancel RustDesk Pro subscription or shut down the self-hosted server. WinDesk audit trail takes over seamlessly. Host software can remain on devices or be removed via MDM.

What changes in practice

  • Server configuration on endpoints — gone. Endpoint is distributed via the account.
  • Address book sync — runs account-centric, not per technician machine.
  • Device identities — regenerated during host installation (hardware-bound). Address book entries are preserved via concierge import.
  • Audit trail — out of the box in the Pro account, no self-hosted logging setup required.
  • Updates — automatic via signed Velopack update, not manual per host.
  • Support escalation — to Lightnet Multimedia GmbH (Switzerland), not to GitHub issues.

Frequently asked questions

Where is WinDesk clearly better than RustDesk?

Swiss hosting (instead of US/SG public servers), EV-signed Windows builds, Apple-notarised macOS builds, hardware-bound tokens via Secure Enclave / TPM, DPA template per GDPR Art. 28, Swiss VAT invoice, dedicated Swiss support. Details on the alternative page.

Where does RustDesk retain the advantage?

Open source with full auditability, self-hosting for air-gapped networks, full code control. If these factors are mandatory: RustDesk remains a good choice.

How long does the migration take?

2–4 weeks of parallel operation for a typical MSP or SME setup. Concierge onboarding shortens preparation to 1 week.

Are RustDesk device IDs migrated?

No. WinDesk device identities are hardware-bound (Secure Enclave / TPM) and are regenerated during host installation. Address book entries (name, group, tags) are imported via concierge onboarding; ID strings themselves are not portable for security reasons.

Can RustDesk and WinDesk run side by side on the same host?

Yes. Both reserve different network ports and service identities. We recommend this explicitly for the pilot phase — you have a fallback at all times and can measure reliability on real use cases, not synthetic tests.

What happens to the RustDesk licence after cutover?

RustDesk Pro subscriptions are usually monthly-cancellable. Self-hosted licences: check your EULA. We recommend cancelling the RustDesk subscription only after 1–2 weeks of successful WinDesk production, not immediately after cutover.

We run a RustDesk self-hosted server — what happens to it?

You can shut it down or keep it running as backup. WinDesk does not require self-operated infrastructure. If you shut down the Hetzner server: do not forget to switch the device configurations (or just install WinDesk Host alongside, then this is automatic).

Pitfalls I should know about before cutover?

Three common ones: (1) Firewall rules: WinDesk host needs its own UDP/TCP reservation, check your endpoint firewalls. (2) MDM distribution: signed MSI/PKG installers are available — use them, not the setup wizard for 100 devices. (3) Address book sync: WinDesk Pro uses the account as source-of-truth, not local lists per technician. Old RustDesk configurations should be cleaned up after cutover.