Skip to main content
Question

Cloning of VM and control room registration

  • August 27, 2026
  • 1 reply
  • 13 views
A
Forum|alt.badge.img

Hi everyone,

I have been using a VM as a runner for some time, and we decided to buy a new bot runner license, and provision a new VM to add to the device pool.

We are using AWS Workspaces that have two drives: D:\ for most programs+documents and C:\ for system and some programs

We have cloned the VM, meaning the C:\ drive is kept and the D:\ drive is empty

When connecting my user runner number 2 to the VM, something very strange happened and from the Control Room point of view they were seen as only one.

I think this can be caused by the control room registration or something like that : I have deleted the files in the  C:\Windows\System32\config\systemprofile\AppData\Local\AutomationAnywhere, configured again the bot agent and it seems to have solved the problem.

Do you think it can actually have been the cause of my problem? In that kind of situation, how should I copy a VM?

1 reply

Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+6
  • Aaron.Gleason
  • Automation Anywhere Team
  • August 27, 2026

​@Augustin You likely still have the Control Room information in that VM. It needs to be erased.

Stop the Bot Agent service, then delete the contents of the c:\windows\system32\config\systemprofile\appdata\local\automationanywhere folder. You can then restart the Bot Agent service and things should be sorted.

    Terms & ConditionsAccessibility statement