Tasks and software resources should get executed in the right order in the Managed Delivery policy - Tasks not executing until after the detection and download of a Resource regardless of order
Last Updated August 25, 2010
Tasks and software resources should get executed in the right order in the Managed Delivery policy.
Scenario is as follows: 1. Create Managed Delivery policy using the following way: First add a task A to the Managed Delivery policy and then add a software resource B to be installed. See this screenshot:
2. Enable and evaluate the policy on the client. 3. See that tasks get evaluated in the following order on the client: -Detection check for SW resource A -Download package for SW resource A -Task B -Execute install command for SW resource A Please, see screenshot 'order'.
So, the order of executing tasks in MD policy is incorrect. Thus the Detection check and download package task for SW resource B are running before Task A gets executed, however I have specified in MD policy that Task A should get executed before SW resource B gets installed. This can be applicable not only to the scenario I have described but to any other execution sequence of added items to MD policy. in all cases first detection checks and download package tasks will be executed, and then all other tasks. This can be a real problem if detection check success execution depends from a task, which is added before SW resource, to which detection check task is applied.
The logic of a Managed Software Delivery places detection rules before the actions of downloads and execution. This is by design, so the use case described in the Problem will not work for a Managed Software Delivery Policy.