Repository Apps
Repository Apps are a curated catalog of common applications maintained by CapaOne — browsers, runtimes, productivity tools, and more. Every app in the catalog is ready to install and update on your endpoints. You don’t need to create anything first.
Repository Apps are the lowest-maintenance option for supported software. Check the catalog before you create a Custom Application for software that might already be there.
What CapaOne handles for you
Section titled “What CapaOne handles for you”- Packaging — CapaOne builds and tests the package for each app, including the silent install and uninstall. You don’t upload installers or set up PowerBricks.
- New versions — CapaOne adds new versions to the catalog when they’re published. See How Repository App versions are sourced.
- Status on your endpoints — CapaOne shows which endpoints have the app, and which of them run an older version. See Track and update an app across endpoints.
- Storage — Repository Apps don’t use your organization’s storage.
CapaOne doesn’t install a new version on your endpoints by itself. You start the update, either manually or with a workflow. See Install and update Repository Apps.
How Repository App versions are sourced
Section titled “How Repository App versions are sourced”CapaOne uses the winget (Windows Package Manager) repository as the version source for Repository Apps.
- CapaOne checks winget for new application versions roughly every 3 hours.
- When a new version appears in winget, it is picked up and added to the Repository Apps catalog as part of the regular release cycle.
- If a newly released vendor version is not showing up in CapaOne yet, the version has usually not reached winget yet. This is not a delay on the CapaOne side. Once the version is on winget, it normally appears in CapaOne within a few hours.
- If a version is on winget but still isn’t in the catalog, CapaOne may not be able to take it yet. Two common causes are a vendor code-signing signature that doesn’t match the signature the winget entry expects, and a winget entry that was published before the vendor signed and attached the app. CapaOne picks up the version after the vendor or winget fixes this. This isn’t a delay on the CapaOne side.
Install and update Repository Apps
Section titled “Install and update Repository Apps”You can install and update a Repository App directly, without adding it as a Company App:
- From the Repository Apps tab — open the app and install or update it on the endpoints you select. See Track and update an app across endpoints.
- From an endpoint — open the endpoint and select its Applications tab. See Windows Endpoint Details.
- From a workflow — use the Update Windows applications action to update Repository Apps on every endpoint that matches a filter, for example on a schedule. Update all Repository Apps, or pick the ones to update from a list. See Automation.
A new version reaches an endpoint only when you update the app. Without a workflow, select Update for each endpoint, or Update All for all endpoints with an older version. To keep your endpoints up to date without manual steps, set up a scheduled workflow with Update Windows applications.
Add the app as a Company App only when you want to assign it to groups. See Add a Repository App.
Track and update an app across endpoints
Section titled “Track and update an app across endpoints”
The Repository Apps tab lists the catalog with each app’s name, vendor, version, category, and description. Click an app to see its status on your endpoints. The page shows the app’s name, vendor, and description, and lists the endpoints by status:
| Status | Actions |
|---|---|
| Update Available | Update or Uninstall the app. |
| Not Installed | Install the app. |
| In Progress | The installation or uninstallation is queued or running. |
| Restart Required | The app is installed, and the endpoint must restart. Redeploy or Uninstall the app. |
| Up-to-Date | Redeploy or Uninstall the app. |
| Failed | Redeploy the app, or Remove the failed patch. |
Select endpoints and choose an action, or run it on all endpoints in the list.
Add a Repository App
Section titled “Add a Repository App”Add a Repository App as a Company App when you want to assign it to groups. Endpoints that join a group get the app automatically. As a Company App, the app also gets an Installation Tier and a release status.
- Go to Windows → Applications and select the Company Apps tab.
- Click New. If you’re asked for an application type, select Repository Application.
- In Available CapaPacks, search for the app and select it.
- Check the settings:
- Name, Vendor, Description, and Icon — prefilled from the catalog.
- Installation Tier — Standard by default. See Installation Tiers.
- Architecture — 32-bit, 64-bit, or Auto, depending on what the app offers.
- Language — Danish, English, or System language, depending on what the app offers. System language is the default.
- Release status — Testing by default. See Release status.
- Click Create.
The app’s page opens, and the app appears on the Company Apps tab with the type Repository Application. You don’t choose a version: the app follows the latest version in the catalog. Endpoints get a new version when you update them, or with a workflow. See Install and update Repository Apps.
To assign the app, open it from the Company Apps tab and select its Assignment tab. See Assign and Redeploy Windows Applications.
Good to know
Section titled “Good to know”- Repository Apps install in the endpoint’s OS language by default (“System Language”). Most apps in the catalog support this; a few are fixed to a specific language.
- Clicking endpoint or group counts in the app list navigates directly to the assignment details for that app, making it easy to audit which devices have a specific application.
- Avoid managing the same app from two places. Some applications update themselves, and Windows Update also updates Microsoft Edge on its own. Running that alongside a Repository App for the same software leads to version conflicts. To let CapaOne control the deployed version, turn off the application’s own auto-update through policy and manage it only through Repository Apps.
- TeamViewer Host installed from an MSI blocks the Repository App. The TeamViewer Host Repository App uses the vendor’s EXE installer, and it can’t upgrade a TeamViewer Host installation that was installed from an MSI package. The installation fails. Uninstall the MSI installation from the endpoints first, and then Redeploy the app. You also can’t install the full TeamViewer client on an endpoint that has TeamViewer Host, or the other way around. Uninstall the one you don’t want first.
- VPN clients aren’t available as Repository Apps. VPN clients, such as Cisco AnyConnect, need configuration that differs from one organization to the next. Repository Apps don’t offer that configuration, so deploy the VPN client as a Company App instead.
- Microsoft 365 Apps isn’t a Repository App. To install Microsoft 365 Apps and choose which Office apps are included, use the Install Microsoft 365 PowerBrick in a script or Company App. Select the apps to leave out in Exclude Applications.
- An app can be temporarily pulled from the catalog. If CapaSystems finds a defect in a Repository App package, the app is removed from the catalog until the package is fixed. While it’s pulled, it doesn’t appear in Available CapaPacks, so you can’t add it as a new application. Endpoints that already have it installed keep it — nothing is uninstalled. The app returns to the catalog once it’s fixed. If you need the software sooner, upload it as a Company App. If an app disappeared because its winget package was split or replaced, see Application Update Stays Failed.
Related
Section titled “Related”- Company Apps and Scripts — upload your own installers or run scripts instead
- Application Manager — overview of the deployment surfaces