Deploy software and troubleshoot its result
Choose compatible target devices for a catalog application, follow each installation or removal, and retry only a diagnosed failure.
Before you start
- Create and review the application’s software catalog entry.
- Use an MFA-verified organization session and inspect target device connectivity.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Start from the catalog application
Open Software → Catalog, find the application and intended version, and click Deploy. In the dialog, choose Install or Uninstall. Confirm the title names the application and version you intend to change.
What you should see: The request is tied to the catalog definition you reviewed.
Select compatible devices and review the count
Search the eligible endpoints and check the intended devices. Select visible adds the currently visible eligible devices up to the 200-device dispatch limit. Review the connection indicator, last-seen age, and final Will install/uninstall on … endpoints count.
Dispatch and wait for a confirmed receipt
Click Deploy or Uninstall, complete any required second-factor check, and wait for the result. A successful dispatch records the target requests; it does not yet confirm installation. If the dialog says Dispatch could not be confirmed, check deployment activity before retrying.
What you should see: You have an operation to follow for each selected endpoint.
Find the deployment records
Open Software → Deployment history. Search by software or endpoint and choose the Deployment status and Deployment action filters. Use Refresh history to update the source; inspect software/version, action, endpoint, status, deployed time, and exit information.
| Field or control | What to do |
|---|---|
| Status | Filter All statuses, Pending, Running, Completed, or Failed. |
| Action | Filter All actions, Install, or Uninstall. |
| Exit | The recorded exit value, when available. A blank value does not establish successful execution. |
Diagnose a failure and retry the same operation
For a failed row, click Error to reveal the recorded error message. Correct the underlying cause, such as package identity, installer arguments, repository access, or agent connectivity. An operator can then choose Retry. Review the new result before retrying again.
Verify installed inventory and export the record
Open the endpoint link and inspect Software, collecting fresh inventory when necessary. Confirm that the expected application/version is present after install or absent after uninstall. Use Export CSV when available to export the filtered history; export is unavailable for a partial or unreadable source.
What you should see: You have both the deployment result and a later device observation of the intended application state.
If something doesn’t work
No eligible endpoints are shown.
Confirm the catalog platform, operator access, MFA state, and selected organization. Clear the search and inspect the inventory coverage notice.
A deployment remains Pending.
Check the device connection and any applicable approval or delivery policy before submitting a duplicate request.
Retry is disabled.
Refresh the history and resolve any unavailable-source or uncertain-retry state. Retry requires a failed, supported operation and operator access.
CSV export is unavailable.
Clear overly narrow filters if no rows match, and refresh any partial or unavailable history. The export control requires complete readable results.