Using the Required Software Policy

Follow

The required software policy is designed to distribute and install software to the endpoints in your organization. By simply uploading an installation binary and setting the package name, installation command, and schedule you can deploy software to an unlimited number of systems.

Package name and installation command

The required software policy needs a package name and installation command to properly execute on the system.

  • Package name is used to identify if the software package has been installed on the endpoint. In the case of Windows, this is a registry GUID or software package name associated with installed software listed on the "Add/Remove" programs dialog.
  • Installation command is, of course, the command(s) used to install the software package on the endpoint. Typically this is the command that will launch the installer in a silent / unattended mode.

Recognized installers

Currently the required software policy will automatically populate the package name 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 will inspect the installer and pre-populate these fields. We will be adding support for additional installer types in upcoming releases.

Working with other types of installers

For .exe, .pkg, .deb and other installer types not listed above, follow these steps to ensure you can populate the package name  field of the required software policy:

  1. You will need to install the software on at least one Automox-managed system in your organization. This will allow Automox to be aware of the package (via refresh of the endpoint) and populate the package name with the software name / identifier
  2. When creating the required software policy, you will want to search for the name / identifier of the installed software package, and select it so Automox can determine if the software is installed on an endpoint or not when the policy is executed.
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.