CapaInstaller 6.7.108 Release Notes

CapaInstaller 6.7.108 Release Notes


Release summary
CapaInstaller 6.7.108 is a maintenance-focused release with fixes across server behavior, client runtime handling, signing, packaging, dashboard access, SSI connectivity, and OSD cleanup. It also includes selected improvements to software catalog search, AD group handling, package processing, and platform readiness.

Improvements in CapaInstaller 6.7.108

  • .NET 10 adopted as the runtime for PowerPacks

    • CapaInstaller PowerPacks have been migrated to .NET 10, the latest long-term support release. This brings performance improvements, enhanced security, and keeps the platform on a supported and up-to-date runtime. It is not nessecary to install .Net 10 on Endpoints beacuse it is embedded in the Execution Engine.

  • Software catalog now supports searching by description

    • The software catalog search has been extended to match against package descriptions, not just titles. This makes it easier to locate packages when you know what a piece of software does but not its exact name.

  • CMS_GetLinkedPackages

    • A new CMS stored procedure, CMS_GetLinkedPackages, has been added to allow retrieval of all packages linked to a given entity. This enables more flexible integrations and reporting against the package relationship model.

  • Failed package unzip now sets status to Cancelled

    • When a package fails to unzip during deployment, the job is now moved to a Cancelled state instead of remaining in an ambiguous or stuck state. This gives administrators a clearer signal and makes it easier to identify and retry failed installations.

  • Resolved PRIMARY filegroup full error in changeset table

    • The changeset table was causing the SQL Server PRIMARY filegroup to fill up, leading to database errors and potential service disruption. The underlying data growth issue has been addressed to prevent recurrence.

  • OSDClient cleans up downloaded repository folders

    • The OSDClient now removes the temporary repository folder after a completed OS deployment, reducing disk usage on target machines and keeping the local filesystem tidy post-installation.

  • AD group synchronisation now limited to active units

    • Active Directory group processing has been updated to only consider active organisational units, preventing disabled or stale objects from being evaluated and reducing unnecessary processing overhead during synchronisation.

  • BAADS server ignored its own free space threshold

    • The BAADS server was distributing content even when available disk space had dropped below the configured minimum, bypassing its own free-space protection rules. This could lead to failed deployments and unexpected storage exhaustion on distribution points.

  • System Plugin forced CI Console to 100% DPI scaling

    • The System Plugin overrode the display scaling settings, causing CI Console to always render at 100% regardless of the user's configured DPI. This made the interface appear too small on high-resolution displays.

  • SSI failed to establish a data connection (Silent Server Installer)

    • The Software Self-Service Interface (SSI) was unable to connect to the backend data source, preventing it from displaying or delivering software to end users.

  • Norwegian locale displayed incorrect thousands separator

    • On Windows systems configured with the Norwegian (Norsk) Unicode locale, numeric values were not formatted with the correct thousands separator, causing display inconsistencies in reports and UI elements.

  • CiStub blocked by unnecessary FIPS requirement

    • CiStub was failing on systems where FIPS-compliant cryptography is enforced, due to an unnecessary FIPS dependency in the component. The requirement has been removed, allowing CiStub to operate normally in FIPS-enabled environments.

  • Executables in the Util folder were unsigned

    • Several executables located in the Util folder were missing a valid code signature. Unsigned binaries can trigger security warnings or be blocked by application control policies such as AppLocker or Windows Defender Application Control.

  • Package creation failed in the management console

    • An error prevented new packages from being created through the management interface. Affected users encountered a failure when attempting to save or submit a new package definition.

  • CapaOne Dashboard missing from client machine context menu

    • Right-clicking a client machine no longer showed the option to open the CapaOne Dashboard, making it inaccessible from that entry point. The menu option has been restored.


If you need assistance confirming your current patch level or are running CapaInstaller 6.6 or older, we highly recommend contacting your technical account manager for guidance on how to update


Resources

Download the latest version

Read how to update

Contact customer services