CapaDrivers 1.5 - Release Notes

Windows 11 is now supported.

Custom content packages are now supported.

This means that you can create your own driver content packages with drivers you select.

You can create custom driver content packages using these guidelines

Driver installation from Windows PE is now supported when running CapaInstaller 6.3 or newer.

With this feature drivers are installed during the OS deployment phase.

You can integrate this feature using these guidelines

The “Push Driver Updates” package is designed to push driver updates from the CapaInstaller Console. The package was previously called “Update Drivers”

The “Publish Driver Updates” package is designed to be published in the CapaInstaller Software Catalog. The package informs the end user before starting the download of driver content packages.

Open

The “Force Driver Updates” package is designed to run completely silent. The package doesn’t prompt the end user before starting the driver update and doesn’t show any warning prompts.

The “Collect Result and Cleanup” package was previously called “Post Update”. The new package contains the same functionality.

The “Download Content Package” package is designed to download (cache) the driver content package on endpoints, before starting the driver update.

Our Set & Forget mentality is now fully supported.

This means that CapaDrivers will automatically detect if a driver content package has already been applied - and then skip job execution accordingly.

You can override the default behavior with a setting in each package.

The Cloud Updater is now fully supported.

This means that driver content packages, service files and scripting libraries are automatically updated when necessary.

You can read more about the Cloud Updater here

CapaDrivers packages no longer return status Failed, when executed on virtual machines.

Instead, the packages status is set to Installed and the reason is written at the top of the package log.

Open

Open

Troubleshooting is now easier because you can follow which driver type that is currently being installed, and you can view details in the PnpUtilOutput.log if something goes wrong.

Open

Open

Collection of Custom Inventory to the CapaInstaller database can now be disabled with a setting in each package.

The option to enable verbose logging has been deprecated.

Instead, a simple log and a standard log are always created.

During package installation, the simple log is updated simultaneously with the standard log.

Open

When the package installation ends, the log files are switched and renamed, as shown below.

Open

The purpose of keeping log files with different levels of information is to show the contents of the simple log in the console and still have the option to troubleshoot various issues using the more comprehensive information from the standard log on the endpoints.

Temporary files are now automatically cleaned up.

When package execution stops due to a missing prerequisite or an error, the execution status is always logged in Custom Inventory.

Open

This makes it a lot easier to identify why a package installation has stopped, without having to access the package log.

Endpoints can now be excluded from driver updates - based on :

• IP-address

• IP-gateway

• Host Name

• Hardware Model

Danish, Norwegian, Swedish, Faroese* and English (default) are now supported, based on the operating system language.

Open

Open

* Faroese will work from CapaInstaller 6.5

• Custom Inventory is now only collected twice: When the script execution starts and when the script execution ends.

  Previously, Custom Inventory was collected continuously and many times, which sometimes caused excessive load on the CapaInstaller BaseAgent and on some rare occasions caused the CMS_AddCustomInventory function to return an error.

• The library file versioning has been changed to contain dates, instead of sequential numbers.

Open

This makes it easier to identify how old a specific scripting library is.