This article explains how to install the Atera Agent on a Windows device, which Windows versions are supported, how the agent works with a proxy server, and how the one-time password (OTP) verification code works.

The Atera Agent is the backbone of Atera’s monitoring system. Installed on every device you want to monitor, it continuously tracks performance, availability, and health — securely sending data to the cloud for real-time insights. With low system impact, built-in auto-updates, and smart reporting intervals based on big-data analysis, the Atera Agent ensures you’re alerted only when it matters. 

Note: Trial accounts are limited to 300 devices.

Supported operating systems

Using a supported operating system and setup ensures the agent installs correctly and performs reliably. The Atera Agent supports the following Windows versions and configurations:

• Windows 11
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Windows 10 has reached end of support, and Windows 7, Windows 8, and Windows Server 2012 R2 are officially not supported. While you may try to install the Atera Agent on these unsupported versions, we cannot guarantee that the agent will communicate properly with the console or receive automatic updates.

Additional requirement: Microsoft .NET Framework 4.7.2 or above.

Agents installed on unsupported OS versions may lead to unexpected issues or security risks, so we strongly recommend upgrading to a supported OS version for optimal performance and security. Please note that Atera is not responsible for any issues that arise from using agents on unsupported operating systems.

Note: Atera's Windows Agent supports x64 (64-bit) systems only. Windows on ARM (e.g., Snapdragon-based devices, Surface Pro X) is not currently supported as there is no ARM64 installer.

Agent versions and updates

Agents are updated automatically as part of ongoing rollouts. If your version isn’t the latest yet, don’t worry - it will update soon. If you prefer not to wait, you can reinstall the agent manually to get the newest version.

View an individual device’s agent version in its Agent Console (Overview tab), or track upgrade progress for all devices in the Windows agents support status report

Latest version: The latest version is automatically installed for all new agent downloads on active subscriptions.

For the changes in each release, see Atera Agent Version History.

Enhancements in Agent v2:

• Upgraded to .NET 8 for improved reliability and performance.
• Strengthened security with support for TLS 1.2 only.

Note:

• Agents will not yet be upgraded if they:
  • Run on 32-bit systems
  • Operate on an OS that isn’t compatible with .NET 8
• If you’re deploying the Atera Agent via a software distribution tool, make sure to download the latest installer and replace any older versions.

Features and capabilities

Silent installation

The Atera Windows Agent installs silently when installed on a device using the SYSTEM account (covers installations via GPO and Network Discovery).

Note: Silent installation is available for agent versions 1.8.5.7 and later.

Uninstall prevention

To prevent both intentional and accidental removal of the Atera Agent and ensure continuous monitoring and management of devices, end users cannot uninstall the agent via:

• Apps & Features
• Command Prompt with user privileges
• Right-clicking to uninstall from C:\Windows\Installers

You can enable uninstall prevention via Admin > My account > Account settings > Agents. If enabled, the Atera Windows Agent can only be removed via:

• SYSTEM user privileges (GPO, CMD, PowerShell, WMI)
• Deleting the device from the Atera console

Note:

• Uninstall prevention is available for agent versions 1.8.5.7 and later.
• When enabled, end users will still see "Atera" in Apps & Features.
• Uninstall prevention also applies retroactively to existing agents.

Proxy environments

From version 2.5.8.0, the Atera Windows Agent supports HTTP forward proxy environments, where the device routes its traffic through a proxy server. The proxy can be set manually, through the operating system's settings, or automatically using a PAC (Proxy Auto-Config) file, typically pushed by Group Policy.

Because the AteraAgent service runs under the LocalSystem account, the proxy settings must be applied to LocalSystem and not to the logged-in user. This differs from the v1 agent.

Note: Transparent proxies require no configuration. Traffic is redirected at the network layer by a router, firewall, or switch, so the agent communicates normally with no changes on the device.

Before you begin

• Requires Atera Windows Agent v2.5.8.0 or later.
• The proxy server must not require authentication. Proxies that require a username and password aren't currently supported.
• Allow the Atera domains and ports listed in Firewall settings for Atera's integrations on your proxy.
• Full admin permissions are required.

Automate the configuration with a script

To apply the configuration across multiple devices, use the Set-AteraAgentProxy.ps1 script. It requires PowerShell 5.1 and an elevated session, and can safely be re-run on a device that's already configured.

Configure a static proxy:

.\Set-AteraAgentProxy.ps1 -Enable -Mode WinINet -ProxyHost '10.10.1.10' -Port 8080

Add a bypass list:

.\Set-AteraAgentProxy.ps1 -Enable -Mode WinINet -ProxyHost '10.10.1.10' -Port 8080 -BypassList '192.168.1.*;*.corp.local'

Use a PAC file:

.\Set-AteraAgentProxy.ps1 -Enable -Mode WinINet -Autoscript 'http://wpad.domain.com/proxy.pac'

Use auto detect:

.\Set-AteraAgentProxy.ps1 -Enable -Mode WinINet

Check the current configuration:

.\Set-AteraAgentProxy.ps1 -Status -Mode WinINet

Remove the configuration:

.\Set-AteraAgentProxy.ps1 -Disable -Mode WinINet

Note: The script is designed to run safely as a Group Policy startup script, which runs as SYSTEM and therefore meets the script's administrator requirement. To remove the configuration later, run it again with -Disable -Mode WinINet.

Configure the remote connection tool

