For some reason a software application, delivered via a managed software delivery policy, fails to install with some sort of error. On the managed software delivery policy, if the advanced options, results-based actions, actions after termination or failure, is set to continue, the compliance is recorded as compliant. The expectation is that the compliance would be not compliant. This setting is shown as follows:
No error message is applicable to this situation.
When you set the results-based action to continue, this will cause the compliance of the policy to be essentially ignored. This is stated in the policy, when you choose continue. The wording used is as follows: Compliance status of the policy will not be affected with the software.
If your managed software delivery policy is configured to delivery a 32-bit and 64-bit software application, with applicability checks for both, you were required to set the results based action to continue because setting it to abort, would cause the policy to abort when it failed the 32-bit applicability or 64-bit applicability checks.
By creating a new custom core setting, MdpContinueOnApplicabilityFailure, setting it to true, you enable expected functionality for applicability failure. Here is what will happen with this new setting configured:
You have a managed software delivery policy configured to deliver a 32-bit and 64-bit software application.
Each software release has an applicability check configured for 32-bit and 64-bit.
You now configure your managed software delivery policy, advanced options, with abort upon termination or failure as shown:
Your 64-bit endpoint will receive the managed software delivery policy and execute it.
When the 32-bit applicability check runs against the 64-bit operating system, it will now show as not detected and will continue on without actually aborting.
To install this point fix, please do the following:
Issue is fixed in a 8.0 HF6 pointfix (attached). It is also fixed in 8.1 RU4 and 8.5.