ID & Alias
If you need more information, click here and find a more detailed, technical description to set up AnyDesk Subscribe to our Newsletter Enter your email address to get updates on AnyDesk. The latest version is installed in win10. Under task manager processes, I can see 2 background anydesk services, they're configured with unattended access. Once every few days, I can't connect to anydesk until I go to apps - anydesk and open the app by physically being in front of the PC.
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.
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 as invalid.
Individual Namespaces
Customers with a Professional or Power License have the option to additionally acquire their own individual namespace (you@yourcompany). This allows for the ability to change the aliases that are registered to this namespace without any limit.
Also, you can use your namespace when setting up your client’s Access Control List.
In order to purchase your own namespace, please reach out to our Sales Team or upgrade your license by yourself on MyAnyDesk Portal by clicking the 'Upgrade!' button.
Anydesk App
Assign or Change the Alias
Free license: Users with a free-license set the alias once. The alias will be bound to the corresponding ID and cannot be altered or reassigned.
Lite / Professional / Power license with a public namespace (you@ad): Users can change a chosen alias up to three times on [my.anydesk.com], always depending on whether this public alias is not yet taken by any other user in the AnyDesk network. The alias can be changed but not reassigned.
Professional / Power license with an individual namespace (you@yourcompany): Users can change or reassign the alias for all clients on [my.anydesk.com] without limit.
Enterprise: With an individual or public namespace (you@yourcompany or you@ad) users can change or reassign the alias for all clients on [my.anydesk.com]. They are not limited in how often they change it or which aliases to choose, even with the public namespace, as they are working within their own private network.
For all licenses: ID and alias are stored in the configuration file service.conf.If the configuration files get lost by any means, the ID and Alias will be lost. If the configuration file is not manually restored, this action cannot be undone. (See 'Backup & Restore Settings and ID' below.)
Backup & Restore Settings and ID
Warning: If the configuration files get lost by any means, the ID and Alias will be lost.If the configuration file is not manually restored, this action cannot be undone.
Some cases require you to backup the ID. In case you have a new device to use AnyDesk with, copy the configuration files in order to use the ID on the new system. The directory of the configuration files depends on whether you have installed AnyDesk or run it portable. The ID is stored in the service.conf
.Uninstallation will not touch or delete your ID or configuration files, except explicitly requested in the uninstallation menu.
To backup your identity, save the service.conf' in a secure location. This enables you to retrieve your Identity in case of data loss. To secure settings and recent session list with it, copy the entire folder:
Windows 7 and later | 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 | |
Before Android 7.0 and AnyDesk 5.3.4 | Default: | root/data/data/com.anydesk.anydeskandroid/files/.anydesk/service.conf |
Since Android 7.0 and AnyDesk 5.3.4 | Credential encrypted storage (CE): | root/data/user/0/com.anydesk.anydeskandroid/files/.anydesk/service.conf |
Device encrypted storage (DE): | root/data/user_de/0/com.anydesk.anydeskandroid/files/.anydesk/service.conf |
Anydesk Sign Up Page
Cloned operating system - ISO
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:
- Create an OS installation.
- Install AnyDesk.
- Exit AnyDesk completely.
- Delete the service.conf file in %programdata%AnyDesk.
- Create the image for rollout/deployment.
AnyDesk provides the option to run as administrator (elevated), which enables the user to control applications that are limited to administrators. AnyDesk automatically runs as administrator when installed. A session to such remote client cannot request elevation since it's already granted and displays this option as disabled in the actions menu. By default, the portable (not installed) version has only standard user rights. A process that requires administrator privileges won't be accessible. (e.g. Windows Task Manager)
Actions Menu
Anydesk For Windows 10
Use Request elevation from the actions menu during session to request elevation for a portable AnyDesk on the remote client in order to control applications running as administrator. This request requires the confirmation of a UAC dialogue. When confirmed, AnyDesk is elevated on the remote client and thus able to control applications running as administrator. In case the credentials have been submitted to the remote client as shown in the image to the right, the remote client has to confirm this operation. Thus, submitting credentials to the remote side cannot be done unattended.
Account Types
Windows has two account types: Administrator and Standard User.
Administrator accounts | Have complete control. Users with this type of account can change settings globally, install programs and pass the user account control (UAC) request without credentials. |
---|---|
Standard User accounts | Have limited control. Users with this type of account can run but not install applications. Users can change system settings, but only settings that won't affect other accounts. Tasks that require elevations can only be confirmed by providing admin credentials. |