I need help now customers
- Download and open the app for your device (below). Windows: just run it, no install needed.
- Read the ID and one-time password shown in the app to the InnSys technician.
- Click Accept when the connection request appears. Close the app to end the session.
Nobody can connect to your computer without the password shown on your screen, and you can disconnect at any time.
Staff: set up a device for unattended access staff
One command installs the client, points it at remote.innsys.ca, and sets a permanent password.
Windows (run PowerShell as Administrator)
& ([scriptblock]::Create((irm https://remote.innsys.ca/install.ps1))) -Password 'YourStrongPassword'
Linux (Debian/Ubuntu/RHEL/Fedora)
curl -fsSL https://remote.innsys.ca/install.sh | sudo bash -s -- --password 'YourStrongPassword'
macOS
curl -fsSL https://remote.innsys.ca/install-macos.sh | bash -s -- --password 'YourStrongPassword'
Add --id 123456789 (or -Id on Windows) to choose the device ID. Omit --password for attended mode only. Use a different strong password per customer or site.
Staff console administrators
Admin console Web client (control from a browser)
- Users → add each technician (name, password, role). Administrators manage users and see every device; users see their own and shared address books.
- Devices → every computer installed with the staff scripts reports here (ID, hostname, user, OS, online status). Click to connect from the web client.
- Address books → shared lists of customer devices with tags; staff see them in the app after logging in (top-right in the app, same username and password as the console).
- Login log and audit trails show who connected when.
Self-registration is off. Only an administrator can create accounts.
Downloads RustDesk 1.4.9 · SHA-256 checksums
| Platform | Files | Notes |
|---|---|---|
| Windows 10/11 (x64) | Pre-configured EXE · EXE · MSI | Pre-configured EXE already knows our server. Run it directly for one-off support, or click Install inside it for permanent access. MSI is for Intune / GPO deployment. |
| Windows on ARM | Pre-configured EXE · EXE | Surface Pro X, Snapdragon laptops. |
| macOS | Apple Silicon · Intel | macOS asks for Screen Recording and Accessibility permission the first time. Enter the server settings below, or use the staff script. |
| Linux | .deb · .rpm · AppImage · .deb arm64 | Ubuntu, Debian, Mint, Fedora, RHEL, Rocky. X11 sessions are fully supported; Wayland needs a logged-in user. |
| Android | APK · Google Play | Can be controlled (screen share + input via Accessibility service) and can control other devices. Enter the server settings below once. |
| iPhone / iPad | App Store | Can control other devices (Apple does not allow iOS itself to be remote controlled). Enter the server settings below once. |
| Web browser | rustdesk.com/web | Control any device from a browser with nothing installed: open the settings (⚙) in the web client and enter the ID server and key below. |
Server settings (for manual setup)
In the app: Settings → Network → ID/Relay server. The API server is what makes the device show up in the admin console and lets staff log in inside the app.
| ID server | remote.innsys.ca |
| Relay server | remote.innsys.ca |
| API server | https://remote.innsys.ca |
| Key | WNTCip0kqOJqFujJzBJ99Oi9Q8e46iS7yBSDTjNycTY= |
Or import in one go
Copy this string, then in the app press Import server config (Settings → Network) — it reads the clipboard.
=0nI9kFVjlnTqRFRTJUe3MVa2QTZ4EVOp9UO5okQ6pka1ZUcK9UcrBDcpNEVOdlI6ISeltmIsISYj5yc5NnbulmLlR3btVmcv8iOzBHd0hmI6ISawFmIsISYj5yc5NnbulmLlR3btVmciojI5FGblJnIsISYj5yc5NnbulmLlR3btVmciojI0N3boJye
Why this is safer than ScreenConnect
- Our server, our keys. Nothing goes through a vendor cloud. The ID and relay servers run on InnSys hardware.
- End-to-end encrypted. Every session is encrypted between the two devices (NaCl/Curve25519). The relay only forwards ciphertext and cannot read screen or keystrokes.
- Server key pinning. Clients must present our public key; strangers cannot register on or relay through this server.
- Consent by default. Customers see a request and must accept it. Unattended access requires a password that staff set per device; enable 2FA in the app for extra protection.
- Direct where possible. Sessions connect peer-to-peer (UDP hole-punch) and fall back to the relay only when needed, so it is fast on LAN and WAN.
- Open source (AGPL) and auditable, with no license expiry or per-technician seat fees.
Staff quick reference
Connecting to a device
- Open the InnSys Remote app (or the web client). It should show Ready with a green dot; if it says Not ready, check Settings → Network shows our server.
- Type the device's 9-digit ID and press Connect, or pick it from the address book / Devices list after logging in.
- Attended: ask the customer for the one-time password, or wait for them to click Accept. Unattended: enter the permanent password you set.
- Toolbar: file transfer, clipboard, TCP tunnel, Ctrl-Alt-Del, switch monitor, record session, chat.
Address book / saving devices
Log in inside the app (top-right) with your console account. Shared Address Books and the Devices list come from the admin console and follow you to any computer or phone.
Changing or removing a device
On the device: Settings → Security → Set permanent password (change) or Uninstall from Windows Apps / apt remove rustdesk. To revoke everything for a customer, change the password on that device; a new key on the server would require reconfiguring every client.
Ports (if a customer firewall blocks the connection)
Outbound to remote.innsys.ca: TCP 21115–21119, UDP 21116, plus HTTPS 443 for downloads. Only outbound is required on the customer side.