As of 6.8.7 R2 HF1, filter driver versions of FlexApp One packages that differ from the driver version of the currently installed client tools can now be automatically installed when managed via ProfileUnity.
Scenario 1:
Managed FlexApp One applications packaged with an older filter driver are deployed via ProfileUnity configuration to a system with client tools running a newer filter driver.
Scenario 2:
Managed FlexApp One applications packaged with a newer filter driver are deployed via ProfileUnity configuration to a system with client tools running an older filter driver.
In both of the scenarios above, the absent filter driver can be automatically installed by configuring at least one of the respective FlexApp One rules to NOT be Click-To-Layer.
For example, in the first scenario, if the filter driver version of the installed client tools is newer than that of one or more managed FlexApp One packages, a rule for at least one of the older packages must have the Click-To-Layer option deselected for automatic installation of the older driver to occur.
Similarly, in the second scenario, if the filter driver version of the installed client tools is older than that of one or more managed FlexApp One packages, a rule for at least one of the newer packages must have the Click-To-Layer option deselected for automatic installation of the newer driver to occur.
NOTE: While both 6.8.7 R2 HF1 and HF2 FlexApp One packages contain the 2024 filter driver, there is a current limitation which only affects HF1 packages and prevents automatic installation when deploying to systems with client tools running an older filter driver. HF2 packages and newer are unaffected.