I downloaded and installed anydesk (free licence) in Ubuntu 18.04:
sudo dpkg -i anydesk_2.9.6-1_amd64.debBut it does not allow me to change the "alias" (change the number to a custom alias, like e.g. pc1@MyCompany or machine@ad) (see fingerprint)
According to anydesk (source) you have to modify this file:
Linux:
~/.anydesk/service.confBut they do not explain how to permanently change it. How can I change the alias of anydesk? Thanks in advance
Update: (thanks to @danzel)
This question maybe has no answer (for free license). I have consulted with the official Anydesk, and only the Anydesk professional and enterprise license can change the ID to Alias. Therefore the free version can not. See
Note: If AnyDesk is used portable (not installed), only the ID is displayed and no Alias can be assigned.
So, at least on my part, this question is closed. Thanks to all the participants
54 Answers
This is available on the free version.
On the main welcome tab of AnyDesk, simply right click on the red icon in the "This Desk" card on the left hand side. This is the same UI component that shows you default AnyDesk address.
For example, the UI presents the option as so
I did this on the second run of AnyDesk. I had original tried looking at the service.conf file though I saw nothing relating to the alias name. You are also not prompted on the first run to set the alias (AFAIK) under Ubuntu; even though the AnyDesk help page on the topic says you will be.
Depends of version that you have in your System, normally when you finish the installation, it present only one time, at the first runs, the interface with you can choice your alias, it check that alias is available and set it in both site, your system, and the remote servers configuration (anydesk servers)... If you dismiss the first run when you can choice the alias, you can purge from your system the anydesk installation, and try again... this operation set a new ID and you can choice the desired alias...
1Just because this topic is in the active search so my experience might will helpful. So I cloned windows computer and any desk picked up old allies so I could not really access my first computer until the second one was on.
And just because any desk was installed I had real trouble even run portable version because no matter what you do it's still picking the old name of the first computer.
So how to actually to deal with it. There is cache file in user local and roaming folders. You need to delete the program itself and those files from user caches folders. Then if you run portable version again it will give you a number finally.
If you want to install it then change your computer name but before installation deletes old caches files otherwise, it will still pick the old name.
2The Alias is stored in a token on the computer, according to the AnyDesk support portal. This is for security reasons. They chose not to put the Alias in a file anywhere, lest the location be spread around amongst hackers and those who spend their time creating malware. Should one of them, or their programs, ever gain access to your computer they could do any number of malicious things with it. So, to answer the original posters question, by design the Alias is kept on the computer in a token and cannot be accessed, altered, or modified by anyone.
If you choose to use an Alias using the Free license, it will pick up the computer name that is stored in the "properties" information for the computer. You cannot choose your own Alias.
However, you can manually rename other computers that show up in the "Recent Sessions" area on the "New Connections" window. This is done by clicking on the menu icon (3 vertical dots in lower right side of computer icon) and selecting "rename". Of course, you have to make an initial connection to another computer running AnyDesk first, to get it to show up in the "Recent Connections" area, after which you can rename it to anything you desire.
if an "@acl" suffix appears after an Alias, it should be disregarded when connecting to computers on the local network. Although it shows up, it is not actually part of the Alias itself.
AnyDesk will only discover computers that are on the same network. It will only recognize Alias's of computers that are on the same network, as well.
If you want to connect to a remote computer that is not on the same network as the computer you are accessing it from, you need to use the AnyDesk ID of the remote computer you'd like to connect to. After connecting, you can then rename the computer to anything you'd like in the "recent connections" area of the AnyDesk "New Connections" window on the computer you accessed it from.
Using the Free License, you can only set the Alias once, from the Welcome screen, after the installation completes.
After you've set the Alias, if you need to locate the AnyDesk ID for the computer then you can right-click the AnyDesk Icon in the system tray of the computer you want to get the ID for, select "settings", then in the left-pane of the window that appears highlight "User interface", and in the right-pane check "Show AnyDesk ID instead of Alias". When you click the "New Connection" tab at the top of the window, Under "This Desk" the AnyDesk ID will now appear.
If you want set up "unattended access" to connect to a computer without anyone having to be present at the other computer, you need to set up a password on the machine you intend to access when you install AnyDesk on it. You can do this from the Welcome Screen by clicking the "set password" icon, or from the "settings" screen by clicking on "Security" on the left pane, then checking "Enable unattended access" on the right pane and clicking the "Set password for unattended access" button.
One last thing - if you can't connect to a computer that has AnyDesk installed on it, and a message appears saying "session closed" after timing out with error code win32_10060, a complete uninstall of AnyDesk needs to be done on the machine you can't connect to using a program like Revo Uninstaller or IOBit Uninstaller, then reinstall AnyDesk and set up the configuration again. Everything should work properly after that.
Hope this helps... ;-)
