Install software remotely on Windows and macOS devices with Atera's built-in WinGet (Windows) and Homebrew (macOS) integrations. Deploy applications to one or many devices in a few clicks, without downloading installers or checking for the latest versions manually.
Note:
- To link your integrated repository to Atera, see Private software repository.
- To upload your own .EXE or .MSI files to install software applications, see Create, upload, and generate scripts.
- To schedule automated patching, see Automate software patching via automation profiles.
Requirements and limitations
WinGet
- Microsoft Visual C++ Redistributable must be installed on devices before you can install software via WinGet.
- WinGet installations executed through the Atera agent run under the SYSTEM account. To prevent applications from being installed only to the SYSTEM profile, Atera enforces machine-wide installs by adding
--scope machineto WinGet commands. - Windows Server 2019 and 2022 don't include WinGet by default. When you install software via WinGet or enable "Update all via WinGet" on these servers, the Atera agent installs WinGet automatically.
- In the Software inventory, only applications detected with WinGet as the source display an Available version for updates.
Homebrew
- Some Homebrew software patches require password authentication or have other permission requirements, so they can't be installed through Atera. If this applies, Atera displays a message.
- The Homebrew integration in Atera uses Homebrew's Cask Tap (cask.json) only. This means only software on Homebrew's Cask list is available through Atera.
Install software
Deploy software to one or many devices, as long as all selected devices run the same OS. When deploying to Windows devices, you can also set your execution preferences (for offline devices) and choose the software source.
Note: Chocolatey is being deprecated as a software source in Atera. For Windows devices, we recommend installing software from WinGet. For timelines and next steps, see Chocolatey deprecation: what's changing and how to move forward.
To install software:
-
From Devices, check the box next to each device you want to install software on.
-
Click Software installation.
The Software installation window appears.
- Set the following:
-
Software execution preferences (Windows devices only): Choose to install the software on:
- Online devices only.
- Online and offline devices. The task stays in the queue for a set amount of time until the device comes back online (1 hour, 1 day, 1 week, 2 weeks, or 1 month).
- Source (Windows devices only): Select the repository to install the software from.
- Software: Enter the full or partial name of the software (autocomplete will bring up all relevant matches). Once the software is selected, you can enter parameters for a customized installation. When available, a list of package parameters, along with descriptions, is displayed.
-
Software execution preferences (Windows devices only): Choose to install the software on:
-
Click Install.
The installation request is sent. Check the Recent Processes report for details.
If the software isn't available in WinGet
If the software you need doesn't appear when you search WinGet in Atera, you can request that it be added to the WinGet public repository. Until it's added, you can deploy it with Atera another way.
Get it added to WinGet:
- Request it (recommended): Open a Package Request/Submission issue in the microsoft/winget-pkgs GitHub repository. You don't need to create a package manifest. A community contributor or the app's publisher can then submit the package.
- Submit it yourself: If you want more control over timing, you can create and submit the package manifest yourself. Anyone can submit a package, as long as the publisher has a publicly available download URL. For step-by-step instructions, see Request or submit a missing application to the WinGet repository.
Note: Microsoft and its community moderators manage the WinGet repository, not Atera. Atera doesn't control whether a request or submission is approved, or how long the review takes.
Deploy it with Atera in the meantime:
- Upload your own installer or script: Upload the vendor's .EXE or .MSI file, or a PowerShell or Batch install script, and run it on your devices. Make sure installers use silent installation arguments. A script installs a fixed version, so update it when a newer version is released. See Create, upload, and generate scripts.
- Use your private repository: Host your own packages and install them from Atera. See Private software repository.
