AnyDesk ID and Alias

service conf config safe show the ID, get getting hacked by ID

ID & Alias

Each AnyDesk has a unique numerical ID to identify in the AnyDesk network. A readable Alias can be assigned to that ID. Both represent an address to the device.

Note: An Alias is structured by name and namespace: name@namespace" E.g. computer@ad. The public namespace is "@ad" referring to AnyDesk. All Users with free license have to use this namespace. Free Users with AnyDesk portable (not installed), only have an ID. No Alias can be assigned.

The allowed characters are: numbers 0-9, letters a-z, A-Z, and symbols: minus(-), dot(.), and underscore(_). All other characters are forbidden and regarded invalid.

Assign or Change the Alias

Users with free-license set the Alias once. The Alias will be bound to the corresponding ID and cannot be altered or reassigned. Professional and Enterprise Users with individual namespace (you@yourcompany) can change or reassign the Alias for all clients on [my.anydesk.com].

Back-Up

The ID & and Alias are your identity in the AnyDesk network. To backup your identity, save the config file service.conf in a secure location. This enables you to retrieve your ID in case your devices crashes or your Operating System is reinstalled.

Windows 7/Server 2008 R2 and newer Portable: %appdata%\AnyDesk
Installed: %programdata%\AnyDesk
Windows XP/Server 2003 Portable: %appdata%\AnyDesk
Installed: %AllUsersProfile%\AnyDesk
macOS local user: ~/.anydesk/service.conf
service (default): /etc/anydesk/service.conf
Linux local user: ~/.anydesk/service.conf
service (default): /etc/anydesk/service.conf
Note: To backup your settings and recent connections, you need to backup the whole directory %appdata%\AnyDesk on Windows.

service.conf

Warning: If the config files get lost by any means, the ID will be lost. The removal of your config file also removes the Alias. If the config file is not manually restored, this action cannot be undone.

Uninstallation will not touch or delete your ID and config files, except explicitly requested in the uninstallation menu.

Security

Providing your AnyDesk ID to a third party does not put you at risk. A request from a remote client must always be confirmed by the local user or the unattended password.

Cloned systems - ISO/Rollout/Deployment

Cloned systems have the same ID, which makes it impossible to connect to both of them.

Delete the service.conf on one of these systems and restart AnyDesk to get a new ID. In this way both machines will have a unique ID. Hence both devices can be connected to. Use this technique to deploy/rollout images of your OS with AnyDesk pre-installed:

  1. Create an OS installation.
  2. Install AnyDesk.
  3. Exit AnyDesk completely.
  4. Delete the service.conf file in: %programdata%\AnyDesk.
  5. Create the image for rollout/deployment.