Page Type: SOLUTION
If cloning PCs with Anydesk installed, each of the clones will have the same Anydesk ID as the original PC. This is a problem, since it will only be possible to contact one of the PCs remotely (and there is no control over which PC.) Therefore, in this situation, it is necessary to clear the Anydesk ID from some/all of the PCs. This can be done by erasing a specific configuration file from the PC, and then re-running the Anydesk installation script.
The following instructions are from the Anydesk website (as of April 2019) and describe how this is done.
--------------
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:
Create an OS installation.
Install AnyDesk.
Exit AnyDesk completely.
Delete the service.conf file in: %programdata%\AnyDesk.
Create the image for rollout/deployment.
--------------
If the PC has already been cloned, deleting service.conf from the indicated folder is likely sufficient to clear the old ID. After this is done, you can re-run the Anydesk installation script to get a new ID (and send Rangecast the ID that is generated by the software.)
[FAQ-1324] Installing Anydesk on a PC where Rangecast software has already been loadedAnydesk is remote desktop software used by Rangecast to access PCs. If Anydesk must be installed (or re-installed) on a PC where Rangecast software has already been loaded, you can use an Anydesk install script that is included as part of the Rangecast software.
SYMPTOM