Clone machines with AteraAgent installed

When the Atera agent is installed, a unique registry entry called AgentId found in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent is created.

Thus, installing the agent through a cloned image will result in duplicated devices reporting back to the console.

However, if you need to create an image where the AteraAgent is already installed, as a workaround, the image needs to be created with all the agent's registry keys deleted - except for the IntegratorLogin key. This way, after the device is set up and it connects to the web, the keys will recreate automatically.

These registry keys can either be deleted manually:

Or by running the below commands in an elevated instance of CMD:

REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent" /f /v AgentId
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent" /f /v AccountId
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent" /f /v CompanyId
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent" /f /v DisableRemote
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\ATERA Networks\AlphaAgent" /f /v ServerName

Once the keys are deleted and you created the cloned image, you can restart the AteraAgent service either manually from services.msc or by running the following command in an elevated instance of CMD: 

sc stop AteraAgent && sc start AteraAgent

Deleting the agent's registry keys prior to creating the image, will prevent duplicated devices to be created in the Atera console.