Define an application in the software catalog
Save application identity, platform, install method, package or installer details, and an optional detection path before deploying it.
Before you start
- Know the application’s exact package identifier or trusted installer URL and its unattended-install arguments.
- Choose the supported platform and the version you intend the catalog entry to represent.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Check the catalog before adding software
Open Software → Catalog, search by name or publisher, and filter All, Windows, macOS, or Linux. Read the existing version and install-method badges. Click Add Software to create an entry, or an existing card’s edit action to revise it as an administrator.
What you should see: You have chosen an existing definition or are creating a deliberate new one.
Enter the application identity
In Add software or Edit software, fill the identity section. Name and version are required. Select the platform before choosing the installation method, because the allowed methods depend on that platform.
| Field or control | What to do |
|---|---|
| Name | The recognizable application name, for example Google Chrome. |
| Publisher | Optional publisher metadata used for catalog discovery. |
| Version | The version represented by this catalog definition. |
| Platform | Windows, macOS, or Linux. Create a suitable definition for each platform. |
| Icon URL | Optional image URL for the catalog card. |
Choose the installation method
In Installation, select the platform package manager or Custom URL. Enter the exact package-manager identifier when using a package manager; a marketing name is not always the installable package ID.
| Field or control | What to do |
|---|---|
| Windows → WinGet | Enter a Package ID such as Google.Chrome. |
| macOS → Homebrew | Enter a cask or formula name such as google-chrome. |
| Linux → APT | Enter the package name available in the device’s configured repositories. |
| Custom URL | Enter Installer URL, Install args, and optional Uninstall args appropriate to the actual installer. |
Set an optional detection path and save
Under Verification, enter Detect path if the agent should check a known file after installation. Use a path appropriate for the selected OS and application. Click Add software or Save changes, then confirm the updated card appears with the expected version and method.
What you should see: The catalog contains the saved installation definition. No device has been changed by saving it.
Deploy the saved definition
Choose Deploy on the card to open the device chooser. Select Install or Uninstall, search compatible endpoints, and check the exact devices. Review the final target count before dispatch. Follow the Software deployments guide to inspect resulting records and failures.
If something doesn’t work
The package manager choice changes after selecting an OS.
The form keeps only supported methods: WinGet for Windows, Homebrew for macOS, APT for Linux, and Custom URL for each.
The save could not be confirmed.
Refresh the catalog before saving again; the request may already have reached the service. Check the returned card values.
Deployment fails although the catalog saved.
Inspect the deployment error and verify the package ID, installer URL, install arguments, package-manager availability, and device connectivity.