Otto  background

Using the Required Software Policy in Automox

Connect With Us

Start now, and patch, configure, and control all your endpoints in just 15 minutes.

The Required Software Policy is designed to distribute and install software to the endpoints in your organization. You can deploy software to an unlimited number of systems by uploading an installation binary and setting the package name and version number, providing an installation command, and setting a patching schedule.

Required software policies require a package name, version number, and installation command to properly execute on the system.

  • The package name is used to identify if the software package has been installed on the endpoint. The name in the policy must match the installed name otherwise the associated devices will show as non-compliant in the Automox Console.
  • The version number is required to guarantee compliance. The version number in the policy must match or exceed the version number of the software package otherwise the associated devices will show as non-compliant in the Automox console.
  • The installation command is a script containing the necessary command(s) used to install the software package on the endpoint. It is necessary that the installation commands use silent or quiet mode in order to remove the need for user input and maximize the automated capacity of the Automox service.

Recognized Installers

Currently, the required software policy automatically populates the package name, version number, and installation command for the following installation binaries.

  • MSI (Microsoft Windows installer package)
  • .deb (Debian Software package)
  • .rpm (RPM Package Manager)

When an installer of one of these types is uploaded to the Automox platform, we inspect the installer and pre-populate these fields with values found inside the installation package. We also provide a script in the installation command field. Before the system sets these values, you are prompted to accept the installation.

Working with Other Types of Installers

For .exe, .pkg, .dmg and other installer types not listed above, follow these steps to ensure you can populate the package name and version number fields for the required software policy:

  • Use the command line to install the software package locally and check the package name and version number.
  • Enter the software package name and version number in the correct fields on the Create Policy page.
  • The commands used to install the software package can be used as a guide for the creation of the installation script.

Automox for Easy IT Operations

Automox is the cloud-native IT operations platform for modern organizations. It makes it easy to keep every endpoint automatically configured, patched, and secured – anywhere in the world. With the push of a button, IT admins can fix critical vulnerabilities faster, slash cost and complexity, and win back hours in their day. 

Grab your free trial of Automox and join thousands of companies transforming IT operations into a strategic business driver.

Dive deeper into this topic

loading...