CapaDrivers v1.6 - Migrating from CapaDrivers v1.5
CapaDrivers v1.6 released on May 16, 2023
Step 1 - Migrate variable values
Section titled “Step 1 - Migrate variable values”Show more...
The existing variable values must be migrated from all the old packages to all the new packages.
Fortunately, most of the existing variable values can be migrated one-to-one.
Some variables has been discontinued and you don’t have to do anything about them:
- gbAllowDownloadFromPublicFrontend
- gbForceFileDownload
- gbAllowUseOfOlderDriverPacks
- gbClearCustomInventoryCategory
- gbReboot
Some new variables has been added and you should update the values to match your preference:
- gbAllowDriverDownloadFromCapaOne
- gbAllowWin10DriversOnWin11
You can read more about all the variables in CapaDrivers v1.6 - Variables
Step 2 - Update Group Membership
Section titled “Step 2 - Update Group Membership”Show more...
The group membership for the old Push, Publish and Force Driver Updates packages must be updated to match the new Push, Publish and Force Driver Updates packages.
You can use the “copy relation” functionality to achieve this, as shown below.
💡 We don’t recommend to select “Unlink groups and units from existing package” at this point, because unlinking the old package from units will cause you to lose package history.
Step 3 - Update the PreDriverCopyScript
Section titled “Step 3 - Update the PreDriverCopyScript”Show more...
The PreDriverCopyScript must be updated to use the new service files and the new driver pack format.
You can read instructions on how to update the PreDriverCopyScript in CapaDrivers v1.6 - PreDriverCopyScript