NetLock RMMNetLock RMM Docs
III — How-To Guides

Deploy software with App Hub (Winget)

Add a Winget app to the catalogue, then install it on a target device set via Software Deployment.

Deploy software with App Hub (Winget)

App Hub is a catalogue; it does not install software by itself. To roll an app out to devices you combine two Collections features: App Hub supplies the package definition, and Software Deployment wraps that definition in a deployment job with targets, scheduling, and per-device result tracking. This guide walks through picking a Winget app into App Hub and rolling it out to a small group with the Software Deployment wizard.

Software Deployment wizard on the Packages step

Before you start

  • Target devices are online and assigned a policy.
  • For Winget apps, target devices are Windows and have Winget available (Windows 10 1809+ or Windows 11).
  • Required permissions: collections_enabled, collections_app_hub_enabled and one of the browser flags (collections_app_hub_browse_winget for Winget); plus collections_software_deployment_enabled and collections_software_deployment_add for the deployment.

Steps

Add a Winget app to App Hub

  1. Open Collections → App Hub (route /app_hub_manage_apps).
  2. Either click Refresh catalogs first to sync the remote catalogues, or use the Winget Catalog Browser directly.
  3. Open the Winget Catalog Browser, search for the app you want (for example 7zip.7zip), select it, and click Add to Catalog. The app appears in the App Hub list with the winget source chip, publisher, and version.

Alternatively, click Add on App Hub to open the manual-entry dialog, pick Winget as the source, and paste the Winget Package ID and Winget Source directly.

Create a deployment

  1. Open Collections → Software Deployment (route /software_deployment).
  2. Click New Deployment. Enter a Name and optionally a description at the top of the page; the four-step wizard is below it.
  3. Step 1: Packages. In Search catalog, find the app you added and pick it; it is added to the list below. Choose Install in its Action column.
  4. Step 2: Targets. Pick tenants, locations, groups, or individual devices. Tick Automatically include future group members (or the matching option for tenants and locations) if devices that join the selected scope later should be picked up automatically.
  5. Step 3: Options. Set the start date and expiry if needed, the retry policy (Max attempts per device, Backoff between retries (minutes)), and the force-reinstall and abort-on-first-failure options as needed.
  6. Step 4: Review. Check the summary and click Create Deployment. The deployment appears on the Software Deployment list.

Note: Software Deployment is not policy-driven. A deployment targets devices directly through its own wizard. The App Hub tab inside the Policy Settings editor is a separate setting; it only selects which apps appear in the tray icon.

Verify it worked

  • The deployment shows on /software_deployment with a progress indicator (finished devices / target devices) that ticks up as devices report results.
  • The deployment's detail page shows four info cards (Status, Progress, Author & Created, Scheduled / Expires) and a per-device result table.
  • Clicking into a device on the detail page opens the per-attempt details: exit code, duration, stdout / stderr tails, and any error summary.
  • On a successfully targeted device, the application is installed and reported under the device's inventory.

Troubleshooting

  • Some devices fail. Open the deployment detail page and review the per-device result. The stderr tail and exit code usually identify the cause (Winget source unavailable, package ID incorrect, insufficient disk space).

  • Install fails with an elevation or permissions error. An installer runs in a specific user context, and whether it needs administrative elevation is declared by the package maintainer, not by NetLock RMM. The App Hub entry carries an elevation setting (whether the installer requires elevation) that reflects what the maintainer specified.

    Maintainers occasionally specify this incorrectly: an installer that needs elevation is marked as not requiring it, or the reverse. The installer then runs in the wrong context and reports installation failed. When the exit code or stderr points to a permissions or elevation problem, edit the App Hub entry and test the opposite elevation setting before assuming the package itself is broken.

  • An update in the tray icon's App Hub ends with winget does not see this package as installed for the whole device or winget does not find this package in your user profile. winget keeps packages that are installed for the whole device apart from packages installed for a single user. An app with Requires Elevation is updated by the agent as the system account, which only sees packages installed for the whole device. An app without it is updated by the tray icon in the user's session and only looks at the packages of that user. The tray icon offers Update from what the signed-in user's winget reports, so the action finds nothing when the package was installed the other way. Set Requires Elevation to match how the package is installed: off for a package installed for one user, on for a package installed for the whole device. The Logs dialog shows the sentence in front of winget's own output (agent and tray icon 3.3.0.12 or later). An automatic update that meets this state is skipped without an error and tried again the next day.

  • Non-Windows devices reported failure. Winget is Windows-only. Narrow the Target step to Windows devices, or add a Flathub app (Linux) or a script-based app for the other platforms.

  • App not listed in the wizard. Apps created through the public API with availableForDeployment: false do not appear. Set the field to true through the API.

  • Retry the failed devices. Click Retry on the deployment detail page. Retry respects Max attempts per device and Backoff between retries (minutes) and increments the per-device attempt counter.