Using the Required Software Policy

The required software policy enables you to distribute and install software across your organization’s devices. You can deploy to an unlimited number of devices by uploading an installation binary and specifying the package name, installation command, and schedule.

Policy attachments

You can attach files to a required software policy to install software, run scripts, or perform other actions on devices.

Note: The maximum file size for a policy attachment is now 10 GB—an increase from the previous 1 GB limit. This larger size allows you to include bigger installers, scripts, or other necessary files directly in your policies. This limit applies to all new and updated policies.

Package name, package version, and installation command

The policy requires the following information to execute properly:

  • Package name: Used to identify if the software is already installed on a device (for example, in Windows this can map to the registry GUID or the program name listed in Add/Remove Programs). For third-party software, see Naming Scheme for Third-Party Software Packages to understand how Automox identifies software.
  • Package version: Used to identify if the exact version of the package is installed on the device.
  • Installation command: The complete command that installs the software, typically using a silent or unattended installation option.

At this time, you must enter these values manually for all file types.

Optional commands for common installer types

Previously, the policy automatically filled in the installation command for certain installer types when you uploaded a file. At the moment, this does not occur. You can use the following example commands to run installers manually. Replace your-file with the actual file name.

Window MSI

Copy 
exit (Start-Process -FilePath 'msiexec.exe' -ArgumentList ('/qn', '/i', 'your-file.msi') -Wait -Passthru).ExitCode

Linux RPM

Copy 
yum install -y your-file.rpm

Linux DEB

Copy 
dpkg -i your-file.deb

You can use these commands on a test device to confirm the correct syntax and behavior before adding them to your policy.

Adding installer files to a policy

The required software policy supports a variety of installer formats, including but not limited to .msi, .rpm, .deb, .exe, and .pkg. For any file type, follow these steps:

  1. Install the software on an Automox-managed device.
  2. Refresh the device so that Automox can detect the software and display the package name or identifier.
  3. When creating the policy, enter the package name, package version, and installation command manually.

For instructions to create this type of policy, see Creating a Required Software Policy.