Skip to content

CapaPacks in Console

CapaPacks is a subscription service where CapaSystems builds and maintains ready-to-deploy application packages for you. Subscribed packages appear under Applications and Packages > Computer Packages > CapaPacks and are shown with a blue icon in the console.

CapaSystems keeps the packages current, but you decide when to roll out a newer version. You can only upgrade a CapaPack in a root Configuration Management Point, with admin rights, and when the CapaOne integration is set up. If one of these is missing, the menu item’s tooltip tells you why it’s unavailable. To update a CapaPack:

Step Action
1 Right-click the CapaPack package and select Upgrade Package to…
2 Choose the version you want, or select Show all versions… to pick a specific one.

When a CapaPack changes without a new version

Section titled “When a CapaPack changes without a new version”

Sometimes CapaSystems updates a CapaPack without changing its version number. For example, a vendor can replace a broken installer with a fixed one under the same version. You don’t get a notification when this happens, and your console keeps the copy you already downloaded.

If a CapaPack fails to install but the vendor’s own installer works, get the updated copy:

  1. Note which groups and units the CapaPack package is linked to.
  2. Delete the existing CapaPack package in the console.
  3. In Configuration Management, right-click Applications and Packages in the root Configuration Management Point and select Create CapaPack….
  4. Select the same CapaPack to download it again.
  5. Link the package to the same groups and units as before.

The updated package deploys to the linked groups and units.

The TeamViewer Host CapaPack uses the vendor’s EXE installer. It can’t upgrade a TeamViewer Host installation that was installed from an MSI package. The CapaPack installation fails, and the package log shows a line like this one:

Shell_Execute : Run returns errorlevel '2'

To install the CapaPack:

  1. Uninstall the MSI installation of TeamViewer Host from the computers.
  2. In the CapaInstaller Console, set the CapaPack package to Waiting on the computers, so the agent installs it again.

The CapaPack installs, and the computers are listed with the CapaPack’s TeamViewer Host version.

You also can’t install the full TeamViewer client on a computer that has TeamViewer Host, or TeamViewer Host on a computer that has the full client. Uninstall the one you don’t want first.

CapaPacks is enabled through your CapaOne integration, and your CapaOne organization needs a CapaPacks contract to download packages. See CapaOne Integration in Console for how to connect the CapaInstaller console to CapaOne.

CapaPacks that contain an Install.ps1 script in the package kit run that script with the PowerShell 7 that’s installed on the client. The client needs the following:

  • PowerShell 7 or later, installed as pwsh.exe under C:\Program Files\PowerShell. Windows PowerShell 5.1 isn’t enough.
  • CapaOne.ScriptingLibrary.dll in the agent’s Lib folder, C:\Program Files\CapaInstaller\Client\Lib. It’s installed with the CapaInstaller agent.

If PowerShell 7 is missing, the job fails with the following error and is retried later:

JOBERROR : Powershell 7 must be installed.

To install PowerShell 7 on the clients, deploy the PowerShell 7 CapaPack. Deploy it before other CapaPacks, for example by linking it to the same groups.