Skip to content
Documentation

All versions since [6.6] - 2024

All versions

[6.6] - 2024

Added

  • Full HTTPS support across all CapaInstaller communication, including Windows Update Server integration.
  • PowerPacks v2.0: a dedicated PowerShell execution engine, user-facing message boxes ($InputObject.ShowMessageBox), and access to all CMS functions from PowerPacks.
  • Copy any value from the endpoint Inventory view to the clipboard.
  • Keep load-balanced front-ends in sync automatically when promoting packages.

Changed

  • Removed the “Select all” option in the Software Catalog.
  • Copy Relations now removes the old package and suggests a better name for the new one.

Fixed

  • Numerous fixes: CapaPack download cleanup, agent signing, distribution server, console performance without internet access, OSD chassis-type detection, and more.

[6.7.0] - 2025

Added

  • PowerPacks now require .NET Desktop Runtime 8.0.0.
  • Improved code signing of .exe, .msi, and .dll files.

Changed

  • The CapaOne agent no longer installs if OrgKey is missing from the configuration.

Removed

  • Discontinued support for SQL Server 2014, Windows Server 2012, and Windows Server 2012 R2.

Fixed

  • BIOS clock errors affecting HTTPS during OSD (requires rebuilding boot.wim after patching).
  • CapaOne dashboard link.
  • Statistics not sent after re-establishing a connection with CapaOne.
  • PowerPack message box not shown before restarting the InfoCenter.
  • Duplicate Service tree structures appearing after a fresh installation.
  • Products not working on a contract’s expiration date.

[6.7.101] - 2025

Added

  • Windows Server 2025 x64 is available as an image type in OSD.
  • Keyboard language can be selected in Windows PE to reduce password-entry errors.

Fixed

  • CapaInstaller BaseAgent caused high CPU utilization.
  • Deletion of the CapaInstaller OSDeploy service.

[6.7.102] - 2025

Changed

  • The EFI System partition size during image deployment is now 512 MB (was 100 MB).

[6.7.103] - 2025

Added

  • CapaInstaller MDM now supports Apple iOS 26.

[6.7.104] - 2025

Fixed

  • A unit was not correctly removed from calendar groups.

[6.7.105] - 2025

Added

  • CapaInstaller MDM now supports Apple iPadOS 26.

[6.7.106] - 2026

Changed

  • PowerPack default execution timeout increased from 25 minutes to 12 hours.

Fixed

  • PowerPack-related modules are now correctly signed.

[6.7.107] - 2026

Added

  • Asynchronous PowerPack message boxes can be closed with $InputObject.CloseMessageBox.

Fixed

  • CapaInstaller Agent ran every hour instead of respecting its configured interval (default 4 hours).

[6.7.108] - 2026

Added

  • PowerPacks now run on .NET 10 (embedded in the Execution Engine — no .NET 10 install required on endpoints).
  • Software catalog search now matches package descriptions, not just titles.
  • New CMS stored procedure CMS_GetLinkedPackages to retrieve all packages linked to an entity.

Changed

  • A failed package unzip now sets the job status to Cancelled instead of leaving it stuck.
  • Active Directory group synchronisation is limited to active organisational units.
  • OSDClient removes the temporary repository folder after a completed OS deployment.

Fixed

  • BAADS server distributed content even when free disk space was below the configured minimum.
  • System Plugin forced CI Console to 100% DPI scaling on high-resolution displays.
  • SSI (Software Self-Service Interface) failed to establish a data connection.
  • Norwegian locale displayed the wrong thousands separator.
  • CiStub was blocked by an unnecessary FIPS requirement in FIPS-enabled environments.
  • Unsigned executables in the Util folder.
  • Package creation failed in the management console.
  • CapaOne Dashboard option missing from the client machine context menu.
  • Changeset table filled the SQL Server PRIMARY filegroup.

[6.7.109] - 2026 Latest

Added

  • Optimized disk partitioning – Microsoft-recommended layout — CapaInstaller now supports the Microsoft-recommended partition layout for UEFI-based devices when deploying Windows, creating the four required partitions (System/EFI, MSR, Windows, and Recovery) in the correct order with the correct sizes and file systems. This results in more robust installations, better support for Secure Boot and BitLocker, and ensures your setup is ready for future Windows updates.

Fixed

  • Package Status Views now load correctly — an issue that prevented the view from displaying package status data has been resolved.