CapaWinUpgrade 4.3 - Release Notes

It's now possible to use colored wallpaper on the dynamic installation screen, based on the result of a feature upgrade.

Setting the global variable gbUseColoredWallpaper to True in the “Post Upgrade” package will result in a green wallpaper when a feature upgrade is successfull and a red wallpaper when a feature upgrade has failed.

The wallpaper is always blue during the feature upgrade.

Open

Open

Open

It’s now possible to show custom text on the dynamic installation screen, based on the result of a feature upgrade.

The value of the global variable gsInstScreenCustomerTextOnInstallation in the “Upgrade” package will be presented to the end-user during the feature upgrade.

The value of the global variable gsInstScreenCustomerTextOnError in the “Post Upgrade” package will be presented to the end-user when a feature upgrade has failed.

The value of the global variable gsInstScreenCustomerTextOnSuccess in the “Post Upgrade” package will be presented to the end-user when a feature upgrade has succeeded.

It’s now possible to show a warning prompt to the end-user, using the global variable gbShowCloseAppPrompt in the “Upgrade” package.

Setting the value to True will show the following prompt to the logged on user. The language can be controlled by setting the gsMessageBoxLanguage global variable value to either “DA” or “EN”.

Open

The solution detects if the optional features containing Microsoft PDF printer and Microsoft XPS printer are enabled.

If the optional features are enabled, they are automatically disabled during the feature upgrade and are re-enabled afterwards.

It’s now possible to cache extracted installation files, using the “Download Content Package” package.

The “Post Install” package has been renamed to “Post Upgrade”

The “Check PreRequisites” package will show status Failed in the CapaInstaller Console, when a computer is not ready for a feature upgrade.

The “Post Upgrade” pcakage will show status Failed in the CapaInstaller Console, when a feature upgrade has failed.

It’s now possible to leave the installation files extracted on the computer by setting the global variable gbKeepUpgradeFilesOnClient to True in the “Check PreRequisites” package.

It’s also possible to download and extract only the installation files, using the new “Download Content Package” package. The package can be used for caching installation files or for troubleshooting.

The solution automatically detects if the extracted installation files on the computer matches the expected version. This ensures that neither the compatibility scan nor the upgrade is started with an unexpected version of the installation files from Microsoft.

When a computer is ready for feature upgrade, the “Check PreRequisites” package no longer includes the content of the SetupErr.log in the package log. This makes it easier to read the log.

If a feature upgrade has failed, SetupDiag is automatically executed and the contents of the SetupDiag log is included in the package log. This makes troubleshooting easier, because SetupDiag processes the contents of several logfiles and filter the result, before writing it’s own log.

When a content package is not downloaded to the on-prem CapaInstaller environment, just before running a compatibility scan or an upgrade, the name of the content package is written to the top of the log.

Open

Cleanup after feature upgrade is now handled, before the end-user is shown the “Login” button on the dynamic installation screen. This means that end-users will no longer experience a “slow computer” after logging in.

It’s now possible to automatically re-run the “Upgrade” package if it fails, because the expected content package is not yet downloaded to the on-prem CapaInstaller environment.

Package re-run can be activated using the gbRetryLaterOnMissingOnPremPackage variable in the “Upgrade” package.

This way, IT-administrators are no longer forced to take manual action, when a feature upgrade fails due to missing content packages on-prem.

• The user profile count displayed on the dynamic installation screen is now correct.

• System volume partition check on Windows 10 1703/1709 is now supported.

• The “Check PreRequisites” package now waits for the compatibility scan to start, before updating the log.

• The value of the gbUpgradeReady variable is now saved in custom inventory.

• The dynamic installation screen is now only shown, if the upgrade process starts successfully.

Some of the improvements and bug fixes are integrated in the scripting libraries, and will also apply to CapaWinUpgrade v4.2