TideDesk for organisations
An administrator can set how TideDesk behaves for every user of a computer. The settings live in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\TideDesk, where only an administrator can write, so the person at the computer cannot change them. TideDesk shows each one as Set by your organisation.
How to set them
Use whatever already manages your computers: Group Policy (a registry preference), Microsoft Intune or another device management tool, or a .reg file run as an administrator. TideDesk reads the settings again every few seconds, so no restart is needed.
The settings
| Value | Type | What it does |
|---|---|---|
Rendezvous | DWORD | 0: no connection service at all, so no device-ID connections over the internet. |
RendezvousServer | String | Use only this connection service, for example your own. |
RendezvousAllowed | Multi-string | Use only one of these connection services. |
LanDiscovery | DWORD | 0 or 1: whether the computer can be found by device ID on the local network. |
TypedAddresses | DWORD | 0 or 1: whether viewers may connect to typed addresses, not only device IDs. |
AccessCode | DWORD | 0 or 1: whether viewers may come in with the access code. |
SavedPassword | DWORD | 0 or 1: whether viewers may come in with the saved password. |
PortMapping | DWORD | 0 or 1: whether TideDesk may ask the router to open its port. |
AllowStopSharing | DWORD | 0 or 1: whether the person at the computer may stop sharing or quit TideDesk. |
Reports | DWORD | 0: problem reports can be copied, not sent anywhere. |
ReportServer | String | Problem reports go only to your own report service (host or host:port, port 47902 by default), never to TideDesk. |
ReportServerFingerprint | String | The SHA-256 of that service’s certificate, in hex. Without a valid one, reports are not sent at all. |
A value that is not set leaves the choice to the person at the computer. The report settings need v0.1.0-alpha.13 or later; the others, v0.1.0-alpha.12 or later.
An example
This .reg file keeps a company’s computers on its own connection service, lets viewers in only with the saved password, leaves the router alone and sends problem reports to the company’s own service:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\TideDesk]
"RendezvousServer"="rendezvous.example.com"
"AccessCode"=dword:00000000
"SavedPassword"=dword:00000001
"PortMapping"=dword:00000000
"ReportServer"="reports.example.com"
"ReportServerFingerprint"="the certificate's SHA-256, 64 hex digits"
Problem reports
TideDesk keeps the problems it runs into on the computer, under History, Problems, and sends a report only when the person presses the button after seeing all of it. By default reports go to TideDesk. With ReportServer and its fingerprint they go only to your own report service, and with Reports set to 0 they can only be copied. Either way, TideDesk’s support email is not offered. To run your own report service, write to [email protected].
Licences
TideDesk is free for personal, non-commercial use. Use in an organisation needs a TideDesk licence. A computer managed by an organisation (joined to a domain or to Microsoft Entra ID, or in device management) says so in the app. For licences, write to [email protected].
More guides
- Remote desktop without an account How device IDs and access codes work, and what the connection service sees.
- TideDesk vs AnyDesk, TeamViewer, RustDesk and VNC When TideDesk fits, and when another tool fits better.
- Remote access scams How they work, and what to do if you already let someone in.