AnyDesk-ID and Alias

Table of Contents

 

Each AnyDesk has a unique numerical ID to identify in the AnyDesk network. A more descriptive Alias can be assigned to that ID. Both represent an address to a specific AnyDesk client.

Note: Uninstallation will not touch or delete your AnyDesk-ID or configuration files unless explicitly requested in the uninstallation menu.

Alias Requirements

An Alias is structured by name and namespace: <name>@<namespace> such as computer@ad.

The public namespace is “@ad” referring to AnyDesk. All users have access to this namespace. AnyDesk portable (not installed) only has an ID. No Alias can be assigned until AnyDesk is uninstalled.

AnyDesk-Alias can currently consist of the following characters:

  • Numbers: 0-9
  • Letters: a-z, A-Z
  • Symbols: minus (-), period (.), and underscore (_)

All other characters are forbidden and regarded as invalid.

Warning: AnyDesk-Aliases in the public namespace (@ad) are permanently linked to the AnyDesk-ID and cannot be removed or reassigned. Paid license users are able to assign up to 3 Aliases in the public namespace to one AnyDesk-ID.

If regularly changing AnyDesk-Aliases or wish to reassign them, please consider using a custom namespace.

Back to Top

Custom Namespaces

Performance and Enterprise license users have the option to purchase their own custom namespace (you@yourcompany). This allows for the ability to change or reassign the Aliases that are registered to this custom namespace an unlimited number of times.

A custom namespace can also be very helpful in securing your devices in combination with our Access Control List.

To purchase a custom namespace, please contact our Sales team or through your my.AnyDesk.com customer portal by clicking the “Upgrade!” button.

Back to Top 

Backing up and Restoring the AnyDesk-ID and Settings

Whether you want to migrate your AnyDesk-ID to a new device or simply want to backup your AnyDesk-ID and Alias for a rainy day, AnyDesk allows users to backup and restore their configuration files.

To backup your ID and Alias, save the service.conf configuration file in a secure location. This enables you to retrieve your ID and Alias in case of data loss. To secure settings and recent session list as well, backup the entire “Installed” and “Uninstalled” folders respectively.

The directory of the configuration files depends on whether you have installed AnyDesk or run it portable:

Operating System Type Standard Client Location Custom Client Location
Windows 7 and newer Uninstalled
%appdata%\AnyDesk\
%appdata%\AnyDesk\ad_<prefix>\
  Installed
%programdata%\AnyDesk\
%programdata%\AnyDesk\ad_<prefix>\
Windows XP/Server 2003 Uninstalled
%appdata%\AnyDesk\
%appdata%\AnyDesk\ad_<prefix>\
  Installed
%AllUsersProfile%\AnyDesk\
%AllUsersProfile%\AnyDesk\ad_<prefix>\
macOS Uninstalled
~/.anydesk/
~/.anydesk_ad_<prefix>/
  Installed
/etc/anydesk/
/etc/anydesk_ad_<prefix>/
Linux Uninstalled
~/.anydesk/
~/.anydesk_ad_<prefix>/
  Installed
/etc/anydesk/
/etc/anydesk_ad_<prefix>/
Android 7.0 or AnyDesk 5.3.2 or older Default storage
root/data/data/com.anydesk.anydeskandroid/files/.anydesk/
root/data/data/com.anydesk.anydeskandroid/files/.anydesk-ad_<prefix>/
Android 7 and AnyDesk 5.3.4, and newer Credential encrypted storage (CE)
root/data/user/0/com.anydesk.anydeskandroid/files/.anydesk/
root/data/user/0/com.anydesk.anydeskandroid/files/.anydesk-ad_<prefix>/
 
Device encrypted storage (DE)
root/data/user_de/0/com.anydesk.anydeskandroid/files/.anydesk/
root/data/user_de/0/com.anydesk.anydeskandroid/files/.anydesk-ad_<prefix>/

Note: On Android, your device needs to be rooted to restore the service.conf file in the appropriate folder.

Setting/Changing AnyDesk-Aliases

If the client does not have a pre-existing AnyDesk-Alias, one can be assigned by right-clicking the AnyDesk-ID and selecting “Choose alias…”.

Alternatively, paid license users are able to set or change AnyDesk-Aliases of devices registered to their account through the Clients tab of their my.AnyDesk.com customer portal.

Warning: The AnyDesk-ID and Alias is stored in the service.conf configuration file. If the configuration files get lost for any reason, the ID and Alias will be lost and cannot be reclaimed unless the backups of the configuration files are restored. See Backing up and Restoring the AnyDesk-ID and Settings.

Cloned Operating Systems

If a system has been cloned after AnyDesk has already been started on it and deployed on multiple devices, they all have the same AnyDesk-ID as they have the same configuration files.

To resolve the issue, recreate and redeploy the image without the folders mentioned in Backing up & Restoring the AnyDesk-ID and Settings or manually delete the folders on the devices with the duplicate AnyDesk-IDs while AnyDesk is completely closed.

Back to Top