When a device routes its traffic through a proxy, the remote connection tool installed on it must be adjusted as well. Otherwise, the device may appear online in Atera while remote connections fail.

For Splashtop, Atera's integrated remote access tool, use the Set-SplashtopProxy.ps1 script to enable its cloud proxy setting so the Splashtop streamer routes its traffic through the configured proxy. The script requires PowerShell 5.1 and an elevated (Run as Administrator) session. It restarts the Splashtop service only when the setting actually changes, so it can safely be re-run (including as a Group Policy startup script) without disrupting active remote sessions.

Enable the proxy for Splashtop:

.\Set-SplashtopProxy.ps1 -Enable

Check the current configuration:

.\Set-SplashtopProxy.ps1 -Status

Remove the configuration:

.\Set-SplashtopProxy.ps1 -Disable

Note: If you use a different remote connection tool, apply the equivalent proxy setting according to that tool's documentation.

Install Atera's Windows Agent

There are several ways to install Atera’s Windows Agent: by downloading the installer, copying the cURL command, or sharing the installation link. These methods only deliver the installer and don't generate a code. During an interactive installation, the installer may ask for an OTP verification code (also called an installation token) to confirm the installation’s authenticity. This step helps keep installations secure and is automatically skipped for system-level deployments (e.g., via GPO or other automated methods). For details, see OTP verification code.

Note:

• Atera's Windows Agent is available for all IT Department plans.
• Atera's Windows Agent is available for all MSP plans.
• Full admin permissions are required to install the Atera Agent.
• Atera will install .NET Runtime 8 on Windows devices.
• If you're installing the Atera Agent via Microsoft Intune or in a Citrix environment, this may create duplicate devices in your console as each environment re-deploys the software after a certain period. For more info, see:
  • Install the Atera Agent using Group Policy
  • Install the Atera Agent using Intune

To install Atera's Windows agent:

1. Click Install agent in the menu bar at the top of the screen.

The Download agent installer window appears.

2. Select Windows (.msi). Then click Next.

3. Assign the agent to a site and folder (optional). Then click Next.

Note: Assigning the agent will automatically allocate all policies, configurations, and automations applied to that site and/or folder. This assignment also comes in handy with any IT automation profiles that are intended to run on newly added devices. However, you also have the option to assign the agent at a later time. For more info, see Assign a device

3. Assign the agent to a customer and folder (optional). Then click Next.

Note: Assigning the agent will automatically allocate all policies, configurations, and automations applied to that customer and/or folder. This assignment also comes in handy with any IT automation profiles that are intended to run on newly added devices. However, you also have the option to assign the agent at a later time. For more info, Assign a device

There are 3 installation methods:

• Download the agent installer package
• Install the agent via the command line
• Share the download link

Download installer package

• From the Download installer tab, click Download.
• Open the installer package (.msi file) and follow the onscreen instructions to install the Atera Agent.

Note: If the installer asks for an installation token, enter the OTP verification code. The installation token and the OTP verification code are the same code: it’s generated during the installation and emailed to all technicians. For details, see OTP verification code.

OTP verification code (installation token)

During an interactive installation of the Atera Agent on a Windows device, the installer may ask for an OTP (one-time password) verification code to verify the installation. The installer may call it an installation token, and it's sometimes referred to as an IT admin PIN. These names all refer to the same OTP verification code. There is no static or pre-generated installation token: the OTP verification code is generated during each installation.

• All technicians on the account automatically receive the OTP verification code by email, so any of them can provide it to the end user to complete the installation.
• The email is sent from support@atera.com with the subject "Agent installation requires verification code".
• The OTP verification code expires 30 minutes after the MSI file is opened. If it expires or the email doesn't arrive, restart the agent installation to generate a new one.
• The OTP verification prompt is not enforced consistently. One installation attempt on a device may show the prompt, while a later attempt on the same device may not.

If the OTP verification code email doesn't arrive:

• Check the spam or junk folder and any email security quarantine.
• The device may have Atera's servers blocked. Make sure all required domains and ports are allowed, as listed in Firewall settings for Atera's integrations, then run the troubleshooting script in Troubleshoot Atera's Windows Agent.
• The email will not arrive if the technician's email address was blocked after a hard bounce (an email that permanently failed to deliver).

Install via command line

• From the Install via command line tab, click Copy command.
• Open the terminal with elevated administrator privileges.
• Enter the installation script and hit Enter to install the Atera Agent.
• Note: During an interactive installation, the installer may ask for an OTP verification code (installation token). It's emailed to all technicians and expires 30 minutes after the MSI file is opened. For details, see OTP verification code.

Within a couple of minutes, the Atera Agent will appear on the Devices page.

Share download link

Note: Sharing the agent installer link by email won’t work, but you can use a file-sharing tool (e.g., SharePoint), or embed the link on your website. Atera agent installer links cannot be whitelisted in email or messaging platforms due to external provider security policies.

• From the Share download link tab, click Copy link.
• Share it with your end user to download and install the Atera Agent themselves.
• Note: During an interactive installation, the installer may ask for an OTP verification code (installation token). It's emailed to all technicians and expires 30 minutes after the MSI file is opened. For details, see OTP verification code.

Once installed by the end user, the Atera Agent will appear on the Devices page.

Troubleshooting

If you experience any trouble with agent installation or stability, see:

• Troubleshoot Atera's Windows Agent
• Atera Agent FAQ