The Atera Agent serves as the foundation of the Atera monitoring system and must be installed on all devices you wish to monitor. It continuously monitors the availability, performance, and health of the computer/server, securely transmitting the information to the cloud. By doing so, Atera promptly notifies you of any critical issues, degradation, or when predefined thresholds are reached.
The Atera Agent is compatible with Windows, macOS, and Linux devices provided that the operating system version is supported by the respective vendors. Although the agent may function on older OS versions, Atera does not guarantee its performance and does not offer support, bug fixes, or security patches for devices running unsupported versions.
What the Atera Agent Does
Q: What is the purpose of the Atera Agent?
A: The Atera Agent is a software application designed to enable monitoring and management of Windows, Mac, and Linux devices directly from the Atera console. Additionally, the Atera agent is a lightweight application that enables remote monitoring, management, automation, patching, and reporting from the Atera console. It securely reports device health and status to the cloud while enabling a wide range of remote tools and automation features.
Supported Devices and Operating Systems
Q: What are the supported versions of Windows, Mac, and Linux for the Atera agent?
A: The Atera agent is compatible with Windows, Mac, and Linux operating systems, as long as the specific version is supported by the respective vendors. While the agent may function on older OS versions, it's important to note that Atera does not provide any guarantees, support, bug fixes, or security patches for devices running unsupported versions.
For Windows, the supported versions are Windows 11 and Windows Server 2019, 2022, and 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. For the full list, including the macOS versions and Linux distributions that are supported, see:
- Install Atera's Windows Agent - Supported Operating Systems
- Install Atera's macOS Agent
- Install Atera's Linux Agent
Q: Can the Atera Agent be installed on devices other than Windows, Mac, and Linux?
A: At present, the Atera Agent is only compatible with Windows, Mac, and Linux devices. However, you can monitor other types of devices using SNMP (Simple Network Management Protocol) or other supported protocols. For more info, see SNMP FAQ
Q: Is it possible to install the Atera Agent on portable devices such as Chromebooks, Android tablets, Android phones, Apple tablets, and phones?
A: No, the Atera Agent cannot be installed on these types of devices. The Atera agent is designed for installation on Windows, Mac, and Linux devices only.
Q: Is it possible to install the Atera Agent in an on-premises environment?
A: No, the Atera Agent is a cloud-based software that requires internet access. It is not designed to be installed or operated in an on-premises environment.
Q: Is there an Atera agent for Synology NAS?
A: No, the Atera agent cannot be installed directly on Synology NAS devices, as Synology's DSM operating system is not supported by the agent; you can only monitor Synology NAS in Atera by adding it as an SNMP device, provided you have a compatible Windows machine on the same subnet to serve as the monitoring agent, macOS-only environments are not supported for this purpose. All requirements can be found on our installation articles: Install an agent
Installation Options and Permissions
Q: What are the installation options for the Atera agent?
A: There are several installation methods available for the Atera Agent. You can manually install the Windows, Mac, and Linux agents on your devices. If your Windows devices are part of an Active Directory Domain, you can use Group Policy Objects for agent installation. For Windows devices in an Azure AD domain, Intune can be used to install the Windows agent. As for Linux and Mac devices, you can utilize another remote management tool to deploy the Atera agent in bulk. We recommend referring to our articles for detailed instructions on the supported installation methods for the Atera agent.
- Install an agent
- Install Atera's Windows Agent
- Install the Atera agent using Group Policy
- Install the Atera agent using Intune
Note: For security reasons, installing previous versions of the Atera Windows agent will display a confirmation dialog for the following conditions:
- Downloading and installing the .msi package.
- Locally installing the agent via the Command Prompt.
- You can avoid the confirmation dialog by installing the .msi package via Group Policy or by installing agents via Network Discovery
Q: Do I need admin rights on a device to install the Atera Agent?
A: Yes, you will need administrative privileges on the device to successfully install the Atera Agent. Administrative rights are necessary to perform the installation process and ensure that the agent is properly installed and configured on the device. It is not possible to install the Atera Agent without administrative rights.
Q: I installed a device under the wrong customer - how do I move it?
A: Select the device on the Devices page, click the ellipses icon, choose Edit relations, select the correct customer and folder, then click Apply. This reassigns the device without needing to reinstall the agent.
Q: Can I move or migrate agents between accounts?
A: No, agents can't be transferred or migrated directly between accounts. The only way to do this is to uninstall the agents from the current account and then reinstall them under the desired account.
Installation Token and OTP Verification Code
Q: How do I get an IT admin PIN/token to install the Atera Agent?
A: The IT admin PIN, installation token, and OTP verification code are the same thing: a one-time password generated during each interactive installation of the Atera Agent on Windows. There is no static or pre-generated token. When the installer asks for it, all technicians on the account receive the OTP verification code by email from support@atera.com, with the subject "Agent installation requires verification code". The OTP verification code expires 30 minutes after the installer is opened. If it expires, restart the installation to generate a new one. The agent will appear on the Devices page within a few minutes.
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.
The OTP verification code can't be sent to another email address, and there is no option to turn off the OTP verification prompt.
Q: Why didn't I receive the IT admin PIN/token/OTP verification code while installing the Atera Agent?
A: First, check the spam or junk folder and any email security quarantine for the email from support@atera.com with the subject "Agent installation requires verification code". If it isn't there, the OTP verification code typically doesn't arrive due to communication issues between the device where the agent is being installed and Atera's servers. The email will also not arrive if the technician's email address was blocked after a hard bounce (an email that permanently failed to deliver).
Make sure all required domains and ports are allowed, as listed in Firewall settings for Atera's integrations, then follow the steps in the article below. It includes the Troubleshoot Windows Agent (.ps1) script, which you can run on the device to diagnose and fix the most common issues.
Golden Image and Cloned Devices
Q: Can I create a golden image with the Atera agent preinstalled in my Windows setup?
A: Absolutely! You have the option to create a Windows golden image that includes the preinstallation of the Atera agent. This way, you can save time and effort by not having to install the Atera agent manually every time you need to reimage a Windows machine. Please refer to our article below for detailed instructions on setting up a golden image that includes the Atera Agent:
Q: I used a Golden image for multiple Windows devices, and now all of my devices report under a single agent. How can this be fixed?
A: The golden image article has a troubleshooting section for cloned devices that appear as duplicates or report under the same agent. Follow the steps in that section to fix the problem of multiple devices reporting under a single agent.
Network Requirements and Missing Agents
Q: Are there any network changes required for the Atera agent to function in my environment?
A: Yes, it is necessary to ensure that your network adheres to the required Firewall settings for the Atera agent. For a comprehensive list of these settings, please refer to the following article:
Q: I have installed the Atera agent on my devices, but it appears to be missing. What should I do?
A: If you are experiencing issues with the installation or functionality of the Atera agent, we recommend referring to our articles that provide troubleshooting steps. Common causes include firewall or network restrictions, outdated agent versions, or unsupported operating systems. Ensure that the required ports and domains are allowed and that antivirus software isn't blocking the agent. These resources will guide you through the process of resolving any issues related to the installation and proper functioning of the Atera agent. In case these articles do not provide any help with the issues that you are experiencing, please reach out to our support team for assistance.
- Troubleshoot the Atera Agent (Windows)
- Troubleshoot the Atera Agent (Mac)
- Troubleshoot the Atera Agent (Linux)
- Agent missing from the Console
- Firewall settings for Atera's integrations
Security, FIPS, and Agent Permissions
Q: How secure is the Atera agent?
A: The Atera agent is designed with a strong emphasis on security. All communication between the Atera agent and Atera's servers is encrypted using TLS 1.2 or higher, with additional mutual TLS (mTLS) authentication for backend services. This ensures data integrity and confidentiality. To learn more about the security measures implemented in Atera and the Atera agent, please check our Trust page.
Q: Is Mutual TLS (mTLS) implemented between the Atera Console and the Atera Agent for secure communication? Do both authenticate using digital certificates during the TLS handshake?
A: Atera agents and servers communicate via a secure asynchronous messaging system rather than direct HTTP calls. For backend-to-backend communications, mutual TLS is implemented using certificates and service identities. The Atera agents use TLS 1.2 for secure communication, ensuring data confidentiality, integrity, and authenticity, with an additional layer of application-level mutual authentication through the messaging service.
Q: Is the Atera agent compatible with FIPS (Federal Information Processing Standards)?
A: Windows agents version 2.0.0.0 and later are compatible with FIPS mode and can operate on devices where it's enabled. On agents earlier than 2.0.0.0, FIPS mode isn't supported and can prevent the agent from communicating with the Atera console, so make sure it's disabled on those devices.
Note: FIPS compatibility means the agent can run on a device with FIPS mode enabled. It doesn't mean Atera is FIPS-validated or FIPS-certified.
Q: Which OS user account does the Atera agent use for its commands and features?
A: The Atera agent operates under the SYSTEM account. The SYSTEM account is a built-in user account utilized by the Windows operating system and various services. It possesses elevated privileges and permissions, granting it access to system resources and enabling it to execute crucial tasks on behalf of the Atera agent.
Q: Can the Atera agent run under a local user account?
A: No, the Atera agent cannot run under a local user account. The Atera agent requires administrative privileges and runs under the SYSTEM account, which is a built-in account used by the operating system and various services. Running the agent under a local user account is not supported.
Remote Access and Remote Actions
Q: Is it possible to initiate a remote session on devices with the Atera agent installed?
A: Yes, you can initiate a remote session on devices that have the Atera agent installed. Additionally, you have the possibility to initiate remote sessions on devices that do not have the agent installed. For more detailed information about remote options and how to utilize them, please refer to the article provided below.
Q: Are there any remote functions available with the Atera agent?
A: Absolutely! The Atera agent offers a wide range of remote features that can be accessed and utilized from the Atera console. These include functionalities such as Registry Editor, Service Manager, Task Manager, Command Line Interfaces (CLIs), and more. For more info, see Live Manage
Q: Will end users be able to see the remote actions I perform from the Atera console?
A: No, end users will not have visibility into the remote actions performed by a technician from the Atera console. The actions taken by the technician, such as troubleshooting or configuration changes, are not visible to end users. This ensures that the work of end users remains uninterrupted and unaffected by the actions performed by the technician through the Atera console. The only actions that may be visible to end users are remote connection requests and shutdown actions.
Q: Can you wipe/deactivate a Windows, Mac, or Linux device remotely using the Atera Agent?
A: No, there are no options that allow you to wipe/deactivate a device remotely using Atera.
Patch Management and Additional Software
Q: Is patch management supported by the Atera agent?
A: Yes, the Atera agent includes a patch management module that facilitates the installation of updates. It also allows you to exclude, approve, and postpone updates for your devices. For detailed information and instructions on how to utilize the patch management capabilities of the Atera agent, please refer to the articles provided below.
Q: Does the Atera agent install additional software on my devices?
A: Yes, when it's needed for a feature you use. For example, if you install software via WinGet or enable "Update all via WinGet," and WinGet isn't installed on the device, the Atera agent installs WinGet automatically. This mainly affects Windows Server 2019 and 2022, which don't include WinGet by default. The agent also installs your remote access tool (Splashtop or AnyDesk) when needed.
Agent Updates and Removal
Q: Are periodic updates provided for the Atera agent?
A: Absolutely, the Atera agent undergoes automatic periodic updates, requiring no actions on your part. These updates aim to enhance both the functionality and security of the agent. If you don't want to wait for the automatic rollout, you can update an agent manually: generate a fresh installer from the Atera console and run it over the existing installation. To see what changed in each agent release, see Atera Agent Version History
Q: How do I uninstall the Atera agent from end users' devices?
A: There are several methods available to uninstall the Atera agent from your devices. You can directly uninstall it from the Atera console, utilize scripts, uninstall it locally from the Control Panel on the device, or leverage GPO if the devices are part of an Active Directory Domain. Please refer to our articles for comprehensive instructions on uninstalling the Atera agent from your devices.
Monitoring and Console Information
Q: What monitoring capabilities does the Atera agent offer?
A: The Atera agent provides comprehensive monitoring capabilities for various critical metrics on your devices. It can monitor component temperatures, CPU/RAM/Disk usage, network bandwidth, Windows events, services, and Microsoft Exchange parameters. For more info, see Remote monitoring FAQ
Q: What information does the Atera agent display in the Console?
A: The Atera agent displays the following information for your devices:
- Hostname
- Last logged user
- Last reboot time
- IP address
- OS details (Edition, Version, Build)
- Office version
- Security info (AV, Anti Spyware, Firewall)
- Hardware details (Vendor, Model, Serial number, Motherboard, Bios manufacturer, Bios version, Bios version date, Processor, Memory, Video Card, System Drive, Mac Addresses)
- Disk details (Media Type, Model, Serial number, Number of partitions, Media type, Interface/Bus Type, Operational status, Health status, Firmware version, BitLocker key)
Q: How to enable BitLocker key?
A: Atera does not offer a built-in, BitLocker enablement, but you can enable BitLocker remotely by deploying a PowerShell script via Atera's scripting feature
Q: Can additional information about a device be displayed in the Atera Console?
A: Yes. You can use script-based custom fields to display additional device information directly in the Atera Console. These fields are populated by monitoring scripts (.bat, .ps1, or .sh) and can be set up as items within threshold profiles. This allows you to track and display custom values from your devices and even trigger alerts when thresholds are met or breached. For more info, see:
Agent Resource Usage (RAM and CPU)
Q: How many resources does the Atera Agent use for Windows devices?
A: When the agent is idle or not actively used, it typically consumes very little RAM, usually between 10-50 MB. Even when the agent is actively monitoring and performing tasks, RAM usage remains relatively low, and it may peak at around 250 MB in some cases for short durations of time.
Similar to RAM, the CPU usage of the Atera Agent is minimal. When idle, it consumes almost no CPU resources, with CPU usage hovering around 0% to 1%. During more intensive tasks, CPU usage can increase slightly, reaching 1% to 3%. Please note that the CPU consumption also heavily depends on the CPU used on the device, low-end CPUs might go above the mentioned usage, while high-end CPUs will have lower usage.
Q: How many resources does the Atera Agent use for Mac and Linux devices?
A: The Atera Agent for Mac and Linux devices is designed to be lightweight and has minimal resource consumption. When the agent is idle or not actively used, it typically consumes very little RAM, usually around 50 MB.
Similar to RAM, the CPU usage of the Atera Agent is minimal. When idle, it consumes nearly no CPU resources, with CPU usage typically hovering between 0% to 3%.
