Atera's comprehensive software management options empower you with a high degree of control and exceptional flexibility, enabling you to seamlessly handle the installation, updates, and removal of software applications across your devices.
Frequently asked questions
This section will cover the frequently asked questions regarding the Atera Software management module.
General
Q: How can I install applications on my devices using Atera?
A: You have multiple options for installing third-party applications on your devices:
Software Installation Tool: Use the built-in tool to install applications remotely and silently from Chocolately, Homebrew, Winget, or your Private Repository.
Manual Upload: If the application isn’t available in Chocolately, Winget or Homebrew, or you don’t have access to a private repository, you can upload the .exe or .msi file directly to your Atera instance and run it as a script on your devices. More details on how to upload your files can be found here: Create, upload, and generate scripts.
Q: Can I install applications in bulk on my devices?
A: Yes. There are two main ways to install applications on multiple devices at once:
Devices Page: Go to the Devices page, select the agents you want, and click Software Installation. Choose the application, and it will be installed on all selected devices.
IT Automation Profile: Within an IT Automation profile, you can select a single application or a software bundle to deploy to your target devices.
Q: Are there any actions required on my end to ensure I can install applications on my devices?
A: Yes:
Whitelist all required servers/ports for Atera integrations.
Chocolatey/Homebrew: No extra action—dependencies are handled automatically when the Atera Agent is installed.
Winget: Is installed automatically by the Atera agent. To use it, ensure that Microsoft App Installer (which provides Winget) and Microsoft Visual C++ Redistributables are installed on each device, as these are not installed by the Atera agent. Microsoft App Installer comes preinstalled on Windows 10 and 11, while Visual C++ Redistributables are not installed by default and are added only when required by applications. If you encounter issues installing applications via Winget, check whether these components are present and install them if necessary.
See: Firewall settings for Atera's integrations.- Firewall settings for Atera's integrations
Q: Why might software versions appear behind or fail to update in Atera?
A: This can happen for a few common reasons. The device might be offline, missing internet access, or missing required components. Some apps can’t update automatically if they need user input or if the app is currently open. Updates also depend on external software lists (like WinGet, Chocolatey, or Homebrew), and if the newest version isn’t available there yet, the update may be delayed. In some cases, apps installed outside supported package managers, automation profile settings, or update limits can also affect updates.
Q: What version of Winget do I need to update through Atera?
A: We recommend using the latest version of Winget. It typically updates automatically on your device, ensuring compatibility with Atera updates.
Public repository
Q: Are there additional charges associated with the software management options in addition to my Atera subscription?
A: While the majority of software management features are included within your Atera subscription, it's worth noting that some specific features may incur additional costs.
Q: Could you explain how the software management options function within Atera?
A: Atera integrates with Chocolatey, Winget, and Homebrew, enabling installation and updates on devices with the Atera Agent installed. You can deploy on demand (Devices page) or automatically (Automation profiles + Bundles).
Q: Can you explain what Chocolately, Winget and Homebrew are?
A: Chocolatey is a Windows command-line package manager for automating software installation and updates, Winget (Windows Package Manager) is Microsoft’s official secure solution for installing and managing software on modern Windows systems, and Homebrew is an open-source package manager for installing software on macOS devices—all three simplify bulk deployments and updates through Atera’s integrations.
Q: Who oversees the management of packages used for software installation?
A: The management and upkeep of packages used for software installation are the responsibility of community members within Chocolately, Winget, and Homebrew. These individuals actively manage and update the packages available within the public repositories of Chocolately, Winget, and Homebrew.
Q: Is it necessary to have the Atera agent installed on my devices to utilize these features?
A: Indeed, you do require the Atera agent to be installed on your devices to fully utilize these features.
Q: Which operating systems are compatible with the public repository?
Chocolatey: Windows (desktop & supported server builds).
Winget: Windows 10 1709+, Windows 11, and Windows Server 2025 (older servers like 2019 are not supported due to missing dependencies).
-
Homebrew: macOS (Linux currently not supported for software installs via Atera).
Note: Linux devices aren’t currently supported for software installs via Atera, even though Homebrew exists for Linux.
Q: Is it necessary to manually install Chocolatey, Winget, or Homebrew on my devices?
A:
- Chocolatey/Homebrew: No. They’re handled automatically with the Atera Agent.
- Winget: Yes, you must ensure App Installer and Visual C++ Redistributable are present on each device. Atera does not deploy these prerequisites.
Q: What is the procedure for installing applications through Atera?
A: There are several methods available for installing software applications. You can opt for manual installation through the Software installation module. Alternatively, you can automate software installations on your devices by utilizing IT Automation profiles in combination with Software bundles.
Q: What exactly is a software bundle?
A: A software bundle is a compilation of multiple software applications within your Atera instance. It allows for streamlined installations, as you can easily apply the bundle to install all the included software applications on a device. Moreover, software bundles can be leveraged to automate the installation of software applications on newly added devices.
Q: What are the steps to manually install a software application in Atera?
A: To manually install a software application in Atera, navigate to the relevant device, select "Manage," then choose "Software installation." Next, search for the specific software application you want to install. For a more in-depth guide, please consult the article provided below.
Q: What's the process for automatic software application installation?
A: To install a software application automatically, start by creating a Software installation bundle. Subsequently, you'll need to associate this bundle with an IT Automation profile. For a more comprehensive guide on how to automate software installations, please consult the article linked below.
Q: How can I update software applications using the Software Management tool?
A: To gain a comprehensive understanding of the process for updating your software applications, please refer to the resource provided here.
Private repository
Q: Can I integrate a private repository into the Software Management module within Atera?
A: Certainly, you have the option to establish your private repository where you can incorporate the software applications you intend to install on your devices.
Q: Could you explain the functioning of the private repository within Atera?
A: Atera's private repository takes advantage of NuGet and Chocolatey to streamline application management. NuGet enables customers to store and manage their preferred applications, with Chocolatey serving as the tool for installing applications sourced from NuGet.
Q: Which private repositories are compatible with Atera?
A: Here is a list of the supported Private Repository Versions:
- Azure Artifacts: Learn how to get started with NuGet packages in Azure Artifacts.
- JFrog Artifactory: Follow the guide on setting up a NuGet repository in JFrog Artifactory.
- MyGet: Get started by creating your own NuGet feed using MyGet.
All three options offer full integration with NuGet, requiring customers to configure their repositories on the chosen platform. Azure Artifacts is recommended as the preferred platform.
Q: Are there any additional expenses associated with the private repository?
A: Indeed, in addition to the charges within Atera, you will be responsible for the storage of the software applications housed in your private repository. These storage costs are paid directly to your chosen vendor, not to Atera, and are billed through the hosting platform of your repository. Furthermore, it's worth noting that bandwidth fees may also apply. Each software installation on a device incurs an associated bandwidth charge. The exact pricing for both storage and bandwidth is determined by individual providers, so it's advisable to contact your respective service providers for specific cost details.
Q: What's the process for integrating my own repository into Atera?
A: For detailed information on integrating your personal repository into Atera, kindly refer to the article provided here.
Q: Why doesn't Robin (Autopilot) find or install software from my private repository?
A: Robin uses the description and summary fields from each package's .nuspec to power its search. If a package is missing either field, Robin won't surface it and may fall back to SharePoint or other sources.
Fix: update the .nuspec with both fields populated, increment the package version, and re-publish. See the Private software repository article for details.
Q: Could you clarify the distinction between a private repository and the repository provided within Atera?
A: Certainly. The public repository is the standard Chocolatey, Winget and Homebrew community repository, openly accessible to the general public. It contains a vast array of software packages meticulously maintained by the community.
In contrast, the private repository is tailored to a specific organization or individual and can host customized or proprietary software that is not available in the public repository.
When you deploy software from your private repository via Atera, you are not drawing applications from the extensive selection of packages in the public Chocolatey, Winget, or Homebrew repository. Instead, you are sourcing software directly from your seamlessly integrated private repository. This ensures that only the software you have personally added, reviewed, and endorsed is installed on your devices.
Q: Which operating system types are compatible with the private repository?
A: The private repository is specifically designed for Windows devices. Mac and Linux devices are not compatible with the private repository.
Q: If I integrate my private repository, can I still access the public repository?
A: Yes, you retain the option to access the public repository through Chocolatey, even after integrating your private repository.
Q: What are the available methods for uploading files to the private repository?
A: Atera provides two distinct methods for incorporating an installer into the private repository:
File Upload: With this method, you can upload the installer file directly to the private repository. However, it's important to note that there's a file size limit of 1.5 GB with this approach. Additionally, customers are responsible for manually replacing the existing version in their Atera instance with each new software release.
URL Addition: This method offers several advantages. It allows the inclusion of installers through a URL link, bypassing the 1.5 GB file size restriction. Moreover, when the software creator uses the same URL for updates, the latest software version is automatically installed. However, one drawback is that if the software developer modifies the URL, customers must manually update the link in such cases.
Uninstall software applications
Q: What's the procedure for uninstalling a software application from my devices?
A: Atera offers three methods for uninstalling software applications from your devices. The first approach involves using the Software inventory module within Atera, which enables you to uninstall individual software applications from your devices. You can also create a Software Inventory Report to remove applications in bulk. The second option is to utilize scripts to uninstall the software application from your devices. This script-based approach allows for uninstallation on a single device or in bulk. For additional details, please refer to the articles linked below.
Q: I'm attempting to uninstall a software application from my devices, but I've noticed that the option to select the software is grayed out. What's the reason for this?
A: The reason for the grayed-out option is that certain software applications lack support for "silent uninstall," a feature typically provided by the software developer. In cases where this feature is absent, the software cannot be uninstalled using the Software inventory option within Atera. The sole method for removing such applications is by utilizing a script.
Technical questions
This section will cover the technical questions regarding the Atera Software management module.
Q: What file types are currently supported in the private repository?
A: Presently, the private repository exclusively supports .EXE or .MSI files.
Q: What are some typical concerns or issues to be aware of when dealing with the private software repository?
A: There are a couple of common issues to keep in mind:
Authentication Error: If authentication fails, such as when the token expires, synchronization will be disabled. As a result, you won't be able to view the software in your private repository or deploy it to your devices.
Detached Repository: When you detach the repository, it's important to note that all software items will be deleted from all their associated bundles.
Q: Is it possible to use file-sharing websites like OneDrive with a private repository?
A: File-sharing websites like OneDrive may encounter compatibility issues due to certain limitations within the Chocolatey framework.
Q: What are some common challenges or constraints that should be kept in mind regarding the public repository within Atera?
A: When working with Chocolatey, encountering the "429 Too Many Requests" error means you've reached the rate limit, which will be in effect for one hour. If the rate limit is exceeded again within that time frame, it will be extended for an additional hour. It's important to note that this rate limit is established by Chocolatey, and Atera does not have the authority to modify it.
As for Homebrew, it's crucial to be aware that certain software applications and patches may necessitate password authentication or have other permission prerequisites. Consequently, these specific software items cannot be installed through Atera at this time. When such situations arise, a notification will inform you of the relevant requirements. This behavior is attributed to a security measure inherent to the Mac OS.
Common limitations or issues with Winget include dependency on Microsoft/community repositories (so not all apps can be installed or updated via Winget), limited version control such as the inability to downgrade, incomplete dependency management requiring occasional manual intervention, possible failures if prerequisites like Microsoft Visual C++ Redistributable are missing, and challenges with software installed under the system account not appearing as expected for users or in the Start Menu. Additionally, Winget is only supported on modern Windows versions (not older Windows Server editions), and troubleshooting failed installs may require examining logs or the installation context.
