New in version 4.1

The following new features and bug fixes have been implemented in version 4.1 of the CANCOM Packaging PowerBench:

New features
  • The Packaging PowerBench and the Package Subscription Service have new icons in the CANCOM corporate design.
  • PPB packages can be exported as a ZIP archive or self-extracting executable.
  • The registry key in which the execution and installation status of PPB packages is logged is now configurable.
  • Custom Package properties and program settings can be added or changed via user-defined configuration files.
  • Authentication to Intune can now alternatively be configured to use a certificate. In addition, a required multi-factor authentication (MFA) is now fully supported.
  • The Packaging PowerBench shows a splash screen at startup and thus provides information about the actions performed during the startup process.


The following bugs and problems from version 4.0 have been fixed
  • When opening a package with cmdlets of external modules, the PPB could crash.
  • Attempting to open the PPB log via CTRL + F12 resulted in a crash if logging was switched off via the options.
  • When registering a package in Ivanti DSM, files were deleted if an existing DSM package was updated. The updated package was then no longer executable.
  • When uninstalling a package via Intune, user parts were not uninstalled.
  • If only the Package Subscription Service was installed as part of the setup, the ImportConfig.xml file was not copied and no package templates could be used.
  • If the Package Subscription Service was installed in maintenance mode, the license file was not copied, although it was specified during setup.
  • If user authentication was configured for the Intune integration, a user could not perform registration if multi-factor authentication (MFA) was configured for him in Entra ID.
  • In the e-mail notifications of the Package Subscription Service, the plain text message content was defined as HTML code and the optimal display variant was arranged unfavorably.
  • If the install behavior "User" was selected during the Intune publishing of a package, the detection of the installed package subsequently failed.- 
  • The Teams notifications from the Package Subscription Service were displayed in the new Teams client without the package icon and not expanded.
  • When quickly scrolling through the package list of the Package Subscription Service, applications were sometimes displayed as subscribed although they were not subscribed.
  • If "User" was selected as the installation behavior during Intune publishing, the Installed Apps registry could not be written and the package was logged as failed.
  • The DSM variables %Date% and %Time% were not converted during the DSM import of a package
  • Under PPB version 4.0, %% placeholders and comments in If- and Else-blocks were erroneously evaluated as errors during DSM script conversion, as a result of which the affected DSM packages could not be imported.
  • No variables were supported in the commands for managing local groups.